Is there an existing issue for this?
- I have searched the existing issues
Current behaviour
I ran “bitcoin-cli stop” and it didn’t stop.
Expected behaviour
I expect it to stop.
Steps to reproduce
It usually works. Sometimes it doesn’t. I don’t know how to reproduce.
Relevant log output
Here’s the end of debug.log
:
2023-06-25T12:55:49Z Saw new header hash=0000000000000000000375a71ccc0569c279dbb751bdbb70d86d983cd38eea68 height=795857
2023-06-25T12:55:55Z UpdateTip: new best=0000000000000000000375a71ccc0569c279dbb751bdbb70d86d983cd38eea68 height=795857 version=0x20600000 log2_work=94.262739 tx=856322917 date='2023-06-25T12:55:38Z' progress=1.000000 cache=90.3MiB(608799txo)
2023-06-25T12:56:00Z New outbound peer connected: version: 70016, blocks=795857, peer=3892, peeraddr=[...].onion:8333 (block-relay-only)
2023-06-25T12:57:09Z SetNetworkActive: false
2023-06-25T12:57:56Z tor: Thread interrupt
2023-06-25T12:57:56Z Shutdown: In progress...
2023-06-25T12:57:56Z RemoveLocal([...].onion:8333)
2023-06-25T12:57:56Z torcontrol thread exit
2023-06-25T12:57:56Z addcon thread exit
2023-06-25T12:57:56Z opencon thread exit
2023-06-25T12:57:56Z net thread exit
2023-06-25T12:57:56Z msghand thread exit
Here’s the output of thread apply all where
in gdb:
Every thread appears to be waiting for something.
There’s no CPU or disk activity, and it’s been 20 minutes since I asked it to shut down.
How did you obtain Bitcoin Core
Compiled from source
What version of Bitcoin Core are you using?
v25.0
Operating system and version
Debian GNU/Linux 11 (bullseye)
Machine specifications
No response