-
Notifications
You must be signed in to change notification settings - Fork 911
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Backup is out of date, we cannot continue safely. Emergency shutdown. #4994
Comments
There are two things here:
The latter can be addressed by removing the backup and re-initializing it. Can you report the |
@manelio Please could you also report |
Hi, I just did a clean shutdown and have the same issue after a reboot, Ubuntu 20. Not sure what to do. |
Was thinking of just moving the file.bkp and writing to a new backup file, but I'm not sure if that won't mess with the .lightning datadir... Edit, missed the part where you said "The latter can be addressed by removing the backup and re-initializing it". Edit2, worked, although I'm really fuzzy on python, unfortunately. |
Ok, seems it was indeed an older version of |
Not to reopen this, but I only yesterday read that lightningd has a built in backup functionality that can write to a second database. Is that the preferred way? Using the plugin now and plan to rewrite the backup file occasionally when the file becomes, lets say 3 or 4 times the .lightning dir size. |
Indeed there now is a litestream based option, but I have no idea how it works under the covers and I personally still prefer my backup plugin. I'll add the replay-to-secondary-db as an option too. |
I'm using lightningd via raspiblitz.
After restarting after a power failure lightningd is not running anymore.
When I try to start the service manually I receive an error message
Backup is out of date, we cannot continue safely. Emergency shutdown.
:Is there any way to fix this problem?
The text was updated successfully, but these errors were encountered: