Bit core sync shows Bus error (core dumped)

Bitcore
#1

I installed bitcore full stack and was trying to sync with blockchain. But now everytime I run “bitcored”, I get the following Bus error. Could someone please suggest what could be the possible causes for this?

[2016-02-04T17:08:12.244Z] info: Starting bitcoind
[2016-02-04T17:08:16.840Z] info: Bitcoin Daemon Ready
[2016-02-04T17:08:16.840Z] info: Starting db
[2016-02-04T17:08:16.972Z] info: Bitcoin Database Ready
[2016-02-04T17:08:16.973Z] info: Starting address
[2016-02-04T17:08:17.401Z] info: Starting web
[2016-02-04T17:08:17.429Z] info: Starting insight-api
[2016-02-04T17:08:17.430Z] info: Starting insight-ui
[2016-02-04T17:08:17.430Z] info: Bitcore Node ready
[2016-02-04T17:08:27.809Z] info: Database Sync Status: Tip: 000000000000000000f657ed225a90f48388d69ad4b9223a0d57f863771c6280 Height: 390489 Rate: 0.6 blocks per second
[2016-02-04T17:08:37.819Z] info: Database Sync Status: Tip: 000000000000000000f657ed225a90f48388d69ad4b9223a0d57f863771c6280 Height: 390489 Rate: 0 blocks per second
[2016-02-04T17:08:47.829Z] info: Database Sync Status: Tip: 000000000000000000f657ed225a90f48388d69ad4b9223a0d57f863771c6280 Height: 390489 Rate: 0 blocks per second
[2016-02-04T17:08:57.839Z] info: Database Sync Status: Tip: 000000000000000000f657ed225a90f48388d69ad4b9223a0d57f863771c6280 Height: 390489 Rate: 0 blocks per second
[2016-02-04T17:09:07.851Z] info: Database Sync Status: Tip: 000000000000000000f657ed225a90f48388d69ad4b9223a0d57f863771c6280 Height: 390489 Rate: 0 blocks per second
[2016-02-04T17:09:17.861Z] info: Database Sync Status: Tip: 000000000000000000f657ed225a90f48388d69ad4b9223a0d57f863771c6280 Height: 390489 Rate: 0 blocks per second
[2016-02-04T17:09:27.871Z] info: Database Sync Status: Tip: 000000000000000000f657ed225a90f48388d69ad4b9223a0d57f863771c6280 Height: 390489 Rate: 0 blocks per second
[2016-02-04T17:09:37.882Z] info: Database Sync Status: Tip: 000000000000000000f657ed225a90f48388d69ad4b9223a0d57f863771c6280 Height: 390489 Rate: 0 blocks per second
[2016-02-04T17:09:47.892Z] info: Database Sync Status: Tip: 000000000000000000f657ed225a90f48388d69ad4b9223a0d57f863771c6280 Height: 390489 Rate: 0 blocks per second
[2016-02-04T17:09:57.903Z] info: Database Sync Status: Tip: 000000000000000000f657ed225a90f48388d69ad4b9223a0d57f863771c6280 Height: 390489 Rate: 0 blocks per second
[2016-02-04T17:10:07.913Z] info: Database Sync Status: Tip: 000000000000000000f657ed225a90f48388d69ad4b9223a0d57f863771c6280 Height: 390489 Rate: 0 blocks per second
[2016-02-04T17:10:17.923Z] info: Database Sync Status: Tip: 000000000000000000f657ed225a90f48388d69ad4b9223a0d57f863771c6280 Height: 390489 Rate: 0 blocks per second
[2016-02-04T17:10:27.935Z] info: Database Sync Status: Tip: 000000000000000000f657ed225a90f48388d69ad4b9223a0d57f863771c6280 Height: 390489 Rate: 0 blocks per second
[2016-02-04T17:10:37.945Z] info: Database Sync Status: Tip: 000000000000000000f657ed225a90f48388d69ad4b9223a0d57f863771c6280 Height: 390489 Rate: 0 blocks per second
[2016-02-04T17:10:47.955Z] info: Database Sync Status: Tip: 000000000000000000f657ed225a90f48388d69ad4b9223a0d57f863771c6280 Height: 390489 Rate: 0 blocks per second
Bus error (core dumped)

#2

If it’s reproducible you can probably get more information with gdb, there is some information here on how to debug: https://github.com/bitpay/bitcore-node/blob/master/docs/testing.md

Also providing versions of Node.js, npm, OS and architecture would also be helpful to debug.

#3

Thanks. I will take a look at the dev guide and try gdb.

But, here are some info about system environment:
OS: Ubuntu 1404
Architecture:AMD64
npm version:
{ npm: ‘2.14.12’,
ares: ‘1.10.1-DEV’,
http_parser: ‘2.5.0’,
icu: ‘56.1’,
modules: ‘46’,
node: ‘4.2.6’,
openssl: ‘1.0.2e’,
uv: ‘1.8.0’,
v8: ‘4.5.103.35’,
zlib: ‘1.2.8’ }

nodejs version: v4.2.6

I noticed in the install guide in the github repo, nodejs 0.12 is mentioned. Is version above 0.12 fine or does it have to be 0.12?

Thanks!

#4

switching to 0.12 fixed it.

#5

Oh really? Did it happen every time with 4?

#6

I ran it clean-slate three times and they all failed.

#7

Which build of Node.js 4 are you using? Installed with nvm?

Is there any API call you’re making that triggers this?

#8

used this source
https://deb.nodesource.com/setup_4.x

#9

I switched to nvm installed 0.12 and it worked fine. I wasn’t making API calls. It just died during block sync.