Closed Simon0x closed 6 years ago
_logs
For more information, see the CONTRIBUTING guide.
CONTRIBUTING
The btc controller had an uncaught exception when I start the miner.
Expected behavior: The error should be handled in a correct way.
Actual behavior: Error when I started the miner.
(0.5.5/9905e51)
You can get this information:
forever start ./bin/cli start --miner-key CryptoSmileee --node --ui --ws
Full Log: http://telobot.com/UP_o.log
2018-05-08T17:11:39.014Z INFO server.index Server available at http://0.0.0.0:3000 2018-05-08T17:11:40.248Z ERROR rover.btc.controller Uncaught exception: { stack: [ 'Error: Unsupported message command: encinit', 'at Messages._buildFromBuffer (/home/bc/bcnode/node_modules/bitcore-p2p/lib/messages/index.js:101:11)', 'at Messages.parseBuffer (/home/bc/bcnode/node_modules/bitcore-p2p/lib/messages/index.js:74:15)', 'at Peer._readMessage (/home/bc/bcnode/node_modules/bitcore-p2p/lib/peer.js:219:31)', 'at Socket.<anonymous> (/home/bc/bcnode/node_modules/bitcore-p2p/lib/peer.js:167:10)', 'at Socket.emit (events.js:180:13)', 'at addChunk (_stream_readable.js:274:12)', 'at readableAddChunk (_stream_readable.js:261:11)', 'at Socket.Readable.push (_stream_readable.js:218:10)', 'at TCP.onread (net.js:581:20)' ], message: 'Unsupported message command: encinit' }
Resolved by #250
Prerequisites
_logs
directory)For more information, see the
CONTRIBUTING
guide.Description
The btc controller had an uncaught exception when I start the miner.
Steps to Reproduce
Expected behavior: The error should be handled in a correct way.
Actual behavior: Error when I started the miner.
Versions
(0.5.5/9905e51)
Application (required)
You can get this information:
forever start ./bin/cli start --miner-key CryptoSmileee --node --ui --ws
Environment (optional but helpful)
Logs
Full Log: http://telobot.com/UP_o.log