Difference between revisions of "Common Sync Problems"
| Line 10: | Line 10: | ||
But first please find debug.log | But first please find debug.log | ||
| − | In the last few line is you see a message like this ( | + | In the last few line is you see a message like this (example block number can be different for you) |
2019-04-23 13:10:37 ProcessMessages(headers, 162003 bytes) FAILED peer=7 | 2019-04-23 13:10:37 ProcessMessages(headers, 162003 bytes) FAILED peer=7 | ||
| Line 25: | Line 25: | ||
You will notice block 00000000002158a02ae3f4b042ca1ef526a5469a545043f185e2a6a7a0a0eb1b is the problem | You will notice block 00000000002158a02ae3f4b042ca1ef526a5469a545043f185e2a6a7a0a0eb1b is the problem | ||
| − | Just type in the console this command | + | Just type in the console this command (example block number can be different for you) |
reconsiderblock 00000000002158a02ae3f4b042ca1ef526a5469a545043f185e2a6a7a0a0eb1b | reconsiderblock 00000000002158a02ae3f4b042ca1ef526a5469a545043f185e2a6a7a0a0eb1b | ||
That will unblock the wallet syncing issue because we permanently marks the block as invalid, as if it violated a consensus rule. | That will unblock the wallet syncing issue because we permanently marks the block as invalid, as if it violated a consensus rule. | ||
Revision as of 00:45, 6 May 2019
An occasional problem when updating your wallet from an old version is that it gets stuck on a block during sync and will not get past it. To fix it, make sure you are using the latest Ritocoin release. Make sure the wallet is not running. Now start it this way:
In Windows, open a cmd prompt. (Start menu, Run, "cmd"). Do cd \"Program Files"\Rito and then press enter. Now do rito-qt.exe -reindex and press enter. That will cause your wallet to reindex from the beginning and should resolve your problem.
In Linux, it is simpler. Just run ```rito-qt -reindex``` from the terminal.
If after all of this your wallet sync is still stuck on a particular block height we may need to use a spacial command in the wallet console (reconsiderblock)
But first please find debug.log
In the last few line is you see a message like this (example block number can be different for you)
2019-04-23 13:10:37 ProcessMessages(headers, 162003 bytes) FAILED peer=7 2019-04-23 13:10:37 ERROR: AcceptBlockHeader: block 00000000002158a02ae3f4b042ca1ef526a5469a545043f185e2a6a7a0a0eb1b is marked invalid 2019-04-23 13:10:37 ERROR: invalid header received 2019-04-23 13:10:37 ProcessMessages(headers, 162003 bytes) FAILED peer=0 2019-04-23 13:10:37 ERROR: AcceptBlockHeader: block 00000000002158a02ae3f4b042ca1ef526a5469a545043f185e2a6a7a0a0eb1b is marked invalid 2019-04-23 13:10:37 ERROR: invalid header received 2019-04-23 13:10:37 ProcessMessages(headers, 162003 bytes) FAILED peer=1 2019-04-23 13:10:38 ERROR: AcceptBlockHeader: block 00000000002158a02ae3f4b042ca1ef526a5469a545043f185e2a6a7a0a0eb1b is marked invalid 2019-04-23 13:10:38 ERROR: invalid header received 2019-04-23 13:10:38 ProcessMessages(headers, 162003 bytes) FAILED peer=2
You will notice block 00000000002158a02ae3f4b042ca1ef526a5469a545043f185e2a6a7a0a0eb1b is the problem
Just type in the console this command (example block number can be different for you)
reconsiderblock 00000000002158a02ae3f4b042ca1ef526a5469a545043f185e2a6a7a0a0eb1b
That will unblock the wallet syncing issue because we permanently marks the block as invalid, as if it violated a consensus rule.
