-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
LND crash on boot #3473
Comments
@stridentbean was this immediately after updating to 0.7.1? If so, do you know what version it upgraded from? If you have an SCB, then it would seem the user was at least on 0.6? It does look like db corruption tho, SCB will probably be the best path forward. Will continue to comb through and see if we can gleam anything |
Woops. This user has not updated to 0.7.1 yet, they were consistently running 0.7.0. Originally, bitcoind was corrupted and we had to resync bitcoind data from the cloud. While bitcoind was corrupted lnd was online and spinning on this
Then we turned off bitcoind and lnd resynced bitcoind to (-1k blocks from head) and restarted lnd. Maybe lnd was corrupted because we started it while bitcoind was behind where it was prior to the chainstate corruption? |
This scenario wouldn't cause this kind of corruption. Are bitcoind and lnd sharing the same disk? Could've been a disk issue given that both bitcoind and lnd were corrupted. |
Yes, they are on the same spinning disk HDD. It's certainly possible. |
Will go ahead and close this then. Keep in mind that the channels will be closed as part of the recovery process. Feel free to comment/reopen if you run into any issues. |
Background
We have a casa node user who's lnd instance is crashing on boot. It looks like it is happening even before lnd is unlocked. Meaning, as soon as the lnd container starts running.
We are going to recover the funds for this user via SCB. I'm assuming there is a database corruption somewhere. I wanted to drop the error logs in here on the off chance that it would be helpful.
Logs,
Your environment
The text was updated successfully, but these errors were encountered: