bsc
bsc copied to clipboard
Geth won't gracefully shut down
System information
Geth version: Geth v1.1.11
OS & Version: Ubuntu 20.04 LTS
Commit hash: -
Having trouble shutting down a new node, it keeps hanging with Waiting background transaction indexer to exit
. Synced from BNB48 snapshot block #18615124.
Expected behaviour
Shuts down gracefully
Actual behaviour
Waiting background transaction indexer to exit
message followed by hang and infinite Looking for peers
, no progress in shutdown
Steps to reproduce the behaviour
Gracefully exit Geth with SIGINT
Backtrace
INFO [06-12|15:42:29.024] Got interrupt, shutting down...
INFO [06-12|15:42:29.025] HTTP server stopped endpoint=127.0.0.1:8545
INFO [06-12|15:42:29.026] IPC endpoint closed url=/root/nvme1_data/newnode/geth.ipc
INFO [06-12|15:42:29.029] Ethereum protocol stopped
INFO [06-12|15:42:29.029] Transaction pool stopped
ERROR[06-12|15:42:30.631] Snapshot extension registration failed peer=dbdf7056 err="peer connected on snap without compatible eth support"
INFO [06-12|15:42:30.663] Looking for peers peercount=1 tried=25 static=36
-------> INFO [06-12|15:42:34.029] Waiting background transaction indexer to exit
INFO [06-12|15:42:40.846] Looking for peers peercount=0 tried=101 static=36
ERROR[06-12|15:42:44.316] Snapshot extension registration failed peer=5513c6a4 err="peer connected on snap without compatible eth support"
INFO [06-12|15:42:50.908] Looking for peers peercount=0 tried=155 static=36
ERROR[06-12|15:42:53.288] Snapshot extension registration failed peer=af0550e5 err="peer connected on snap without compatible eth support"
More info is needed. Try edit your config.toml, change log level to Crit
. Then there will be more logs to help
https://github.com/BNB48Club/bsc-snapshots/issues/6#issuecomment-1154214315
~~https://github.com/BNB48Club/bsc-snapshots/issues/6#issuecomment-1157253367 - This was pretty much just my mistake and unrelated with the node.~~
..Apparently not, I'm experiencing issues shutting down every block pruned DB. The flags du5 provided seem to be of no help(in fact, --txlookuplimit 0 just makes the issue happen every time instead of most of the time).