SIGNAL USERS READ THIS FIRST: code: 'ERR_INTERNAL_ASSERTION' in internalConnectMultiple #47644

yuki12321 · 2023-04-20T15:56:14Z

Version

20.0.0

Platform

Darwin MacBookPro.local 22.3.0 Darwin Kernel Version 22.3.0: Mon Jan 30 20:42:11 PST 2023; root:xnu-8792.81.3~2/RELEASE_X86_64 x86_64

Subsystem

No response

What steps will reproduce the bug?

I ran the Storybook installation on Next.js 13.3.0 and this is what I see.

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

No response

What is the expected behavior? Why is that the expected behavior?

No response

What do you see instead?

$ npx sb init

 storybook init - the simplest way to add a Storybook to your project. 

 • Detecting project type. ✓
 • Adding Storybook support to your "Next" app
node:internal/assert:14
    throw new ERR_INTERNAL_ASSERTION(message);
    ^

Error [ERR_INTERNAL_ASSERTION]: This is caused by either a bug in Node.js or incorrect usage of Node.js internals.
Please open an issue with this stack trace at https://github.com/nodejs/node/issues

    at new NodeError (node:internal/errors:399:5)
    at assert (node:internal/assert:14:11)
    at internalConnectMultiple (node:net:1106:3)
    at Timeout.internalConnectMultipleTimeout (node:net:1637:3)
    at listOnTimeout (node:internal/timers:575:11)
    at process.processTimers (node:internal/timers:514:7) {
  code: 'ERR_INTERNAL_ASSERTION'
}

Node.js v20.0.0

Additional information

No response

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

tniessen · 2023-04-24T14:48:49Z

Based on the stack trace, it looks similar to #46669 and #46670, so possibly related to #44731, #46587. cc @ShogunPanda

ShogunPanda · 2023-04-24T20:28:37Z

@tniessen It seems so. I'll take a look soon

kamagatos · 2023-04-26T00:00:38Z

I'm also seeing a similar issue with ssh2 after upgrading to Node 20.

Repro steps:

Connect to an invalid host
Add an error event handler

client.connect({
  host: 'yahoo.com',
  port: 22,
  username: 'bob',
  password: 'secret'
})

// Adding this line crashes the process.
client.on('error', () => {})

asp3 · 2023-04-29T17:32:28Z

seeing this issue as well on production

Error [ERR_INTERNAL_ASSERTION]: This is caused by either a bug in Node.js or incorrect usage of Node.js internals.

| 2023-04-29T13:32:31.670-04:00 | Please open an issue with this stack trace at https://github.com/nodejs/node/issues
| 2023-04-29T13:32:31.670-04:00 | at new NodeError (node:internal/errors:399:5)
| 2023-04-29T13:32:31.670-04:00 | at assert (node:internal/assert:14:11)
| 2023-04-29T13:32:31.670-04:00 | at internalConnectMultiple (node:net:1106:3)
| 2023-04-29T13:32:31.670-04:00 | at Timeout.internalConnectMultipleTimeout (node:net:1637:3)
| 2023-04-29T13:32:31.670-04:00 | at listOnTimeout (node:internal/timers:575:11)
| 2023-04-29T13:32:31.670-04:00 | at process.processTimers (node:internal/timers:514:7)

Our old build from 10 days ago still works, but all new builds seem to run into this issue.

MikeRalphson · 2023-05-09T10:20:44Z

Just a note, subscribing as still present in v20.1.0:

In a net and async/await heavy program:

node:internal/assert:14
    throw new ERR_INTERNAL_ASSERTION(message);
    ^

Error [ERR_INTERNAL_ASSERTION]: This is caused by either a bug in Node.js or incorrect usage of Node.js internals.
Please open an issue with this stack trace at https://github.com/nodejs/node/issues

    at new NodeError (node:internal/errors:399:5)
    at assert (node:internal/assert:14:11)
    at internalConnectMultiple (node:net:1107:3)
    at Timeout.internalConnectMultipleTimeout (node:net:1638:3)
    at listOnTimeout (node:internal/timers:575:11)
    at process.processTimers (node:internal/timers:514:7) {
  code: 'ERR_INTERNAL_ASSERTION'
}

Node.js v20.1.0

ShogunPanda · 2023-05-09T10:32:32Z

This might be fixed by #47860.
Will keep you posted on this.

ShogunPanda · 2023-05-11T22:51:43Z

@kamagatos @yuki12321 The PR above has landed in master. If you can compile Node locally, do you mind checking it if solves your issues as well?

MikeRalphson · 2023-05-12T11:10:14Z

I now see the following on master:

/Users/mikeralphson/c/node/node[73535]: ../../src/crypto/crypto_tls.cc:1233:static void node::crypto::TLSWrap::GetServername(const FunctionCallbackInfo<v8::Value> &): Assertion `(wrap->ssl_) != nullptr' failed.
 1: 0x100bc1cf0 node::Abort() [/Users/mikeralphson/c/node/out/Release/node]
 2: 0x100bc1a30 node::PrintCaughtException(v8::Isolate*, v8::Local<v8::Context>, v8::TryCatch const&) [/Users/mikeralphson/c/node/out/Release/node]
 3: 0x100d14700 node::crypto::TLSWrap::GetServername(v8::FunctionCallbackInfo<v8::Value> const&) [/Users/mikeralphson/c/node/out/Release/node]
 4: 0x100dca0d4 v8::internal::MaybeHandle<v8::internal::Object> v8::internal::(anonymous namespace)::HandleApiCallHelper<false>(v8::internal::Isolate*, v8::internal::Handle<v8::internal::HeapObject>, v8::internal::Handle<v8::internal::FunctionTemplateInfo>, v8::internal::Handle<v8::internal::Object>, unsigned long*, int) [/Users/mikeralphson/c/node/out/Release/node]
 5: 0x100dc9928 v8::internal::Builtin_HandleApiCall(int, unsigned long*, v8::internal::Isolate*) [/Users/mikeralphson/c/node/out/Release/node]
 6: 0x10164cb24 Builtins_CEntry_Return1_ArgvOnStack_BuiltinExit [/Users/mikeralphson/c/node/out/Release/node]
 7: 0x1015c43e4 Builtins_InterpreterEntryTrampoline [/Users/mikeralphson/c/node/out/Release/node]
 8: 0x10664d2cc
 9: 0x1015c250c Builtins_JSEntryTrampoline [/Users/mikeralphson/c/node/out/Release/node]
10: 0x1015c21f4 Builtins_JSEntry [/Users/mikeralphson/c/node/out/Release/node]
11: 0x100eb082c v8::internal::(anonymous namespace)::Invoke(v8::internal::Isolate*, v8::internal::(anonymous namespace)::InvokeParams const&) [/Users/mikeralphson/c/node/out/Release/node]
12: 0x100eb00a8 v8::internal::Execution::Call(v8::internal::Isolate*, v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Object>, int, v8::internal::Handle<v8::internal::Object>*) [/Users/mikeralphson/c/node/out/Release/node]
13: 0x100d77e80 v8::Function::Call(v8::Local<v8::Context>, v8::Local<v8::Value>, int, v8::Local<v8::Value>*) [/Users/mikeralphson/c/node/out/Release/node]
14: 0x100afdf84 node::InternalMakeCallback(node::Environment*, v8::Local<v8::Object>, v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*, node::async_context) [/Users/mikeralphson/c/node/out/Release/node]
15: 0x100b120b8 node::AsyncWrap::MakeCallback(v8::Local<v8::Function>, int, v8::Local<v8::Value>*) [/Users/mikeralphson/c/node/out/Release/node]
16: 0x100b292dc node::ConnectionWrap<node::TCPWrap, uv_tcp_s>::AfterConnect(uv_connect_s*, int) [/Users/mikeralphson/c/node/out/Release/node]
17: 0x100c917b0 node::MakeLibuvRequestCallback<uv_connect_s, void (*)(uv_connect_s*, int)>::Wrapper(uv_connect_s*, int) [/Users/mikeralphson/c/node/out/Release/node]
18: 0x1015acf94 uv__stream_io [/Users/mikeralphson/c/node/out/Release/node]
19: 0x1015b5650 uv__io_poll [/Users/mikeralphson/c/node/out/Release/node]
20: 0x1015a2e94 uv_run [/Users/mikeralphson/c/node/out/Release/node]
21: 0x100afe7d0 node::SpinEventLoopInternal(node::Environment*) [/Users/mikeralphson/c/node/out/Release/node]
22: 0x100c03504 node::NodeMainInstance::Run() [/Users/mikeralphson/c/node/out/Release/node]
23: 0x100b899d0 node::LoadSnapshotDataAndRun(node::SnapshotData const**, node::InitializationResultImpl const*) [/Users/mikeralphson/c/node/out/Release/node]
24: 0x100b89c24 node::Start(int, char**) [/Users/mikeralphson/c/node/out/Release/node]
25: 0x1a2ad3f28 start [/usr/lib/dyld]
zsh: abort

ShogunPanda · 2023-05-12T12:42:54Z

@MikeRalphson Can you please provide a repro file, along with the dig query of all the hosts you are trying to reach?

tniessen · 2023-05-14T10:53:36Z

The same internal assertion is causing CI to fail on Fedora machines, see #48000. However, it is not the ERR_INTERNAL_ASSERTION that this issue was about originally.

Side note: the main branch is called main. We intentionally abandoned the previous branch name.

bradleybeighton · 2023-05-16T14:47:36Z

This randomly started happening on my production build after a deployment. I'm using lts-alpine image in my docker file, has there been a recent change that could be causing this?

ShogunPanda · 2023-05-16T15:29:16Z

@brandon-beacher It's the network family auto selection which was enabled by default in 20.0.0.
I fixed this issue (already merged in main) and once I'll fix some other problems it should go out on 20.2.0 or 20.3.0.

tniessen · 2023-05-19T11:33:58Z

This is still an issue in Node.js 20.2.0. As a workaround, you can try restoring the more predictable pre-20 behavior by setting this environment variable:

NODE_OPTIONS="--no-network-family-autoselection"

arllop · 2023-06-03T15:04:33Z

this happened when i open signal app on mac laptop. has this been fixed? thanks.

tniessen · 2023-06-03T16:03:01Z

@arllop If Signal does not override NODE_OPTIONS, the workaround in #47644 (comment) might work.

dmcr · 2023-08-04T13:26:32Z

Have been redirected here as per my closed duplicated ticket.

So as I understand it this is still an active issue in v20.4 and is related to the network area with the current solutions being to:
Apply NODE_OPTIONS="--no-network-family-autoselection" or to use node ^v19.

I have been redirected here but this is also closed so presumably the best place to follow as to when ^v20 is usable is now #48763 #request/request#3458

I can confirm that going back to v19 resolves this issue in production for me.

ShogunPanda · 2023-08-05T13:01:15Z

@dmcr can you please provide a repro repo or at least which host are you trying to connect to and how your DNS resolves such host?

fix source: nodejs/node#47644 (comment)

PR-URL: nodejs#48464 Fixes: npm/cli#6409 Fixes: KararTY/dank-twitch-irc#13 Fixes: nodejs#47644 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com>

Rand0mF · 2023-08-30T10:33:02Z

Issue still occurring for node 20.5.1 with the same stacktrace.
Randomly starts occurring and keeps happening for multiple hours after which it randomly stopped.
Node is running as a kubernetes service and not using workers or websockets (like #48763).
Using the docker image node:20.5.1

ShogunPanda · 2023-09-11T07:02:15Z

@Rand0mF In order to address this, I need to know which host your node app is connecting to and how your local (or Kubernetes system) is resolving it. Can you provide me such info?

Rand0mF · 2023-09-13T14:34:40Z

@ShogunPanda Unfortunately I don't know.. The app is doing many queries to all kinds of hosts. The error logs don't provide any useful information for that, that's the only thing which is printed. Reverse engineering is difficult as it seems to occur completely at random, I didn't yet find a way to reproduce it.

Error [ERR_INTERNAL_ASSERTION]: This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
    at new NodeError (node:internal/errors:405:5)
    at assert (node:internal/assert:14:11)
    at internalConnectMultiple (node:net:1118:3)
    at Timeout.internalConnectMultipleTimeout (node:net:1687:3)
    at listOnTimeout (node:internal/timers:575:11)
    at process.processTimers (node:internal/timers:514:7)

ainsleyclark · 2023-10-01T18:15:03Z

Very sporadic error which seems to be difficult to debug locally as @Rand0mF mentioned.
export NODE_OPTIONS=--no-network-family-autoselection works.
All v20.x versions are producing the same error.

ShogunPanda · 2023-10-03T13:44:44Z

@ainsleyclark Is the same for you? Can you provide a list of which hosts the production system is connecting to and how these are resolved by the production system DNS servers?

pimterry · 2023-10-12T12:20:44Z

I'm seeing lots of these errors too, on Node v20.8.0. Similar to other reports, it seems to be very intermittent and only happening under load. I can't confirm the addresses involved either unfortunately (software is running on end user machines, I just see exception reports).

Rand0mF · 2023-11-16T14:09:45Z

@ShogunPanda
list of hosts will still be difficult, here's the dig output from within the container for

cluster-external hosts

dig google.com

; <<>> DiG 9.18.19 <<>> google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7886
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;google.com.			IN	A

;; ANSWER SECTION:
google.com.		30	IN	A	142.250.185.142

;; Query time: 2 msec
;; SERVER: 10.251.0.10#53(10.251.0.10) (UDP)
;; WHEN: Thu Nov 16 14:03:26 UTC 2023
;; MSG SIZE  rcvd: 55

cluster-internal hosts

dig hello-world.default.svc.cluster.local

; <<>> DiG 9.18.19 <<>> hello-world.default.svc.cluster.local
;; global options: +cmd
;; Got answer:
;; WARNING: .local is reserved for Multicast DNS
;; You are currently testing what happens when an mDNS query is leaked to DNS
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 13182
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;hello-world.default.svc.cluster.local. IN A

;; ANSWER SECTION:
hello-world.default.svc.cluster.local. 30 IN A	10.251.3.203

;; Query time: 8 msec
;; SERVER: 10.251.0.10#53(10.251.0.10) (UDP)
;; WHEN: Thu Nov 16 14:08:01 UTC 2023
;; MSG SIZE  rcvd: 71

any other flags which would be helpful?

ShogunPanda · 2023-11-22T16:20:14Z

Nope, that should be it. I will keep you posted.

stefanrows · 2023-12-14T08:31:22Z

Still experiencing the issue with Node 20^. Switching to Node 18 solves the problem for me.

ShogunPanda · 2023-12-14T09:05:00Z

This should be solved by #51045. Will keep you as soon as this reaches 20.x.

guillenotfound · 2024-04-03T07:31:19Z

Any updates on when this is going to be fixed for 20.x @ShogunPanda ?

brian6932 · 2024-04-03T07:56:39Z

It has been for a long time @guillenotfound https://nodejs.org/en/blog/release/v20.12.0#new-connection-attempt-events.
Latest node release's v21.7.1...

ShogunPanda · 2024-04-04T10:40:39Z

@guillenotfound It has been release in 20.12.0.

tniessen added the net Issues and PRs related to the net subsystem. label Apr 24, 2023

This was referenced May 19, 2023

Encountered [ERR_INTERNAL_ASSERTION] #48068

Closed

ERR_INTERNAL_ASSERTION #48075

Closed

tniessen mentioned this issue May 23, 2023

Implement parallel Happy Eyeballs as described in RFC 8305 #48145

Open

brian6932 mentioned this issue May 24, 2023

PSA: If you're on node 20.0.0 and above, and want to use this library with client.configuration.connection.secure === true, use the argument --no-network-family-autoselection KararTY/dank-twitch-irc#13

Closed

This was referenced Jun 2, 2023

Error [ERR_INTERNAL_ASSERTION] #48278

Closed

ERR_INTERNAL_ASSERTION error #48281

Closed

tniessen changed the title ~~code: 'ERR_INTERNAL_ASSERTION'~~ code: 'ERR_INTERNAL_ASSERTION' in internalConnectMultiple Jun 2, 2023

This was referenced Jun 3, 2023

Signal Unhandled Error #48307

Closed

ERR_INTERNAL_ASSERTION from Signal desktop when unlocking sleeping Mac #48302

Closed

Unhandled Error. Error [ERR_INTERNAL_ASSERTION] #48315

Closed

tniessen mentioned this issue Jun 3, 2023

bug in Node.js or incorrect usage of Node.js internals. #48318

Closed

tniessen added duplicate Issues and PRs that are duplicates of other issues or PRs. and removed duplicate Issues and PRs that are duplicates of other issues or PRs. labels Jun 3, 2023

tniessen added the confirmed-bug Issues with confirmed bugs. label Jun 3, 2023

brimonk added a commit to brimonk/rollycubes that referenced this issue Aug 6, 2023

fixes an issue where vite would constantly be disconnected

9734b2a

fix source: nodejs/node#47644 (comment)

brimonk mentioned this issue Aug 6, 2023

fixes an issue where vite would constantly be disconnected cgsdev0/rollycubes#122

Merged

cgsdev0 pushed a commit to cgsdev0/rollycubes that referenced this issue Aug 6, 2023

fixes an issue where vite would constantly be disconnected

480a852

fix source: nodejs/node#47644 (comment)

ShogunPanda mentioned this issue Oct 3, 2023

Error [ERR_INTERNAL_ASSERTION] #49294

Closed

james-rms mentioned this issue Oct 18, 2023

at processTimers (node:internal/timers:514:7) { code: 'ERR_INTERNAL_ASSERTION' } #50233

Closed

tniessen mentioned this issue Oct 26, 2023

lib: hide navigator behind a flag #50412

Closed

lpinca mentioned this issue Oct 28, 2023

Bug: Node.js ERR_INTERNAL_ASSERTION error when updating and saving content with Strapi [v4.15.0] #50436

Closed

SanderKok01 mentioned this issue Nov 21, 2023

ERR_INTERNAL_ASSERTION #50754

Closed

miguelmota mentioned this issue Dec 10, 2023

ERR_INTERNAL_ASSERTION / hop sdk fetchConfigFromS3 error: Error: fetchJsonOrThrow hop-protocol/hop#538

Closed

edoardo-bluframe mentioned this issue Jan 12, 2024

Strapi crash - ERR_INTERNAL_ASSERTION: This is caused by either a bug in Node.js or incorrect usage of Node.js internals. strapi/strapi#18084

Closed

advplyr mentioned this issue Mar 16, 2024

[Bug]: OPML import containing own feed == Server crash advplyr/audiobookshelf#2752

Closed

advplyr mentioned this issue Apr 21, 2024

Trying to add a podcast hosted on HTTPS on local network causes INTERNAL_ASSERTION crash advplyr/audiobookshelf-app#1187

Closed

kakkokari-gtyih mentioned this issue Jul 13, 2024

catodon.socialを照会できないことがある misskey-dev/misskey#14135

Closed

1 task

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

SIGNAL USERS READ THIS FIRST: code: 'ERR_INTERNAL_ASSERTION' in internalConnectMultiple #47644

SIGNAL USERS READ THIS FIRST: code: 'ERR_INTERNAL_ASSERTION' in internalConnectMultiple #47644

yuki12321 commented Apr 20, 2023

tniessen commented Apr 24, 2023

ShogunPanda commented Apr 24, 2023

kamagatos commented Apr 26, 2023

asp3 commented Apr 29, 2023 •

edited

Loading

MikeRalphson commented May 9, 2023

ShogunPanda commented May 9, 2023 •

edited

Loading

ShogunPanda commented May 11, 2023

MikeRalphson commented May 12, 2023

ShogunPanda commented May 12, 2023

tniessen commented May 14, 2023

bradleybeighton commented May 16, 2023

ShogunPanda commented May 16, 2023

tniessen commented May 19, 2023

arllop commented Jun 3, 2023

tniessen commented Jun 3, 2023

dmcr commented Aug 4, 2023 •

edited

Loading

ShogunPanda commented Aug 5, 2023

Rand0mF commented Aug 30, 2023

ShogunPanda commented Sep 11, 2023

Rand0mF commented Sep 13, 2023

ainsleyclark commented Oct 1, 2023

ShogunPanda commented Oct 3, 2023

pimterry commented Oct 12, 2023

Rand0mF commented Nov 16, 2023 •

edited

Loading

ShogunPanda commented Nov 22, 2023

stefanrows commented Dec 14, 2023

ShogunPanda commented Dec 14, 2023

guillenotfound commented Apr 3, 2024

brian6932 commented Apr 3, 2024

ShogunPanda commented Apr 4, 2024

SIGNAL USERS READ THIS FIRST: code: 'ERR_INTERNAL_ASSERTION' in internalConnectMultiple #47644

SIGNAL USERS READ THIS FIRST: code: 'ERR_INTERNAL_ASSERTION' in internalConnectMultiple #47644

Comments

yuki12321 commented Apr 20, 2023

Version

Platform

Subsystem

What steps will reproduce the bug?

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

What is the expected behavior? Why is that the expected behavior?

What do you see instead?

Additional information

tniessen commented Apr 24, 2023

ShogunPanda commented Apr 24, 2023

kamagatos commented Apr 26, 2023

asp3 commented Apr 29, 2023 • edited Loading

Error [ERR_INTERNAL_ASSERTION]: This is caused by either a bug in Node.js or incorrect usage of Node.js internals.

MikeRalphson commented May 9, 2023

ShogunPanda commented May 9, 2023 • edited Loading

ShogunPanda commented May 11, 2023

MikeRalphson commented May 12, 2023

ShogunPanda commented May 12, 2023

tniessen commented May 14, 2023

bradleybeighton commented May 16, 2023

ShogunPanda commented May 16, 2023

tniessen commented May 19, 2023

arllop commented Jun 3, 2023

tniessen commented Jun 3, 2023

dmcr commented Aug 4, 2023 • edited Loading

ShogunPanda commented Aug 5, 2023

Rand0mF commented Aug 30, 2023

ShogunPanda commented Sep 11, 2023

Rand0mF commented Sep 13, 2023

ainsleyclark commented Oct 1, 2023

ShogunPanda commented Oct 3, 2023

pimterry commented Oct 12, 2023

Rand0mF commented Nov 16, 2023 • edited Loading

ShogunPanda commented Nov 22, 2023

stefanrows commented Dec 14, 2023

ShogunPanda commented Dec 14, 2023

guillenotfound commented Apr 3, 2024

brian6932 commented Apr 3, 2024

ShogunPanda commented Apr 4, 2024

asp3 commented Apr 29, 2023 •

edited

Loading

ShogunPanda commented May 9, 2023 •

edited

Loading

dmcr commented Aug 4, 2023 •

edited

Loading

Rand0mF commented Nov 16, 2023 •

edited

Loading