From 67e910a1a069ef958ba06f19c4d4a02f5607691d Mon Sep 17 00:00:00 2001 From: NanoAkron Date: Mon, 21 Nov 2016 23:00:20 +0000 Subject: [PATCH] Instructions for debugging LMDB crashes taken from #1360 --- README.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/README.md b/README.md index 321c9c3da..3545dfb37 100644 --- a/README.md +++ b/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 ` will indicate inconsistencies in the blocks, block_heights and block_info table. + +The output of `mdb_dump -s blocks ` and `mdb_dump -s block_info ` 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.