This happened both on an older octopi 1.7 version and then again after updating everything to the very latest. The hardware is unchanged from a year ago when I last printed and everything was solid.
Not during a print it looks like the octoprint server crashes. Not the pi itself. I can still ssh into it but the webserver has crashed and consequently the print fails. Accessing the octoprint website shows the following error:
503 Service Unavailable
No server is available to handle this request.
Confirmed the octoprint daemon is no longer running.
Where can I start looking for logs or troubleshoot this? (answered)
I have checked the octopring.log and serial.log but don't see anything obvious. The octoprint.log file indicated communication is lost with the printer, but I think the webserver must have crashed first? There's nothing that looks odd to me in the serial.log file, it just ends. I've attached both files below along with the systeminfo bundle that I accessed after restarting octoprint.
No I have not since it doesn't strike me as a loading/bootup problem but rather something that seems to happen during a print. In fact, the Octoprint server seems to be stable for days unless a print is happening.
You can download this in OctoPrint's System Information dialog ... no bundle, no support!)
OctoPrint version, OctoPi version, printer, firmware, browser, operating system, ... as much data as possible