-
-
Notifications
You must be signed in to change notification settings - Fork 65
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
Docker v3.29 crashing #228
Comments
Rolled back to 3.28.0 in the meantime, back to functioning normally. |
Arf it was working fine when testing... |
Debian 11, Docker 20.10.16, Docker compose 2.5.0 |
From the compose file:
|
Amd64? |
Yes |
I tested the uploaded 3.29.0 image, it works fine for me. Do you have more information? Does it crash only when the web interface is accessed? Does it crash at the very beginning? |
same issue here after update to the last image version. After quick investigation, I have this entry in my host syslog (the DB UPDATER came from the container, after that it's a kernel issue) :
Note the container is restarting, without accessing to the web interface |
Thanks for the valuable information! Indeed I managed to reproduce this by just launching a scan |
I solved this by throwing away the DB. If you're not attached to the metadata you can try this and 3.29 will work. |
Unfortunately since starred tracks can't be exported I can't part with the DB. |
Yes, just stick to 3.28.0, we will eventualy figure out what is wrong with this 3.29.0. |
I repushed the |
I can confirm that the crash no longer happens with the new image. I've restored my old DB from a backup to test this and made sure that it fails again, before I pulled the new image. LMS is now up and running again, with my old metadata intact. 🙂 |
Hope this will be possible soon with #163 |
Can confirm it's fixed now. Cool theme! :D |
After updating to the latest release there are the following log errors, LMS later exits with code 139:
The text was updated successfully, but these errors were encountered: