diff options
author | Riccardo Spagni <ric@spagni.net> | 2016-11-24 12:59:27 +0200 |
---|---|---|
committer | Riccardo Spagni <ric@spagni.net> | 2016-11-24 12:59:27 +0200 |
commit | b1a5d4bd5ddfc1284b02159b5c2d78a88fa6ed30 (patch) | |
tree | 0a7f9ee685e68c8bbc10b2ff6ce90b1af4621070 | |
parent | Merge pull request #1364 (diff) | |
parent | Instructions for debugging LMDB crashes taken from #1360 (diff) | |
download | monero-b1a5d4bd5ddfc1284b02159b5c2d78a88fa6ed30.tar.xz |
Merge pull request #1366
67e910a Instructions for debugging LMDB crashes taken from #1360 (NanoAkron)
-rw-r--r-- | README.md | 17 |
1 files changed, 17 insertions, 0 deletions
@@ -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. |