bitcoind stops responding



Summary:

In an email correspondence on October 1, 2013, slush reported that one process was asking getinfo every second as a fallback to possibly misconfigured blocknotify. Additionally, it called getblocktemplate every 30 seconds. However, with version 0.9, users will be able to use getbestblockhash instead of getinfo which has a wider range of functions. Another process was calling getinfo once a minute to check if bitcoind was working. If there was no response within a minute, the process would kill bitcoind and restart it. Gavin Andresen suggested using 'help getinfo' to see if bitcoind was responding to RPC requests without acquiring any locks. Furthermore, users running into the maximum-of-4-keepalive-requests issue were advised to run with -rpcthreads=11 or however many keepalive connections they needed to support to avoid the problem. Gavin Andresen suggested that the rpc code should be smarter, and making the last rpc thread ignore keepalive and always disconnecting should be a simple patch. He added that patches were welcome.


Updated on: 2023-06-07T17:12:12.338507+00:00