2

Ran into the following when syncing:

2017-06-26 21:19:28.150 [P2P1]  ERROR   blockchain  src/cryptonote_core/blockchain.cpp:3383 Error adding block with hash:  to blockchain, what = Error adding spent key image to db transaction: MDB_MAP_FULL: Environment mapsize limit reached
2017-06-26 21:19:28.150 [P2P1]  WARN    blockchain.db.lmdb  src/blockchain_db/lmdb/db_lmdb.cpp:71   Failed to query m_blocks: MDB_BAD_TXN: Transaction must abort, has a child, or is invalid
2017-06-26 21:19:38.034 [P2P1]  WARN    blockchain.db.lmdb  src/blockchain_db/lmdb/db_lmdb.cpp:71   DB error attempting to fetch block index from hashMDB_BAD_TXN: Transaction must abort, has a child, or is invalid
2017-06-26 21:19:56.416 [P2P1]  WARN    blockchain.db.lmdb  src/blockchain_db/lmdb/db_lmdb.cpp:71   DB error attempting to fetch block index from hashMDB_BAD_TXN: Transaction must abort, has a child, or is invalid
2017-06-26 21:20:01.815 [P2P1]  WARN    blockchain.db.lmdb  src/blockchain_db/lmdb/db_lmdb.cpp:71   DB error attempting to fetch block index from hashMDB_BAD_TXN: Transaction must abort, has a child, or is invalid
2017-06-26 21:20:40.659 [P2P1]  WARN    blockchain.db.lmdb  src/blockchain_db/lmdb/db_lmdb.cpp:71   Failed to query m_blocks: MDB_BAD_TXN: Transaction must abort, has a child, or is invalid
^C

^C

Anyone else encounter this?

254123179
  • 4,586
  • 4
  • 32
  • 58
zanegray
  • 141
  • 6

1 Answers1

2

Your errors indicate that your blockchain is most likely corrupted. To resolve this issue you need to resync from scratch. This is done by deleting data.mdb from C:\ProgramData\bitmonero\lmdb (Windows) or $HOME/.bitmonero/lmdb (Linux and Mac OS X), which will trigger the resync.

To avoid corruptions make sure to always gracefully exit monerod.

dEBRUYNE
  • 15,417
  • 18
  • 60
  • 114