-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Internal serer error after reboot #1019
Comments
Ok, I thought I'd fixed this (it happened a couple of times during development but is very hard to reproduce), might be something new though too, hard to tell from the truncated log. Try If that doesn't help, you can disable the use of the webassets stuff by setting |
A reboot of of the pi seemed to fix it. |
If re-creation of the folder fails due to an access error, perform three retries. It might be caused by the folder being open in the file explorer. Waiting a bit before retrying seems to do the trick. See also #1019
I think the cause for this was both a lack of error resilience within the cache implementation of webassets and a possible timing issue when deleting the folder on server startup. I pushed 38be47c (and 0c44762) plus the above commits that should monkey patch webassets to be more forgiving when the cache cannot be read or written (that should then clear itself up further down the road in such situations I hope) and also made the folder reset a bit more intelligent (and resilient against win32 shenanigans I discovered while doing that). Is on I hope that takes care of this. |
I had a thermal runaway and I rebooted the octoprint server
I am getting internal server error at the webpage
1.2.4 latest from OctoPi 0.12 update
(if applicable - always include if unsure):
Rigidbot Marlin 1.0.2
System running Browser (if applicable - always
include if unsure):
Not relevant
(ALWAYS INCLUDE AND DO NOT TRUNCATE):
gist.github.com or pastebin.com (if applicable - always
include if unsure or reporting communication issues AND
DO NOT TRUNCATE):
on gist.github.com or pastebin.com or alternatively a
screenshot (if applicable - always include if unsure
or reporting UI issues):
Nope
include if unsure or reporting UI issues):
Its a boring picture
I have read the FAQ.
The text was updated successfully, but these errors were encountered: