NBXplorer v2.2.20 - Connection unexpectedly failed: Unexpected exception while connecting to socket

[dajohi]

My NBXplorer v2.2.20 w/ postgres 12 and full-node bitcoind is looping on startup.

Feb 17 18:31:26 btc run.sh[1026581]: info: Configuration:  BTC: Testing RPC connection to http://127.0.0.1:8332/
Feb 17 18:31:26 btc run.sh[1026581]: info: Configuration:  BTC: RPC connection successful
Feb 17 18:31:26 btc run.sh[1026581]: info: Configuration:  BTC: Full node version detected: 220000
Feb 17 18:31:27 btc run.sh[1026581]: info: Configuration:  BTC: Loading chain from cache...
Feb 17 18:31:27 btc run.sh[1026581]: info: Configuration:  BTC: Height: 777036
Feb 17 18:31:27 btc run.sh[1026581]: info: Configuration:  BTC: Trying to connect via the P2P protocol to trusted node (127.0.0.1:8333)...
Feb 17 18:31:27 btc run.sh[1026581]: info: Explorer:       BTC: TCP Connection succeed, handshaking...
Feb 17 18:31:27 btc run.sh[1026581]: info: Explorer:       BTC: Handshaked
Feb 17 18:31:27 btc run.sh[1026581]: info: Configuration:  BTC: Loading chain from node
Feb 17 18:31:27 btc run.sh[1026581]: info: Explorer:       BTC: Loading chain...
Feb 17 18:31:27 btc run.sh[1026581]: info: Explorer:       BTC: Chain loaded
Feb 17 18:31:27 btc run.sh[1026581]: info: Explorer:       BTC: NBXplorer is correctly whitelisted by the node
Feb 17 18:31:27 btc run.sh[1026581]: info: Configuration:  BTC: Height: 777036
Feb 17 18:31:27 btc run.sh[1026581]: info: Explorer:       BTC: Handshaked node
Feb 17 18:31:27 btc run.sh[1026581]: info: Explorer:       BTC: Starting scan at block 776883
Feb 17 18:31:27 btc run.sh[1026581]: info: Events:         BTC: Node state changed: NotStarted => NBXplorerSynching
Feb 17 18:31:27 btc run.sh[1026581]: fail: Explorer:       BTC: Connection unexpectedly failed: Unexpected exception while connecting to socket
Feb 17 18:31:27 btc run.sh[1026581]: info: Events:         BTC: Node state changed: NBXplorerSynching => NotStarted
Feb 17 18:31:27 btc run.sh[1026581]: info: Configuration:  BTC: Testing RPC connection to http://127.0.0.1:8332/
Feb 17 18:31:27 btc run.sh[1026581]: info: Configuration:  BTC: RPC connection successful
Feb 17 18:31:27 btc run.sh[1026581]: info: Configuration:  BTC: Full node version detected: 220000

• Is there a known fix? can it be back-ported to v2.2.21 perhaps?
• Where are the upgrade docs from going from v2.2.20 to latest? Does Postgresql 12 work with the latest NBXplorer?
• Is there a way to redownload just the chain from bitcoind?

[NicolasDorier]

it should work, nothing sould have changed. I don't see any error here?

[NicolasDorier]

@dajohi Loading chain..., it show you aren't using the postgres backend but the dbtrie backend.

[tsjk]

I actually observed this recently. Like

info: Configuration:  NBXplorer version 2.5.25
info: Configuration:  Data Directory: /datadir
info: Configuration:  Configuration File: /datadir/Main/settings.config
info: Configuration:  Network: Mainnet
info: Configuration:  Supported chains: BTC,LBTC
info: Configuration:  Network: Mainnet
info: Configuration:  Supported chains: BTC,LBTC
info: NBXplorer.DatabaseSetup: Postgres services activated
...
info: NBXplorer.Indexer.BTC: TCP Connection succeed, handshaking...
info: NBXplorer.Indexer.BTC: Handshaked
info: NBXplorer.Indexer.BTC: Testing RPC connection to http://host.containers.internal:8332/
info: NBXplorer.Indexer.BTC: RPC connection successful
info: NBXplorer.Indexer.BTC: Full node version detected: 260100
info: NBXplorer.Indexer.BTC: Has txindex support
info: NBXplorer.Indexer.BTC: NBXplorer is correctly whitelisted by the node
info: NBXplorer.Events: BTC: Node state changed: NotStarted => NBXplorerSynching
info: NBXplorer.Indexer.BTC: Node disconnected (Unexpected exception while connecting to socket)
info: NBXplorer.Events: BTC: Node state changed: NBXplorerSynching => NotStarted

The last 10 lines loop forever and it never reaches a Ready state.

I'm not sure when it started failing - a week ago or so - and restarting did not help. I can't think of any relevant changes on my side. However, today I upgraded to v2.5.26 and it started working again.

[RampantDespair]

Same thing here, was on a fail loop on v2.5.25, upgraded to v2.5.27 and it started working again...