I synced the whole blockchain by RPC (reading the .dat fails miserably) and when client connects to query, it crashes. Next thing I do is restart, the whole shit crumbled down.
hoshi@NGC4826:~/insight$ INSIGHT_NETWORK=livenet npm start
>
[email protected] start /home/hoshi/insight
> INSIGHT_PUBLIC_PATH=public node node_modules/.bin/insight-bitcore-api
____ _ __ __ ___ _
/ _/___ _____(_)___ _/ /_ / /_ / | ____ (_)
/ // __ \/ ___/ / __ `/ __ \/ __/ / /| | / __ \/ /
_/ // / / (__ ) / /_/ / / / / /_ / ___ |/ /_/ / /
/___/_/ /_/____/_/\__, /_/ /_/\__/ /_/ |_/ .___/_/
/____/ /_/
v0.2.3
# Configuration:
Network: livenet INSIGHT_NETWORK
Database Path: /home/hoshi/.insight INSIGHT_DB
Safe Confirmations: 6 INSIGHT_SAFE_CONFIRMATIONS
Ignore Cache: no INSIGHT_IGNORE_CACHE
# Bicoind Connection configuration:
RPC Username: hoshi BITCOIND_USER
RPC Password: Yes(hidden) BITCOIND_PASS
RPC Protocol: http BITCOIND_PROTO
RPC Host: 127.0.0.1 BITCOIND_HOST
RPC Port: 33441 BITCOIND_PORT
P2P Port: undefined BITCOIND_P2P_PORT
Data Dir: /home/hoshi BITCOIND_DATADIR
Change setting by assigning the enviroment variables in the last column. Example:
$ INSIGHT_NETWORK="testnet" BITCOIND_HOST="123.123.123.123" ./insight.js
info: starting...
insight server listening on port 3000 in development mode
info: Previous TIP is now orphan. Back to:undefined
/home/hoshi/insight/node_modules/insight-bitcore-api/lib/BlockDb.js:119
throw new Error('unable to get info for block:'+ hash);
^
Error: unable to get info for block:50cb40cc4e9fbd5297bcf8fc0743074e7f08b4d543d8b08705d627ee0ecde158
at /home/hoshi/insight/node_modules/insight-bitcore-api/lib/BlockDb.js:119:13
at /home/hoshi/insight/node_modules/insight-bitcore-api/lib/BlockDb.js:280:30
at /home/hoshi/insight/node_modules/insight-bitcore-api/lib/Rpc.js:98:40
at IncomingMessage.
(/home/hoshi/insight/node_modules/insight-bitcore-api/node_modules/bitcore/lib/RpcClient.js:203:7)
at IncomingMessage.EventEmitter.emit (events.js:117:20)
at _stream_readable.js:920:16
at process._tickCallback (node.js:415:13)
npm ERR! weird error 8
npm WARN This failure might be due to the use of legacy binary "node"
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian
npm ERR! not ok code 0
hoshi@NGC4826:~/insight$