Error: getaddrinfo EAI_AGAIN











up vote
41
down vote

favorite
1












My server threw this today, which is a nodejs 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 apart of? I can I recreate this error with a different domain?










share|improve this question


























    up vote
    41
    down vote

    favorite
    1












    My server threw this today, which is a nodejs 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 apart of? I can I recreate this error with a different domain?










    share|improve this question
























      up vote
      41
      down vote

      favorite
      1









      up vote
      41
      down vote

      favorite
      1






      1





      My server threw this today, which is a nodejs 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 apart of? I can I recreate this error with a different domain?










      share|improve this question













      My server threw this today, which is a nodejs 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 apart of? I can I recreate this error with a different domain?







      javascript node.js error-handling dns shopify






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Oct 21 '16 at 17:11









      ThomasReggi

      17.1k43141270




      17.1k43141270
























          5 Answers
          5






          active

          oldest

          votes

















          up vote
          51
          down vote













          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






          share|improve this answer




























            up vote
            0
            down vote













            @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:WindowsSystem32driversetc



            Hope it helps!!






            share|improve this answer




























              up vote
              0
              down vote













              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:windowsSystem32driversetchosts



              127.0.0.1   localhost





              share|improve this answer




























                up vote
                0
                down vote













                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.






                share|improve this answer




























                  up vote
                  -8
                  down vote













                  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.






                  share|improve this answer

















                  • 16




                    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






                  • 1




                    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 at 21:20











                  Your Answer






                  StackExchange.ifUsing("editor", function () {
                  StackExchange.using("externalEditor", function () {
                  StackExchange.using("snippets", function () {
                  StackExchange.snippets.init();
                  });
                  });
                  }, "code-snippets");

                  StackExchange.ready(function() {
                  var channelOptions = {
                  tags: "".split(" "),
                  id: "1"
                  };
                  initTagRenderer("".split(" "), "".split(" "), channelOptions);

                  StackExchange.using("externalEditor", function() {
                  // Have to fire editor after snippets, if snippets enabled
                  if (StackExchange.settings.snippets.snippetsEnabled) {
                  StackExchange.using("snippets", function() {
                  createEditor();
                  });
                  }
                  else {
                  createEditor();
                  }
                  });

                  function createEditor() {
                  StackExchange.prepareEditor({
                  heartbeatType: 'answer',
                  convertImagesToLinks: true,
                  noModals: true,
                  showLowRepImageUploadWarning: true,
                  reputationToPostImages: 10,
                  bindNavPrevention: true,
                  postfix: "",
                  imageUploader: {
                  brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
                  contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
                  allowUrls: true
                  },
                  onDemand: true,
                  discardSelector: ".discard-answer"
                  ,immediatelyShowMarkdownHelp:true
                  });


                  }
                  });














                   

                  draft saved


                  draft discarded


















                  StackExchange.ready(
                  function () {
                  StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f40182121%2ferror-getaddrinfo-eai-again%23new-answer', 'question_page');
                  }
                  );

                  Post as a guest















                  Required, but never shown

























                  5 Answers
                  5






                  active

                  oldest

                  votes








                  5 Answers
                  5






                  active

                  oldest

                  votes









                  active

                  oldest

                  votes






                  active

                  oldest

                  votes








                  up vote
                  51
                  down vote













                  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






                  share|improve this answer

























                    up vote
                    51
                    down vote













                    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






                    share|improve this answer























                      up vote
                      51
                      down vote










                      up vote
                      51
                      down vote









                      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






                      share|improve this answer












                      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







                      share|improve this answer












                      share|improve this answer



                      share|improve this answer










                      answered Oct 21 '16 at 17:40









                      xerq

                      599313




                      599313
























                          up vote
                          0
                          down vote













                          @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:WindowsSystem32driversetc



                          Hope it helps!!






                          share|improve this answer

























                            up vote
                            0
                            down vote













                            @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:WindowsSystem32driversetc



                            Hope it helps!!






                            share|improve this answer























                              up vote
                              0
                              down vote










                              up vote
                              0
                              down vote









                              @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:WindowsSystem32driversetc



                              Hope it helps!!






                              share|improve this answer












                              @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:WindowsSystem32driversetc



                              Hope it helps!!







                              share|improve this answer












                              share|improve this answer



                              share|improve this answer










                              answered Nov 30 '17 at 12:00









                              Mateen

                              675717




                              675717






















                                  up vote
                                  0
                                  down vote













                                  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:windowsSystem32driversetchosts



                                  127.0.0.1   localhost





                                  share|improve this answer

























                                    up vote
                                    0
                                    down vote













                                    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:windowsSystem32driversetchosts



                                    127.0.0.1   localhost





                                    share|improve this answer























                                      up vote
                                      0
                                      down vote










                                      up vote
                                      0
                                      down vote









                                      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:windowsSystem32driversetchosts



                                      127.0.0.1   localhost





                                      share|improve this answer












                                      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:windowsSystem32driversetchosts



                                      127.0.0.1   localhost






                                      share|improve this answer












                                      share|improve this answer



                                      share|improve this answer










                                      answered Jul 30 at 17:49









                                      Radhe9254

                                      3115




                                      3115






















                                          up vote
                                          0
                                          down vote













                                          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.






                                          share|improve this answer

























                                            up vote
                                            0
                                            down vote













                                            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.






                                            share|improve this answer























                                              up vote
                                              0
                                              down vote










                                              up vote
                                              0
                                              down vote









                                              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.






                                              share|improve this answer












                                              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.







                                              share|improve this answer












                                              share|improve this answer



                                              share|improve this answer










                                              answered Nov 7 at 19:20









                                              Martin Bramwell

                                              6691627




                                              6691627






















                                                  up vote
                                                  -8
                                                  down vote













                                                  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.






                                                  share|improve this answer

















                                                  • 16




                                                    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






                                                  • 1




                                                    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 at 21:20















                                                  up vote
                                                  -8
                                                  down vote













                                                  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.






                                                  share|improve this answer

















                                                  • 16




                                                    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






                                                  • 1




                                                    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 at 21:20













                                                  up vote
                                                  -8
                                                  down vote










                                                  up vote
                                                  -8
                                                  down vote









                                                  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.






                                                  share|improve this answer












                                                  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.







                                                  share|improve this answer












                                                  share|improve this answer



                                                  share|improve this answer










                                                  answered Jul 5 '17 at 13:27









                                                  anerjan

                                                  108




                                                  108








                                                  • 16




                                                    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






                                                  • 1




                                                    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 at 21:20














                                                  • 16




                                                    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






                                                  • 1




                                                    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 at 21:20








                                                  16




                                                  16




                                                  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




                                                  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




                                                  1




                                                  1




                                                  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 at 21:20




                                                  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 at 21:20


















                                                   

                                                  draft saved


                                                  draft discarded



















































                                                   


                                                  draft saved


                                                  draft discarded














                                                  StackExchange.ready(
                                                  function () {
                                                  StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f40182121%2ferror-getaddrinfo-eai-again%23new-answer', 'question_page');
                                                  }
                                                  );

                                                  Post as a guest















                                                  Required, but never shown





















































                                                  Required, but never shown














                                                  Required, but never shown












                                                  Required, but never shown







                                                  Required, but never shown

































                                                  Required, but never shown














                                                  Required, but never shown












                                                  Required, but never shown







                                                  Required, but never shown







                                                  這個網誌中的熱門文章

                                                  Xamarin.form Move up view when keyboard appear

                                                  Post-Redirect-Get with Spring WebFlux and Thymeleaf

                                                  Anylogic : not able to use stopDelay()