-
Notifications
You must be signed in to change notification settings - Fork 117
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
Loopd becomes unresponsive after some time #767
Comments
Thanks for raising the issue @Jossec101. Have you been running this setup for a while or did this behavior recently just appear or did you upgrade any versions of your stack? |
Nope, we have running loopd for more than 1 year upgrading from time to time to newer versions, recently we just started to see this behaviour. |
Are you using sqlite or PostgreSQL? If PostgreSQL, could you please provide the version that your interfacing with? |
SQLite |
Wiping up the db fixed this issue, it looks to be a corruption over time |
Thanks for the heads-up @Jossec101. If I understand correctly you're referring to filesystem corruption? Did you identify the source of the corruption? Or do you maybe mean that the DB file itself was changed outside of |
I mean that we stopped loopd, moved the sqlite to a safe place and loopd recreated a new one and that solved the issue. |
It happened again today, bump |
Did you get the same error as reported in #767 (comment) ? |
Yes, and and the db actually corrupted after a few hours since last comment but we upgraded to loop 0.28, I will report back if it happens again |
It has happened again, actually the frequency between db corruptions is increasing 🤔 |
I believe it may not be a DB corruption but perhaps a Go sqlite bug as it seemingly fails to parse the timestamp value. Do you still have your DB? Perhaps could you do a select and see what publication deadlines are there? Or if you could share the DB with me, I'm happy to take a look. I'm on both Keybase and Slack. |
Hey!
After some time (we have not measured how much yet), our loop is having issues doing loop outs, getinfo breaks as in the log below:
Additionally, invoking loop out gives this error:
It somehow resolves if we kill
loopd
and some swaps got broadcast onchainSystem information
Versions:
LND 0.17.5 and loop 0.27.1 for amd64 linux containers on kubernetes (AWS)
The text was updated successfully, but these errors were encountered: