Octopi crashing and pausing print. no access

What is the problem?

Octoprint will work fine and flawlessly for several hours or even days, but then it'll just stopp responding, pause the print, and leave the hot end running. The way I know it crashes is that the UI stops responding and says that its offline and will not come back (this normally happens when im not there or asleep so it can just be sitting and cooking the filament for hours).

I've been here before trying to fix this same issue and it seemed fixed and fine. I installed a new creality v4.2.7 board and reflashed the octopi from scratch and it was stable for a while until yesterday around time stamp 2021-01-29 13:53:20,812 and again around 2021-01-30 06:11:51,476 when the pi just.... stopped. I dont see any errors in the logs it just seems to decide to not be connected to anything and stop running.

What did you already try to solve it?

Reflashed from 0.17 to latest 0.18, updated all plugins, performed:

sudo apt-get update --fix-missing
sudo apt-get upgrade
sudo reboot

enabled "wait for start on connect" in serial connection

Have you tried running in safe mode?


Did running in safe mode solve the problem?

too random to tell. might wait an hour or 2 days. cant see anything in the logs

Complete Logs

octoprint.log, serial.log or output on terminal tab at a minimum, browser error console if UI issue ... no logs, no support! Not log excerpts, complete logs.)

octoprint (8).log (736.4 KB)

Additional information about your setup

OctoPrint version, OctoPi version, printer, firmware, browser, operating system, ... as much data as possible

Version 0.18.0, running on Raspberry Pi 4 Model B Rev 1.4
Version 1.5.3

browser.user_agent : Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.96 Safari/537.36 Edg/88.0.705.53
connectivity.connection_check :
connectivity.connection_ok : true
connectivity.enabled : true
connectivity.online : true
connectivity.resolution_check : octoprint.org
connectivity.resolution_ok : true
env.hardware.cores : 4
env.hardware.freq : 1500
env.hardware.ram : 1771343872
env.os.bits : 32
env.os.id : linux
env.os.platform : linux
env.plugins.pi_support.model : Raspberry Pi 4 Model B Rev 1.4
env.plugins.pi_support.octopi_version : 0.18.0
env.plugins.pi_support.throttle_state : 0x0
env.python.pip : 20.3.3
env.python.version : 3.7.3
env.python.virtualenv : true
octoprint.safe_mode : false
octoprint.version : 1.5.3
printer.firmware : Marlin bugfix-2.0.x (Jan 29 2021

here is where it crashed:
2021-01-29 13:53:13,580 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2021-01-29 13:53:20,812 - octoprint.plugins.tracking - INFO - Sent tracking event ping, payload: {'octoprint_uptime': 5394}
2021-01-29 14:08:13,582 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2021-01-29 14:08:20,847 - octoprint.plugins.tracking - INFO - Sent tracking event ping, payload: {'octoprint_uptime': 6294}
2021-01-29 13:32:06,157 - octoprint.startup - INFO - ******************************************************************************
2021-01-29 13:32:06,159 - octoprint.startup - INFO - Starting OctoPrint 1.5.3
2021-01-29 13:32:06,165 - octoprint.startup - INFO - ******************************************************************************
2021-01-29 13:32:12,543 - octoprint.util.connectivity.connectivity_checker - INFO - Connectivity state is currently: offline

not having the PiOS system logs makes it hard to tell, but I would expect to see this if power failed/was disconnected. the time being earlier when it comes back up is a function of the fakehwclock scripts that save date and time to a file every so often. with a normal shutdown, they save as it shuts down. if not shut down, and a power outage etc takes it down, the time can be a bit off. it will come back to current time after it reconnects to the internet and the NTP daemon corrects the time. I know this doesn't help much, as it doesn't show exactly why, but its a start.