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
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
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