Unable to start bitcored - errors in bitcoind service


(jetyap) #1

Hi, I’m facing some issues resulting in an error when starting bitcored in Ubuntu 16.04 LTS after breaking out from an existing process during block synchronisation. Can someone provide some advice how I can troubleshoot or resolve this?

[2017-04-22T10:22:10.930Z] info: Bitcoin Height: 395770 Percentage: 74.27
^C[2017-04-22T10:22:21.638Z] info: Beginning shutdown
[2017-04-22T10:22:21.639Z] info: Stopping insight-ui
[2017-04-22T10:22:21.640Z] info: Stopping insight-api
[2017-04-22T10:22:21.640Z] info: Stopping web
[2017-04-22T10:22:21.641Z] info: Stopping bitcoind
[2017-04-22T10:22:35.824Z] error: RPCError: Bitcoin JSON-RPC: Request Error: soc ket hang up
[2017-04-22T10:22:35.825Z] error: RPCError: Bitcoin JSON-RPC: Request Error: soc ket hang up
[2017-04-22T10:22:36.642Z] error: Failed to stop services: Error: bitcoind proce ss did not exit
abc123@instance-1:~$ bitcored
[2017-04-22T10:22:52.328Z] info: Using config: /home/abc123/.bitcore/b itcore-node.json
[2017-04-22T10:22:52.329Z] info: Using network: livenet
[2017-04-22T10:22:52.330Z] info: Starting bitcoind
[2017-04-22T10:22:52.332Z] info: Using bitcoin config file: /home/abc123/.bitcore/data/bitcoin.conf
[2017-04-22T10:22:52.335Z] info: Starting bitcoin process
[2017-04-22T10:27:47.734Z] warn: Activating best chain…
[2017-04-22T10:27:47.735Z] error: Failed to start services
[2017-04-22T10:27:47.736Z] error: RPCError: Activating best chain…
at Bitcoin._wrapRPCError (/home/abc123/.nvm/versions/node/v4.8.2/l ib/node_modules/bitcore/node_modules/bitcore-node/lib/services/bitcoind.js:449:1 3)
at /home/abc123/.nvm/versions/node/v4.8.2/lib/node_modules/bitcore /node_modules/bitcore-node/lib/services/bitcoind.js:779:28
at IncomingMessage. (/home/abc123/.nvm/versions/node/v4 .8.2/lib/node_modules/bitcore/node_modules/bitcore-node/node_modules/bitcoind-rp c/lib/index.js:107:7)
at emitNone (events.js:72:20)
at IncomingMessage.emit (events.js:166:7)
at endReadableNT (_stream_readable.js:923:12)
at nextTickCallbackWith2Args (node.js:511:9)
at process._tickCallback (node.js:425:17)
[2017-04-22T10:27:47.736Z] info: Beginning shutdown
[2017-04-22T10:27:47.737Z] info: Stopping insight-ui (not started)
[2017-04-22T10:27:47.737Z] info: Stopping insight-api (not started)
[2017-04-22T10:27:47.737Z] info: Stopping web (not started)
[2017-04-22T10:27:47.738Z] info: Stopping bitcoind
[2017-04-22T10:27:51.039Z] error: Failed to stop services: Error: bitcoind spawn ed process exited with status code: 1
abc123@instance-1:~$ bitcored
[2017-04-22T11:03:46.754Z] info: Using config: /home/abc123/.bitcore/b itcore-node.json
[2017-04-22T11:03:46.755Z] info: Using network: livenet
[2017-04-22T11:03:46.756Z] info: Starting bitcoind
[2017-04-22T11:03:46.758Z] info: Using bitcoin config file: /home/rsa-key-201704 20/.bitcore/data/bitcoin.conf
[2017-04-22T11:03:46.762Z] info: Starting bitcoin process
[2017-04-22T11:03:51.814Z] warn: Loading block index…
[2017-04-22T11:03:56.821Z] warn: Verifying blocks…
[2017-04-22T11:04:01.830Z] warn: Activating best chain…
^C[2017-04-22T11:04:06.168Z] info: Beginning shutdown
[2017-04-22T11:04:06.169Z] info: Stopping insight-ui (not started)
[2017-04-22T11:04:06.169Z] info: Stopping insight-api (not started)
[2017-04-22T11:04:06.170Z] info: Stopping web (not started)
[2017-04-22T11:04:06.170Z] info: Stopping bitcoind
[2017-04-22T11:04:06.832Z] error: Failed to start services
[2017-04-22T11:04:06.833Z] error: Error: Stopping while trying to spawn bitcoind.
at /home/abc123/.nvm/versions/node/v4.8.2/lib/node_modules/bitcore/node_modules/bitcore-node/lib/services/bitcoind.js:905:25
at /home/abc123/.nvm/versions/node/v4.8.2/lib/node_modules/bitcore/node_modules/bitcore-node/node_modules/async/lib/async.js:676:51
at /home/abc123/.nvm/versions/node/v4.8.2/lib/node_modules/bitcore/node_modules/bitcore-node/node_modules/async/lib/async.js:726:13
at /home/abc123/.nvm/versions/node/v4.8.2/lib/node_modules/bitcore/node_modules/bitcore-node/node_modules/async/lib/async.js:52:16
at /home/abc123/.nvm/versions/node/v4.8.2/lib/node_modules/bitcore/node_modules/bitcore-node/node_modules/async/lib/async.js:264:21
at /home/abc123/.nvm/versions/node/v4.8.2/lib/node_modules/bitcore/node_modules/bitcore-node/node_modules/async/lib/async.js:44:16
at /home/abc123/.nvm/versions/node/v4.8.2/lib/node_modules/bitcore/node_modules/bitcore-node/node_modules/async/lib/async.js:723:17
at /home/abc123/.nvm/versions/node/v4.8.2/lib/node_modules/bitcore/node_modules/bitcore-node/node_modules/async/lib/async.js:167:37
at /home/abc123/.nvm/versions/node/v4.8.2/lib/node_modules/bitcore/node_modules/bitcore-node/node_modules/async/lib/async.js:652:25
at /home/abc123/.nvm/versions/node/v4.8.2/lib/node_modules/bitcore/node_modules/bitcore-node/lib/services/bitcoind.js:887:16
[2017-04-22T11:04:06.833Z] info: Beginning shutdown
[2017-04-22T11:04:06.833Z] info: Stopping insight-ui (not started)
[2017-04-22T11:04:06.833Z] info: Stopping insight-api (not started)
[2017-04-22T11:04:06.833Z] info: Stopping web (not started)
[2017-04-22T11:04:06.834Z] info: Stopping bitcoind
[2017-04-22T11:04:21.185Z] error: Failed to stop services: Error: bitcoind process did not exit


(Chibuzo Okolo) #2

could it be that your config file setting isn’t correct? There seem to be a space between “b” and “i” in bitcore-node.json.

See if that helps.


(FedFranz) #3

What happens if you try to run bitcoind (the same executable) manually?