I'm building a service which does some automatic Bitcoin transactions and balance checking. In the system I now created some logging, which told me that my bitcoind daemon (running on Ubuntu 14.04 server) gave an error code -9 when running the following command bitcoind getbalance
. In the bitcoind source I found error code 9 described as:
RPC_CLIENT_NOT_CONNECTED = -9, // Bitcoin is not connected
About this I have 3 simple questions:
- First: what does this mean? I'm running the command on the same machine where the daemon is running, so no remote connection needed.
- Secondly; how can this happen? Why does a stable running bitcoind daemon suddenly gets disconnected?
- And most importantly; how can I prevent this from happening?
All tips are welcome!
getconnectioncount
when this error occurs, it should return zero. A client can get disconnected when the node(s) it is connected to become unavailable. Try manually connecting to one or more fallback/trusted nodes.getconnectioncount
when this happens so we'll know for sure that your client gets disconnected from the bitcoin network. Getting from 87 to 0 though is not something usual nor expected. I would suggest you check your server's connectivity, as many things could go wrong at this level.