Closed AlexVN74 closed 2 years ago
Probably a DB corruption. It might work with --db-salvage The actual error isn't shown on that log fwiw.
--db-salvage doesn't help :( How can I get the reason of monerod stopped work?
The reason is most likely a corrupted DB. What filesystem and OS variant are you using ? Monero is now supposed to switch to a "safe" mode once the initial blockchain is synced. I guess this did not work :/
I'm using docker image builded from official Dockerfile. Host server running on Ubuntu 16.04.4 LTS, file system for blockchain DB is ext4.
That might be the reason: https://github.com/monero-project/monero/pull/3876 It looks like safe mode was not being set.
Is it possible to repair database? Or I have to start new node with empty DB?
If --db-salvage did not work, I don't think you can recover it without expert lmdb knowledge.
Ok, thx. Will start from empty blockchain. But it's strange that log has completely no information why monerod stoped working. Last lines with --log-level 4:
2018-05-29 19:48:08.443 7f55ab68bbc0 TRACE blockchain.db.lmdb src/blockchain_db/lmdb/db_lmdb.cpp:2874 BlockchainLMDB::block_txn_stop
2018-05-29 19:48:08.443 7f55ab68bbc0 TRACE blockchain.db.lmdb src/blockchain_db/lmdb/db_lmdb.cpp:1683 BlockchainLMDB::for_all_txpool_txes
2018-05-29 19:48:08.444 7f55ab68bbc0 TRACE blockchain.db.lmdb src/blockchain_db/lmdb/db_lmdb.cpp:2820 BlockchainLMDB::block_rtxn_start
and no errors in log
Yes, that is odd. Are you sure it's the end of the log ? The logs rotate, so it might be the end of that particular file only.
Yes, I'm sure it's the end of log. It seems monerod stoped when init mempool in line 512 of cryptonote_core.cpp: r = m_mempool.init(max_txpool_size);
Closing due to inactivity and this looking like simple blockchain corruption.
I'm using monerod in docker container for several weeks, but after unexpected power down it can't start again without any errors in log. Here is log with default log level:
and last lines with log level 4: