test: Error: getaddrinfo ENOTFOUND localhost #44003

AdamMajer · 2022-07-26T22:09:56Z

Version

18.6.0

Platform

openSUSE Tumbleweed

Subsystem

No response

What steps will reproduce the bug?

Currently the failures are visible in the current build log,

https://build.opensuse.org/public/build/devel:languages:nodejs/openSUSE_Tumbleweed/x86_64/nodejs18/_log

How often does it reproduce? Is there a required condition?

No response

What is the expected behavior?

No response

What do you see instead?

not ok 1995 parallel/test-net-socket-connect-without-cb
  ---
  duration_ms: 0.506
  severity: fail
  exitcode: 1
  stack: |-
    node:events:491
          throw er; // Unhandled 'error' event
          ^
    
    Error: getaddrinfo ENOTFOUND localhost
        at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:111:26)
    Emitted 'error' event on Socket instance at:
        at emitErrorNT (node:internal/streams/destroy:151:8)
        at emitErrorCloseNT (node:internal/streams/destroy:116:3)
        at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
      errno: -3008,
      code: 'ENOTFOUND',
      syscall: 'getaddrinfo',
      hostname: 'localhost'
    }
    
    Node.js v18.6.0
  ...

...

not ok 2000 parallel/test-net-socket-ready-without-cb
  ---
  duration_ms: 0.507
  severity: fail
  exitcode: 1
  stack: |-
    node:events:491
          throw er; // Unhandled 'error' event
          ^
    
    Error: getaddrinfo ENOTFOUND localhost
        at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:111:26)
    Emitted 'error' event on Socket instance at:
        at emitErrorNT (node:internal/streams/destroy:151:8)
        at emitErrorCloseNT (node:internal/streams/destroy:116:3)
        at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
      errno: -3008,
      code: 'ENOTFOUND',
      syscall: 'getaddrinfo',
      hostname: 'localhost'
    }
    
    Node.js v18.6.0
  ...

not ok 2591 parallel/test-tcp-wrap-listen
  ---
  duration_ms: 0.818
  severity: fail
  exitcode: 1
  stack: |-
    (node:18408) internal/test/binding: These APIs are for internal testing only. Do not use them.
    (Use `node18 --trace-warnings ...` to show where the warning was created)
    node:events:491
          throw er; // Unhandled 'error' event
          ^
    
    Error: getaddrinfo ENOTFOUND localhost
        at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:111:26)
    Emitted 'error' event on Socket instance at:
        at emitErrorNT (node:internal/streams/destroy:151:8)
        at emitErrorCloseNT (node:internal/streams/destroy:116:3)
        at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
      errno: -3008,
      code: 'ENOTFOUND',
      syscall: 'getaddrinfo',
      hostname: 'localhost'
    }
    
    Node.js v18.6.0
  ...

Additional information

> cat /etc/hosts
127.0.0.1 localhost
#
# hosts         This file describes a number of hostname-to-address
#               mappings for the TCP/IP subsystem.  It is mostly
#               used at boot time, when no name servers are running.
#               On small systems, this file can be used instead of a
#               "named" name server.
# Syntax:
#    
# IP-Address  Full-Qualified-Hostname  Short-Hostname
#

127.0.0.1       localhost
# fallback hostname used by NetworkManager
127.0.0.1       localhost.localdomain

# special IPv6 addresses
::1             localhost ipv6-localhost ipv6-loopback

fe00::0         ipv6-localnet

ff00::0         ipv6-mcastprefix
ff02::1         ipv6-allnodes
ff02::2         ipv6-allrouters
ff02::3         ipv6-allhosts

and resolv.conf doesn't exist. All other test cases that use localhost are passing, as expected.

The text was updated successfully, but these errors were encountered:

kvakil · 2022-07-27T05:13:43Z

curious what you see when doing strace. On Ubuntu I see the following:

$ strace -ff ./node test/parallel/test-tcp-wrap-listen.js |& grep localhost
[pid  4385] read(19, "127.0.0.1 localhost\n\n# The follo"..., 4096) = 221
[pid  4385] sendto(19, "\362*\1 \0\1\0\0\0\0\0\1\tlocalhost\3ec2\10inter"..., 51, MSG_NOSIGNAL, NULL, 0) = 51
[pid  4385] recvfrom(19, "\362*\201\203\0\1\0\0\0\0\0\1\tlocalhost\3ec2\10inter"..., 1024, 0, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("127.0.0.53")}, [28 => 16]) = 51
[pid  4385] sendto(19, "Uk\1 \0\1\0\0\0\0\0\1\tlocalhost\0\0\34\0\1\0\0)\4\260"..., 38, MSG_NOSIGNAL, NULL, 0) = 38
[pid  4385] recvfrom(19, "Uk\205\240\0\1\0\1\0\0\0\1\tlocalhost\0\0\34\0\1\300\f\0\34\0"..., 1024, 0, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("127.0.0.53")}, [28 => 16]) = 66

theanarkh · 2022-07-27T05:23:03Z

I get this error sometimes on my pc, but not always.

bnoordhuis · 2022-07-27T08:56:32Z

ENOTFOUND is a synthetic error that node fabricates when it doesn't get an answer back from getaddrinfo(3), it's not a real operating system-level error. Reasons include running out of file descriptors in libc (not visible to node), not getting back a response from the DNS server, etc. It's basically a catch-all.

AdamMajer · 2022-07-27T11:57:55Z

In this case, there is no DNS server and it works with other tests...

strace shows nothing. This is only a problem since about 18.2.0 and not before and not in any other released line. And I only see it in a VM build environment and not in a chroot (at least it disappeared there) which is very strange.

I will try to bisect the issue.

bnoordhuis · 2022-07-28T10:40:46Z

You mean v18.1.0 works? There are no changes between the two that seem like likely culprits. I'm interested to see what bisect turns up.

AdamMajer · 2022-07-28T18:44:28Z

So, the bisect ended up on 70b516e which is #43054 . Looking at the pull request, it kind of makes sense this is the one as the tests in question are explicitly skipped on some platforms.

https://github.com/nodejs/node/pull/43054/files#diff-5ba63fa1f910a3ec440b5174993719278ddca69569c0159e2c782173af190602

The test is reproducible every time on openSUSE:Tumbleweed build VM. I can't reproduce it outside of it on a workstation, but in the VM with no networking connections and only a hosts file to resolve localhost to ipv6 and ipv4, it reproduces every time.

I will try to look more closely what is actually failing here.

AdamMajer · 2022-07-28T18:46:44Z

This was introduced in 18.4.0. I mistyped earlier the versions. 18.2.0 still passed

kapouer · 2022-08-01T08:23:02Z

Is there no network interface at all, no loopback ?

As a consequence of nodejs#43014 , server sockets and others, once connected, report string family names. But when feeding these to Socket.connect(), it passes these to host resolution with a string for family while a numeric family is expected internally. This results wrong hints flags to be set and resolution to fail. As solution, is to add ability to handle both numeric and string family names when doing lookup and connect. Fixes: nodejs#44003

AdamMajer · 2022-08-01T12:10:18Z

So, I've learned something about debugging node over last few days :-) But I did find the problem.

> NODE_DEBUG=net ./node18 test/parallel/test-net-socket-ready-without-cb.js
NET 1834: setupListenHandle ::1 0 6 false undefined
NET 1834: setupListenHandle: create a handle
NET 1834: bind to ::1
{ address: '::1', family: 'IPv6', port: 32841 }
NET 1834: pipe false undefined
NET 1834: connect: find host localhost
NET 1834: connect: dns options { family: 'IPv6', hints: 32 }

The problem is that family is set to a string, which causes hints to be set to 32 which means AI_ADDRCONFIG and then address resolution fails.

On a network connected device, this passes.

Why? We can look at the manpage for getaddrinfo

If hints.ai_flags includes the AI_ADDRCONFIG flag, then IPv4 addresses are returned in the list pointed to by res only if the local system has at least one IPv4 address configured, and IPv6 addresses are returned only if the local system has at least one IPv6 address configured. The loopback address is not considered for this case as valid as a configured address. This flag is useful on, for example, IPv4-only systems, to ensure that getaddrinfo() does not return IPv6 socket addresses that would always fail in connect(2) or bind(2).

This is why these tests fail every time when you have a loopback interface as the only network interface active. They will pass if you have other network interfaces active.

As a consequence of nodejs#43014 , server sockets and others, once connected, report string family names. But when feeding these to Socket.connect(), it passes these to host resolution with a string for family while a numeric family is expected internally. This results in wrong hints flags to be set and resolution to fail. As solution, is to add ability to handle both numeric and string family names when doing lookup and connect. Fixes: nodejs#44003

As a consequence of #43014 , server sockets and others, once connected, report string family names. But when feeding these to Socket.connect(), it passes these to host resolution with a string for family while a numeric family is expected internally. This results in wrong hints flags to be set and resolution to fail. As solution, is to add ability to handle both numeric and string family names when doing lookup and connect. Fixes: #44003 PR-URL: #44083 Reviewed-By: Paolo Insogna <paolo@cowtech.it> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>

As a consequence of nodejs#43014 , server sockets and others, once connected, report string family names. But when feeding these to Socket.connect(), it passes these to host resolution with a string for family while a numeric family is expected internally. This results in wrong hints flags to be set and resolution to fail. As solution, is to add ability to handle both numeric and string family names when doing lookup and connect. Fixes: nodejs#44003 PR-URL: nodejs#44083 Reviewed-By: Paolo Insogna <paolo@cowtech.it> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>

As a consequence of #43014 , server sockets and others, once connected, report string family names. But when feeding these to Socket.connect(), it passes these to host resolution with a string for family while a numeric family is expected internally. This results in wrong hints flags to be set and resolution to fail. As solution, is to add ability to handle both numeric and string family names when doing lookup and connect. Fixes: #44003 PR-URL: #44083 Reviewed-By: Paolo Insogna <paolo@cowtech.it> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>

Daniel-quintero1 · 2023-10-03T22:04:23Z

original: Error: getaddrinfo ENOTFOUND undefined
GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:118:26) {
errno: -3008,
code: 'ENOTFOUND',
syscall: 'getaddrinfo',
hostname: 'undefined'

el error aca como podria solucionar? me arroja basicamente que no encuentra mi localhost.

kyungseopk1m · 2023-10-16T06:48:29Z

In my case, the same error occurred when I made a request to a server address other than localhost, but it turned out that there was no problem with me and the problem was with the server.
Additionally, requests intermittently repeated success and failure.

haojieZzz · 2024-08-02T00:55:08Z

I add the line in my hosts file and it worked;

127.0.0.1 localhost

theanarkh mentioned this issue Jul 27, 2022

lib: add diagnostics channel and perf hooks detail #43984

Merged

4 tasks

AdamMajer mentioned this issue Aug 1, 2022

net, dns: Socket should handle its output as input #44083

Merged

nodejs-github-bot closed this as completed in #44083 Aug 3, 2022

dustinbyrne mentioned this issue Dec 2, 2022

Unhandled network errors while retrieving end-user yarn dependencies getappmap/vscode-appland#545

Open

jorenn92 mentioned this issue Feb 11, 2024

Unable to setup on Synology / Docker jorenn92/Maintainerr#890

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

test: Error: getaddrinfo ENOTFOUND localhost #44003

test: Error: getaddrinfo ENOTFOUND localhost #44003

AdamMajer commented Jul 26, 2022

kvakil commented Jul 27, 2022

theanarkh commented Jul 27, 2022

bnoordhuis commented Jul 27, 2022

AdamMajer commented Jul 27, 2022

bnoordhuis commented Jul 28, 2022

AdamMajer commented Jul 28, 2022

AdamMajer commented Jul 28, 2022

kapouer commented Aug 1, 2022

AdamMajer commented Aug 1, 2022

Daniel-quintero1 commented Oct 3, 2023

kyungseopk1m commented Oct 16, 2023

haojieZzz commented Aug 2, 2024

test: Error: getaddrinfo ENOTFOUND localhost #44003

test: Error: getaddrinfo ENOTFOUND localhost #44003

Comments

AdamMajer commented Jul 26, 2022

Version

Platform

Subsystem

What steps will reproduce the bug?

How often does it reproduce? Is there a required condition?

What is the expected behavior?

What do you see instead?

Additional information

kvakil commented Jul 27, 2022

theanarkh commented Jul 27, 2022

bnoordhuis commented Jul 27, 2022

AdamMajer commented Jul 27, 2022

bnoordhuis commented Jul 28, 2022

AdamMajer commented Jul 28, 2022

AdamMajer commented Jul 28, 2022

kapouer commented Aug 1, 2022

AdamMajer commented Aug 1, 2022

Daniel-quintero1 commented Oct 3, 2023

kyungseopk1m commented Oct 16, 2023

haojieZzz commented Aug 2, 2024