getaddrinfo EAI_AGAIN
See original GitHub issueMy node app is giving out this error. It looks like an API error.
{ Error: getaddrinfo EAI_AGAIN www.googleapis.com:443
20|Music | at Object.exports._errnoException (util.js:1022:11)
20|Music | at errnoException (dns.js:33:15)
20|Music | at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:76:26)
20|Music | code: 'EAI_AGAIN',
20|Music | errno: 'EAI_AGAIN',
20|Music | syscall: 'getaddrinfo',
20|Music | hostname: 'www.googleapis.com',
20|Music | host: 'www.googleapis.com',
20|Music | port: 443 }
20|Music | { Error: getaddrinfo EAI_AGAIN www.googleapis.com:443
20|Music | at Object.exports._errnoException (util.js:1022:11)
20|Music | at errnoException (dns.js:33:15)
20|Music | at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:76:26)
20|Music | code: 'EAI_AGAIN',
20|Music | errno: 'EAI_AGAIN',
20|Music | syscall: 'getaddrinfo',
20|Music | hostname: 'www.googleapis.com',
20|Music | host: 'www.googleapis.com',
20|Music | port: 443 }
Further details:
- Version: 19.0.0
- Node.js version: 8.0.0
- Operating system: Ubuntu 16.04.2
Thanks!
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
What's the cause of the error 'getaddrinfo EAI_AGAIN'?
EAI_AGAIN is a DNS lookup timed out error, means it is a network connectivity error or proxy related error.
Read more >The getaddrinfo EAI_AGAIN error again · Issue #15780 - GitHub
EAI_AGAIN means the DNS server replied that it cannot currently fulfill the request. (If you want the hairy details, the RCODE field in...
Read more >Http request generates error - getaddrinfo EAI_AGAIN
That is a bit odd, So the getaddrinfo EAI_AGAIN error tends to show up when the hostname being used can't be resolved and...
Read more >Getaddrinfo EAI_AGAIN stream.twitter.com - Standard APIs v1.1
Hi there I'm using the “Twit” Twitter API client for node in my project and I keep getting this error. Error: getaddrinfo EAI_AGAIN...
Read more >JavaScript : What's the source of Error: getaddrinfo EAI_AGAIN?
JavaScript : What's the source of Error: getaddrinfo EAI_AGAIN ? [ Gift : Animated Search Engine : https://bit.ly/AnimSearch ] JavaScript ...
Read more >Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
From Node official documentation:
Though the call to dns.lookup() will be asynchronous from JavaScript's perspective, it is implemented as a synchronous call to getaddrinfo(3) that runs on libuv's threadpool.
Thus, you can increase the number of workers in the libuv’s thread pool by setting
process.env.UV_THREADPOOL_SIZE
in your node program. The default number is 4, the max number you can set is 128.Closing this up since there’s likely nothing to be done on our side. Let us know if the async queue doesn’t help!