July 4th:
Wallet V4.0 has been staking well for the last several months, but after a recent system reboot, the wallet is constantly locking up / "not responding" Any help?
Update July 5th:
So, looking into this more, I believe it is on the correct chain, although, according to the debug.log, the wallet seems to be struggling to keep up with the newest block. It doesn't seem to ever catch up to the newest block, it is behind by 3 to 5 blocks. As soon as I lock the wallet, it runs flawlessly and keeps up with the current/correct block instantly.
Leave it running locked a few hours, then check. Is in the correct block?
Yes -> Unlock it and report what happens. (how many transactions do you have?)
No -> Make a copy of wallet.dat and download the bootstrap
Ran for 2 hours while locked and stayed on the correct block all the way
Unlocked and wallet started locking up almost immediately - backed up wallet.dat - implementing the bootstrap
After using the bootstrap and several hours to bring the wallet up-to-date, it is now staking again. While it was updating, the balance was zero, even though by the date the bootstrap was created,it should have had a balance of xx, so I replaced the wallet.dat with an archived backup. Which leads me to believe the wallet.dat was damaged somehow.
Word of caution: everyone should have one or more backup of their wallet.dat.The wallet is staking but still locking up / non-responsive, just not as much. I have never noticed this behavior prior to July 4, 2018. It almost seems like it is peer related, like an outdated or misbehaving peer. but I can't be sure.
Rw13enlib88, I am in your debt. Thank you!
