@peerchemist Ok so, I left my Pi synchronizing all the day while I was out of home.
I just came back and saw it gave me again the error I had last night:
System error: CDB() : can’t open database file wallet.dat, error -30973
I close this message, Peercoin auto-closes and then shows:
Runaway exception
A fatal error occurred. Peercoin can no longer continue safely and will quit.
EXCEPTION: St13runtime_error CDB() : can’t open database file wallet.dat, error -30973
Peercoin on runaway exception
After this I need to restart it and wait for rescanning.
I can’t everytime wait for it to crash after 40000 blocks/few hours and be there to manually restart it…
Can someone help me? I just want to stake in peace
Ok so the error is with the wallet.dat, which makes sense to happen after it was simply moved from elsewhere. That wallet.dat came from another Raspberry or from the PC?
@peerchemist
The very first wallet.dat has been exported (years ago) from Peercoin client in Windows and moved to the initial Peerbox in RaspberryPi.
A day ago I backed up the wallet.dat from the Peerbox (v0.6.1) to my Windows via WinSCP.
Then formatted the SD and installed Stakebox from scratch on the RaspberryPi, as suggested a few comments before, finally I moved the wallet.dat on the RaspberryPi again and started synching.
can you remove the current wallet.dat
and start up and let it sync with a newly but empty wallet.dat?
and when synced after a day or so, stop it and copy your backed up wallet to replace the empty one
The following is how I work with my addresses (not saying everybody should do this): I personally generated them, backed the private keys somewhere safe and imported them one by by one in wallet.dat just to prevent these issues…
After 24h of synching with the disk, the blocks are around 310k/421k, I guess by tomorrow at noon it will eventually be finised
Then I’ll figure out the wallet issue
Yup, I was surprised too. Didn’t remember it being so slow the first time I set it up withe old client. Will be able to tell you the SD card specs once it will have finished
Alright, so it finally synched everything.
Imported my private key with “importprivekey”, waited, looks like it has been imported correctly
1- I have set walletpassphrase with a high number. What else should I do?
2- I just focused on the part of the client where it says “This is a pre-release build”. Can I continue using this or what can I do?
3- If I check the setting “Start Peercoin on system login” and click apply, it then auto-unchecks
Yes, it’s just a problem with a git tag. You can safely ignore it.
Yeah, that is not likely to work on LXDE (UX for Raspberry Pi). They just had a major new release, I’ll see what have they done and try to make this work.
I synced on the v0.8 it was ok but not that’s fast (around 2 hours). Bootstrap file would be faster I guess.
I will try v0.8 on raspberry pi zero and see how it goes
I’ll make the .deb packages for it soon, waiting for bugfixes and few more “point releases”.
Provided linux binary on github should work as well, but mind that they use “compatibility” libdb and I’ll use modern one so the wallet.dat won’t be compatible with both.
I followed the steps on the topped thread to update from v0.7, but was unable to compile.
Are we able to update the Peercoin wallet on the RaspberryPi right now?
