What's the source of Error: getaddrinfo EAI_AGAIN?

Question

My server threw this today, which is a Node.js error I've never seen before:

Error: getaddrinfo EAI_AGAIN my-store.myshopify.com:443
    at Object.exports._errnoException (util.js:870:11)
    at errnoException (dns.js:32:15)
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:78:26)

I'm wondering if this is related to the DynDns DDOS attack which affected Shopify and many other services today. Here's an article about that.

My main question is what does dns.js do? What part of node is it a part of? How can I recreate this error with a different domain?

score 180 · Answer 1 · answered Mar 12 '19 at 23:10

180

If you get this error with Firebase Cloud Functions, this is due to the limitations of the free tier (outbound networking only allowed to Google services).

Upgrade to the Flame or Blaze plans for it to work.

answered Mar 12 '19 at 23:10

bastien

2,447
1
10
20

39

You just saved me **hours** of research. Kudos – David Chopin Dec 03 '19 at 02:44
1

that's right, just upgraded to pay per use blaze plan for zero cost (this carry-forward free tier data from spark) – GorvGoyl Dec 13 '19 at 21:28
Can you @NullPointer, elaborate the solution, i still getting errors ` Error: could not handle the request` – Alam Mar 17 '20 at 12:44
I have same issue and have upgraded to Blaze account but still the problem is same. I am trying using postman. – Devendra Singh May 11 '20 at 11:55
For some reason I've had this when trying access my credentials for SMTP via `process.env.SOMETHING`, even with the `Blaze` enabled. – Daniel Danielecki Nov 27 '20 at 15:35

score 138 · Answer 2 · answered Oct 21 '16 at 17:40

EAI_AGAIN is a DNS lookup timed out error, means it is a network connectivity error or proxy related error.

My main question is what does dns.js do?

The dns.js is there for node to get ip address of the domain(in brief).

Some more info: http://www.codingdefined.com/2015/06/nodejs-error-errno-eaiagain.html

score 13 · Answer 3 · answered May 22 '20 at 12:51

13

If you get this error from within a docker container, e.g. when running npm install inside of an alpine container, the cause could be that the network changed since the container was started.

To solve this, just stop and restart the container

docker-compose down
docker-compose up

Source: https://github.com/moby/moby/issues/32106#issuecomment-578725551

answered May 22 '20 at 12:51

Diego P. Steiner

1,316
10
14

I have a suspected issue where the network is reset on the host, and then the containers seem to have DNS errors thereafter. Is there some way to configure the containers to survive this *without* stopping them? – trademark May 14 '21 at 20:21

score 3 · Answer 4 · answered Nov 07 '18 at 19:20

The OP's error specifies a host (my-store.myshopify.com). The error I encountered is the same in all respects except that no domain is specified.

My solution may help others who are drawn here by the title "Error: getaddrinfo EAI_AGAIN"

I encountered the error when trying to serve a NodeJs & VueJs app from a different VM from where the code was developed originally.

The file vue.config.js read :

 module.exports = {
   devServer: {
     host: 'tstvm01',
     port: 3030,
   },
 };

When served on the original machine the start up output is :

App running at:
- Local:   http://tstvm01:3030/ 
- Network: http://tstvm01:3030/

Using the same settings on a VM tstvm07 got me a very similar error to the one the OP describes:

 INFO  Starting development server...
 10% building modules 1/1 modules 0 activeevents.js:183                              
      throw er; // Unhandled 'error' event
      ^

Error: getaddrinfo EAI_AGAIN
    at Object._errnoException (util.js:1022:11)
    at errnoException (dns.js:55:15)
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:92:26)

If it ain't already obvious, changing vue.config.js to read ...

 module.exports = {
   devServer: {
     host: 'tstvm07',
     port: 3030,
   },
 };

... solved the problem.

score 2 · Answer 5 · answered Jul 30 '18 at 17:49

2

This is the issue related to hosts file setup. Add the following line to your hots file In Ububtu: /etc/hosts

127.0.0.1   localhost

In windows: c:\windows\System32\drivers\etc\hosts

127.0.0.1   localhost

answered Jul 30 '18 at 17:49

Radhe9254

163
1
10

score 2 · Answer 6 · edited Feb 14 '20 at 20:31

I started getting this error (different stack trace though) after making a trivial update to my GraphQL API application that is operated inside a docker container. For whatever reason, the container was having difficulty resolving a back-end service being used by the API.

After poking around to see if some change had been made in the docker base image I was building from (node:13-alpine, incidentally), I decided to try the oldest computer science trick of rebooting... I stopped and started the docker container and all went back to normal.

Clearly, this isn't a meaningful solution to the underlying problem - I am merely posting this since it did clear up the issue for me without going too deep down rabbit holes.

score 2 · Answer 7 · answered Oct 07 '20 at 14:43

As xerq's excellent answer explains, this is a DNS timeout issue.

I wanted to contribute another possible answer for those of you using Windows Subsystem for Linux - there are some cases where something seems to be askew in the client OS after Windows resumes from sleep. Restarting the host OS will fix these issues (it's also likely restarting the WSL service will do the same).

score 1 · Answer 8 · answered Nov 30 '17 at 12:00

@xerq pointed correctly, here's some more reference http://www.codingdefined.com/2015/06/nodejs-error-errno-eaiagain.html

i got the same error, i solved it by updating "hosts" file present under this location in windows os

C:\Windows\System32\drivers\etc

Hope it helps!!

score 0 · Answer 9 · answered Mar 30 '20 at 12:47

0

I had a same problem with AWS and Serverless. I tried with eu-central-1 region and it didn't work so I had to change it to us-east-2 for the example.

answered Mar 30 '20 at 12:47

Igor Janković

5,210
5
26
45

Daniel Danielecki · Answer 10 · 2020-12-02T13:43:55.163

0

Enabled Blaze and it still doesn't work?

Most probably you need to set .env from the right path, require('dotenv').config({ path: __dirname + './../.env' }); won't work (or any other path). Simply put the .env file in the functions directory, from which you deploy to Firebase.

edited Dec 02 '20 at 13:43

answered Nov 29 '20 at 17:26

Daniel Danielecki

3,527
3
29
41

score 0 · Answer 11 · answered Feb 08 '21 at 10:28

0

In my case the problem was the docker networks ip allocation range, see this post for details

answered Feb 08 '21 at 10:28

mbesson

300
9

score -4 · Answer 12 · answered Jul 02 '20 at 10:48

-4

If you are not get that at localhost either production, that means you must upgrade your plan due to the limitations of the free tier

answered Jul 02 '20 at 10:48

Randy Reiza

15
4

score -17 · Answer 13 · answered Jul 05 '17 at 13:27

-17

updating the npm to latest fixes this problem for me.

npm install npm@latest

this issue is related to your network connectivity. hence can be temporary. on a stable internet connection this issue was hardly observed.

answered Jul 05 '17 at 13:27

anerjan

37
8

27

How updating the package manager could fix an error which is not related to the package manager ? – FF_Dev Aug 31 '17 at 10:39
4

In @anerjan's defence, it can occur when running `npm install` and I imagine the time it took to stop update and restart he'd connected back to the internet. – Rambatino Jun 20 '18 at 21:20

What's the source of Error: getaddrinfo EAI_AGAIN?

13 Answers13

Linked

Related