question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Node disconnected for reason: Array size too big

See original GitHub issue

For some reason my NBXplorer node keeps disconnecting from bitcoind with the error “Array size too big”. Attached the log:

Feb 01 21:20:12 btcpricetshirt nbxplorer[500482]: Now listening on: http://127.0.0.1:24444
Feb 01 21:20:12 btcpricetshirt nbxplorer[500482]: Application started. Press Ctrl+C to shut down.
Feb 01 21:20:12 btcpricetshirt nbxplorer[500482]: info: NBXplorer.Indexer.BTC: RPC connection successful
Feb 01 21:20:13 btcpricetshirt nbxplorer[500482]: info: NBXplorer.Indexer.BTC: Full node version detected: 230000
Feb 01 21:20:13 btcpricetshirt nbxplorer[500482]: info: NBXplorer.Indexer.BTC: NBXplorer is correctly whitelisted by the node
Feb 01 21:20:13 btcpricetshirt nbxplorer[500482]: info: NBXplorer.Events: BTC: Node state changed: NotStarted => NBXplorerSynching
Feb 01 21:20:13 btcpricetshirt nbxplorer[500482]: info: NBXplorer.Events: BTC: Node state changed: NBXplorerSynching => Ready
Feb 01 21:20:14 btcpricetshirt nbxplorer[500482]: warn: NBXplorer.Indexer.BTC: Node disconnected for reason: Unexpected exception while connecting to socket (Specified argument was out of the range of valid values. (Parameter 'Array size too big'))
Feb 01 21:20:14 btcpricetshirt nbxplorer[500482]: info: NBXplorer.Events: BTC: Node state changed: Ready => NotStarted

This is nbxplorer v2.3.41 connecting to bitcoind v23.

Unfortunately it’s not that easy for me to upgrade because I’m using nix-bitcoind and newer versions seems to have broken other packages, so I’m stuck here for the time being… Is this a known issue? Is there a known fix/workaround?

Thanks

Issue Analytics

  • State:closed
  • Created 8 months ago
  • Comments:7 (3 by maintainers)

github_iconTop GitHub Comments

3reactions
NicolasDoriercommented, Feb 2, 2023

This bug has been fixed the 14 november 2022 on this version v2.3.45 update to the latest version please v2.3.58

1reaction
openomscommented, Feb 2, 2023

Can confirm that updating NBXplorer fixed this issue.

Before on v2.3.33: image

After the update on v2.3.58: image

Read more comments on GitHub >

github_iconTop Results From Across the Web

socket.io client automatically disconnecting in long Node.js ...
The solution to your problem is to modify the pingTimeout when initiating the server. From Socket.io: The server sends a ping, ...
Read more >
How to escape from memory leaks in JavaScript
The main cause of memory leaks in an application is due to unwanted ... interval periodically and results in a huge size for...
Read more >
Dealing with Node.js high CPU in production
All of these operations can cause high CPU, make sure that payload size is not huge, use pagination, and don't prepopulate unnecessary data....
Read more >
Fix memory problems - Chrome Developers
Detached DOM nodes are a common cause of memory leaks. This section teaches you how to use DevTools' heap profilers to identify detached...
Read more >
Error event IDs and error codes
Event ID Notification type Error code 009020 E 1001 009040 E 1002 009052 W 1196
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found