I am operating Debian 11, all updates put in. 12gb RAM, huge inside SSD for storage.
$ /usr/native/bin/bitcoin-25.0/bin/bitcoin-cli cease
has labored effectively shutting down bitcoind on my pc till immediately, when it appears to have hanged half approach by way of the standard course of.
$ tail .bitcoin/debug.log
reveals:
2023-11-27T13:51:11Z tor: Thread interrupt
2023-11-27T13:51:11Z torcontrol thread exit
2023-11-27T13:51:11Z Shutdown: In progress...
2023-11-27T13:51:11Z addcon thread exit
2023-11-27T13:51:11Z opencon thread exit
2023-11-27T13:51:11Z internet thread exit
2023-11-27T13:51:11Z msghand thread exit
2023-11-27T14:20:38Z Potential stale tip [snipped]
2023-11-27T14:31:08Z Potential stale tip [snipped]
2023-11-27T14:41:38Z Potential stale tip [snipped]
… $ ps ax | fgrep bitcoind
reveals:
1399 ? SLl 171:06 /usr/native/bin/bitcoin-25.0/bin/bitcoind
10818 pts/0 S+ 0:00 grep -F bitcoind
… and $ high
reveals:
1399 [username] 20 0 4218920 1.0g 184480 S 0.3 8.5 171:06.03 b-shutoff
Contents of .bitcoin/ are:
banlist.json
bitcoin.conf
bitcoind.pid
blocks
chainstate
database
db.log
debug.log
fee_estimates.dat
mempool.dat
friends.dat
settings.json
… so no “lock” file seen there.
So, did I do something uncommon earlier than I entered bitcoin-cli cease
? Sure, two issues I do not normally do:
-
Some hours earlier than the tried cease, I ran
rescan
, which appears to have labored completely effectively. -
I used to be operating bisq once I entered
bitcoin-cli cease
. I’ve now closed bisq (“A bit late now!” you may say…) however the b-shutoff continues to be hung.
Would be glad about any ideas, or questions you might need that would assist me out closing the daemon gracefully.