mirror of
https://github.com/monero-project/monero.git
synced 2024-10-01 11:49:47 -04:00
Instructions for debugging LMDB crashes taken from #1360
This commit is contained in:
parent
dbf2ab56c5
commit
67e910a1a0
17
README.md
17
README.md
@ -378,3 +378,20 @@ Note: rlwrap will save things like your seed and private keys, if you supply the
|
||||
|
||||
If you want to help out, see CONTRIBUTING for a set of guidelines.
|
||||
|
||||
# Debugging
|
||||
|
||||
This section contains general instructions for debugging failed installs or problems encountered with Monero. First ensure you are running the latest version built from the github repo.
|
||||
|
||||
## LMDB
|
||||
|
||||
Instructions for debugging suspected blockchain corruption as per @HYC
|
||||
|
||||
There is an `mdb_stat` command in the LMDB source that can print statistics about the database but it's not routinely built. This can be built with the following command:
|
||||
|
||||
`cd ~/monero/external/db_drivers/liblmdb && make`
|
||||
|
||||
The output of `mdb_stat -ea <path to blockchain dir>` will indicate inconsistencies in the blocks, block_heights and block_info table.
|
||||
|
||||
The output of `mdb_dump -s blocks <path to blockchain dir>` and `mdb_dump -s block_info <path to blockchain dir>` is useful for indicating whether blocks and block_info contain the same keys.
|
||||
|
||||
These records are dumped as hex data, where the first line is the key and the second line is the data.
|
||||
|
Loading…
Reference in New Issue
Block a user