Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
libevent http fixes #6695
Fix a few rough edges discovered in use of the new libevent http server:;
init: Ignore SIGPIPE
Ignore SIGPIPE on all non-win32 OSes, otherwise an unexpectedly disconnecting
http: Disable libevent debug logging, if not explicitly enabled
Add a option "-debug=libevent" to enable libevent debugging for troubleshooting.
Addresses stdout spew in #6655.
rpc: Split option -rpctimeout into -rpcservertimeout and -rpcclienttimeout
The two timeouts for the server and client, are essentially different:
Split the options into
Should fix, or make it possible to fix timeout issues in #6655.
On the server side it doesn't affect that - it doesn't spend time waiting for input from the client.
Unfortunately I'm 0/2 on testing these. I couldn't recreate the SIGPIPE issue, in master or here, so thats's a start. But I still get what looks like a timeout from getblocktemplate_longpoll.py and I still get errors spewed to stdout when I don't have an IPv6 address.
EDIT: as per IRC:
Looks like the issue is not in bitcoin-cli but in the python http functionality that cannot cope with disconnects between requests (as said by @sdaftuar ). Which would be strange, but I'll take a look at it.
I could reproduce it on debian as well. Use a bitcoin-cli command like
The SIGPIPE gets emitted when bitcoind starts to write to a closed socket (ctrl-c will terminate bitcoin-cli which ends up in writing to a closed socket on the server side).