Yesterday evening (14 Jul) I checked on a print that had been running for a couple of hours to find the hot end stationary on the print. The printer's (CR-10S) display showed nothing untoward showing the print as 20% completed and both heaters still on. I then checked my PC and switched to the Octopi tab to find the message that Octoprint was not running. pressing the re-connect button had no effect and I was unable to cancel the message. I closed the browser tab and attempted a fresh connection and received the message that Octoprint was not running and gave me the suggestion to check whether Python? was running on the Raspberry Pi. (3B with Raspberry's 2.5a power supply).
I logged into the Pi using SSH without issue and pasted the suggested command. This brought back nothing suggesting that Python? was not running. I then attempted to restart Octoprint using suggested command. This too produced no output and nor was I able to connect using my PC.
At this point I decided to pursue the matter the next morning and shutdown the Raspberry with the sudo shutdown now command. I then powered down the Raspberry and PC, switched off the printer and retired.
This morning I have removed the SD card and backed it up (disk copy) using Win32DiskImager and then started the Pi again and am able to connect with my PC. I then thought I would check the Octoprint log and decided to download it. There wasn't a log dated for yesterday but there was one dated for 13th. At this point I did something unbelievably stupid and hit the delete icon instead of the download icon. My eyes take a while to acclimatise in the mornings and the icons are very small. May I suggest a confirmation be added to the delete option.
I'm guessing there's not much can be done to investigate why my Octoprint failed after running pretty much non-stop since 15 May. Unless there's an un-delete option on the Pi somewhere.
Did you do a df -h to see what disk space there was left on the card? Having run that long its possible that log files could have filled the card. What size card are you using?
16Gb. The list of log files extended to two pages. There were only about 6 or 8 Octoprint.logs. It seemed to me that a new was created daily and were deleted automatically because there were none as old as the length of time the Pi has been in use. I don't keep timelapses or gcode files on the Pi. I delete gcode files once printed and delete timelapses once downloaded.
The chip has BCM2837IFBG printed on. If this means it's a + then that does not reflect what I ordered. I ordered the 3B thinking this was the latest version on 16 May. The amazon page said "Raspberry Pi 3 Official Desktop Starter Kit (16Gb, Black)" with this image.
I have just bought a second 16GB SD card and will restore the backup I took on the morning after the event. That backup should contain the octoprint log that I accidentally zapped. I'll post again later.
Here's the octoprint.log for the hang. I tried to upload the serial.log but it was too big. It doesn't seem to have any clues as to what happened it just froze mid print. Here's the last few lines of the serial.log.
