Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Octoprint crashes upon resuming print #3213
What were you doing?
While printing, clicking pause, results in a normal pause. When "resume" is pressed the entire octoprint crashes (goes offline).
What did you expect to happen?
Expected to pause a print, and go through my normal resume routine. Instead it resumed, and the octoprint server crashed. Repeated across 2 printers multiple times, all result in same problem.
What happened instead?
octoprint server crashed and doesn't really appear to record in either of the log file what happened.
Did the same happen when running OctoPrint in safe mode?
Will try first thing tomorrow.
Version of OctoPrint
Operating System running OctoPrint
Printer model & used firmware incl. version
Solidoodle press + Marlin flavor
Browser and version of browser, operating system running browser
Link to octoprint.log
Link to contents of terminal tab or serial.log
Screenshot(s)/video(s) showing the problem:
I have read the FAQ.
Please report back when this is clarified. It doesn't make sense to look into an issue if it's not verified that it's reproducible with stock OctoPrint.
Also please clarify what "crashes" means. Is the process gone (
Try running it manually from SSH:
This will start the server in your SSH session. It will log to the console (you can stop it again by hitting Ctrl+C). Reproduce the issue and check if it logs any kind of segfault or error that never made it into the log. Share the results.
We tested 3 machines in safe mode (5 prints on each), and the problem vanished! We flashed the card and installed a new copy, ran perfect without safe mode! As soon as we installed:
I will try your instructions and report back tomorrow:
Hm, that sounds like there's an issue with this particular plugin then. I'm going to close this ticket, however it would still make sense to run the tests (as you have planned anyhow) and report your findings in the ticket on the plugin's tracker that you already opened (
I'll also disable the plugin on the repository for now until this issue is clarified.