When issuing bitcoind the `stop` rpc command, it waits forever for existing clients to disconnect #4235

issue ryancdotorg opened this issue on May 27, 2014

ryancdotorg commented at 1:51 AM on May 27, 2014: none

Also, oddly, it continues serving RPC commands to them.

I found this using bitcoinrpc.authproxy in python. Open up a process that polls bitcoind in a loop from python, then issue a stop command from a different client. bitcoind does not stop until the python script is closed.
laanwj added the label RPC on May 27, 2014
laanwj added the label Bug on May 27, 2014
sipa commented at 5:39 PM on January 23, 2017: member

I believe this is no longer the case since at least #5677 or earlier.

dcousens commented at 1:32 AM on June 2, 2017: contributor

Could not reproduce with master.

while true; do ./src/bitcoin-cli getinfo && sleep 0.1; done

./src/bitcoin-cli stop

No delay. Synced node. Loop dumped out the following immediately after the server stopped (as expected).

(make sure server is running and you are connecting to the correct RPC port)
error: couldn't connect to server: unknown (code -1)

Contributors

Labels