bitcoind is crashing soon after start, how to fix ? centos linux

[btctousd81]

Hi,

i am running
bitcoind version v0.15.1
on
centos el7.x86_64

bitcoind is crashing soon after i start it.

here is my debug.log

Code:

2019-03-10 13:54:25 Bitcoin version v0.15.1
2019-03-10 13:54:25 InitParameterInteraction: parameter interaction: -listen=0 -> setting -upnp=0
2019-03-10 13:54:25 InitParameterInteraction: parameter interaction: -listen=0 -> setting -discover=0
2019-03-10 13:54:25 InitParameterInteraction: parameter interaction: -listen=0 -> setting -listenonion=0
2019-03-10 13:54:25 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2019-03-10 13:54:25 Assuming ancestors of block 0000000000000000003b9ce759c2a087d52abc4266f8f4ebd6d768b89defa50a have valid signatures.
2019-03-10 13:54:25 Setting nMinimumChainWork=000000000000000000000000000000000000000000723d3581fe1bd55373540a
2019-03-10 13:54:25 Using the 'standard' SHA256 implementation
2019-03-10 13:54:25 Default data directory /root/.bitcoin
2019-03-10 13:54:25 Using data directory /root/.bitcoin
2019-03-10 13:54:25 Using config file /root/.bitcoin/bitcoin.conf
2019-03-10 13:54:25 Using at most 100 automatic connections (1024 file descriptors available)
2019-03-10 13:54:25 Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2019-03-10 13:54:25 Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2019-03-10 13:54:25 Using 8 threads for script verification
2019-03-10 13:54:25 scheduler thread start
2019-03-10 13:54:25 HTTP: creating work queue of depth 128
2019-03-10 13:54:25 Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcuser for rpcauth auth generation.
2019-03-10 13:54:25 HTTP: starting 128 worker threads
2019-03-10 13:54:25 init message: Verifying wallet(s)...
2019-03-10 13:54:25 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2019-03-10 13:54:25 Using wallet wallet.dat
2019-03-10 13:54:25 CDBEnv::Open: LogDir=/root/.bitcoin/database ErrorFile=/root/.bitcoin/db.log
2019-03-10 13:54:25 Cache configuration:
2019-03-10 13:54:25 * Using 56.2MiB for block index database
2019-03-10 13:54:25 * Using 8.0MiB for chain state database
2019-03-10 13:54:25 * Using 385.8MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space)
2019-03-10 13:54:25 init message: Loading block index...
2019-03-10 13:54:25 Opening LevelDB in /root/.bitcoin/blocks/index
2019-03-10 13:54:25 Opened LevelDB successfully
2019-03-10 13:54:25 Using obfuscation key for /root/.bitcoin/blocks/index: 0000000000000000
2019-03-10 13:54:30 LoadBlockIndexDB: last block file = 1539
2019-03-10 13:54:30 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=59, size=58031043, heights=564293...564421, time=2019-02-23...2019-02-24)
2019-03-10 13:54:30 Checking all blk files are present...
2019-03-10 13:54:30 LoadBlockIndexDB: transaction index enabled
2019-03-10 13:54:30 Opening LevelDB in /root/.bitcoin/chainstate
2019-03-10 13:54:30 Opened LevelDB successfully
2019-03-10 13:54:30 Using obfuscation key for /root/.bitcoin/chainstate: 26026def1b5ceee9
2019-03-10 13:54:30 Loaded best chain: hashBestChain=000000000000000000086df0b3424771f04c9726fd2a12f94fda7b19e8cfe8b5 height=564347 date=2019-02-23 17:14:30 progress=0.989791
2019-03-10 13:54:30 init message: Rewinding blocks...
2019-03-10 13:54:32 init message: Verifying blocks...
2019-03-10 13:54:32 Verifying last 6 blocks at level 3
2019-03-10 13:54:32 [0%]...[16%]...[33%]...[50%]...2019-03-10 13:58:26

here is my bitcoind config file /root/.bitcoin/bitcoin.conf

Code:

daemon=1
server=1
txindex=1
rpcuser=user
rpcpassword=password
maxconnections=100
listen=0
forcednsseed=1
rpcworkqueue=128
rpcthreads=128
rpctimeout=220

there may have system crash due to sudden power outage in the past.

how can i fix this ?

Thanks

[1713563453]

1713563453

[1713563453]

1713563453

[1713563453]

1713563453

[1713563453]

1713563453

[DaveF]

Can you update to a newer version of bitconid?
15.2 or something in the 17 branch?
The version you are running is vulnerable to CVE 2018-17144 https://nvd.nist.gov/vuln/detail/CVE-2018-17144

Either way it looks like something in the DB is corrupted.

Backup your wallet file (you are doing that anyway right???), remove the blockchain data and re-download.

-Dave

[btctousd81]

Can you update to a newer version of bitconid?
15.2 or something in the 17 branch?
The version you are running is vulnerable to CVE 2018-17144 https://nvd.nist.gov/vuln/detail/CVE-2018-17144

Either way it looks like something in the DB is corrupted.

Backup your wallet file (you are doing that anyway right???), remove the blockchain data and re-download.

-Dave

i dont have any active wallet, i just use this to parse full blockchain in mysqld.

which directory data should i remove , so it will start downloading blockchain again ?

/root/.bitcoin/blocks  ?
/root/.bitcoin/chainstate

Code:

$ ls -lah
total 21M
drwxr-xr-x.  5 root root  280 Feb 24 14:28 .
dr-xr-x---. 26 root root 4.0K Feb 12 11:54 ..
-rw-------.  1 root root   37 Feb 23 07:29 banlist.dat
-rw-r--r--.  1 root root  848 Jan  8  2018 bitcoin.conf
-rw-------.  1 root root    6 Mar 10 19:28 bitcoind.pid
drwx------.  3 root root  76K Feb 24 12:58 blocks
drwx------.  2 root root  40K Mar 10 19:28 chainstate
drwx------.  2 root root   28 Feb 24 14:29 database
-rw-------.  1 root root    0 Dec 27  2017 db.log
-rw-------.  1 root root 9.8M Mar 10 19:28 debug.log
-rw-------.  1 root root 243K Feb 24 13:01 fee_estimates.dat
-rw-------.  1 root root    0 Dec 27  2017 .lock
-rw-------.  1 root root  50K Feb 24 13:01 mempool.dat
-rw-------.  1 root root 4.6M Feb 24 13:01 peers.dat
-rw-------.  1 root root 4.2M Dec 29  2017 peers.dat.bak
-rw-------.  1 root root 440K Dec 29  2017 peers.dat.bak.1
-rw-------.  1 root root 1.4M Feb 24 19:53 wallet.dat

thanks

[ABCbits]

which directory data should i remove , so it will start downloading blockchain again ?

/root/.bitcoin/blocks  ?
/root/.bitcoin/chainstate

You only need to delete /root/.bitcoin/blocks

You might want to delete chainstate (which contain all UTXO) and txindex (which contain all transaction index) folder as well since both of them will be recreated anyway and just in case if those two are corrupted as well.

[btctousd81]

which directory data should i remove , so it will start downloading blockchain again ?

/root/.bitcoin/blocks  ?
/root/.bitcoin/chainstate

You only need to delete /root/.bitcoin/blocks

You might want to delete chainstate (which contain all UTXO) and txindex (which contain all transaction index) folder as well since both of them will be recreated anyway and just in case if those two are corrupted as well.

thanks.,

i cleaned

/root/.bitcoin/blocks
/root/.bitcoin/chainstate

and started bitcoind.,

now its started to download blocks.,

[DaveF]

thanks.,

i cleaned

/root/.bitcoin/blocks
/root/.bitcoin/chainstate

and started bitcoind.,

now its started to download blocks.,

Did it finish the sync / download? Is it working or still crashing?
 
-Dave

[btctousd81]

thanks.,

i cleaned

/root/.bitcoin/blocks
/root/.bitcoin/chainstate

and started bitcoind.,

now its started to download blocks.,

Did it finish the sync / download? Is it working or still crashing?
 
-Dave

sorry i forgot to update.

bitcoind is up and running, didnt crashed once since i cleaned up blocks directory and started bitcoind.

blocks are still being downloaded , current getinfo shows

blocks : 487116

so i guess, it will take a day or two to finish.

thanks