So here I am again, a different machine, same Raspberry Pi 3 setup, up to date on Octoprint and plugins...and 60% into a print, it just up and stopped.
Serial Log
I'm scrolling along and not sure what caused the failure.
I'm starting to loose confidence in Octoprint and I have 7 devices on 7 printers. They've never up and quit printing like this in over a year in operation. Help
Thank you, kindly
2019-12-10 23:28:55,170 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-10 23:29:25,246 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-10 23:17:09,545 - octoprint.startup - INFO - ******************************************************************************
2019-12-10 23:17:09,547 - octoprint.startup - INFO - Starting OctoPrint 1.3.12
2019-12-10 23:17:09,552 - octoprint.startup - INFO - ******************************************************************************
2019-12-10 23:17:09,652 - octoprint.startup - INFO - We don't appear to be online, not fetching plugin blacklist
2019-12-10 23:17:09,771 - octoprint.plugin.core - INFO - Loading plugins from /home/pi/oprint/lib/python2.7/site-packages/octoprint/plugins, /home/pi/.octoprint/plugins and installed plugin packages...
2019-12-10 23:17:12,931 - octoprint.plugin.core - INFO - Found 18 plugin(s) providing 18 mixin implementations, 27 hook handlers
2019-12-10 23:17:13,276 - octoprint.server.heartbeat - INFO - Starting server heartbeat, 900.0s interval
What precisely happened here? There are no clean shutdown messages in there for the server, it just suddenly continues with a startup log and the time stamps also jump. If that is you pulling power on the pi, it might explain issues you've been seeing because just pulling power is a pretty good way to corrupt the filesystem and cause various problems, one of which could cause things to just crash out of the blue.
Thank you for your reply
I went to the web console and the IP was not responding. My only alternative was the pull power and restart the device. Then try to see what happened in the logs.
Would the only fix be to replace the SD card with a new one? The one in there is a DSLR grade (fast, large) SD Card that has been in use since early 2018.
I think some have mentioned using a an actual SATA HDD but I wasn't sure how one would image that, etc? Replacing the SD seems the cheapest and quickest fix.