When I leave my printer idle for a while (more than 15 mins) Octoprint often can no longer connect. to my printer. Prusa MK3. If I reboot my Pi, it connects no problem.
Is this a normal timeout? How do I stop it?
What did you already try to solve it?
Looked at logs, nothing popped out at me, but I suck at understanding logs....
Have you tried running in safe mode?
No
Systeminfo Bundle
browser.user_agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/110.0
connectivity.connection_check: 1.1.1.1:53
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.0
env.hardware.ram: 8204619776
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_check_enabled: True
env.plugins.pi_support.throttle_check_functional: True
env.plugins.pi_support.throttle_state: 0x0
env.python.pip: 20.3.3
env.python.version: 3.7.3
env.python.virtualenv: True
octoprint.last_safe_mode.date: 2022-06-05T14:29:21Z
octoprint.last_safe_mode.reason: incomplete_startup
octoprint.safe_mode: False
octoprint.version: 1.8.6
printer.firmware: Prusa-Firmware 3.12.1 based on Marlin
systeminfo.generated: 2023-02-21T17:54:31Z
systeminfo.generator: zipapi
Additional information about your setup
Prusa MK3s, Firmware 3.12.1-5686, Firefox on Windows 11, PrusaSlicer 2.5.0+win64-202209060714
Then I assume you have the worst case: A corrupted file structure of the SD card of the Pi.
...
2023-02-21 11:25:00,385 - octoprint.util.comm - ERROR - Something crashed inside the serial connection loop, please report this in OctoPrint's bug tracker:
Traceback (most recent call last):
File "/home/pi/oprint/lib/python3.7/site-packages/octoprint/util/comm.py", line 2515, in _monitor
self._handle_ok()
File "/home/pi/oprint/lib/python3.7/site-packages/octoprint/util/comm.py", line 3208, in _handle_ok
self._continue_sending()
File "/home/pi/oprint/lib/python3.7/site-packages/octoprint/util/comm.py", line 3429, in _continue_sending
elif job_active and self._send_from_job():
File "/home/pi/oprint/lib/python3.7/site-packages/octoprint/util/comm.py", line 4092, in _send_from_job
line, pos, lineno = self._get_next_from_job()
File "/home/pi/oprint/lib/python3.7/site-packages/octoprint/util/comm.py", line 4072, in _get_next_from_job
self._callback.on_comm_print_job_done()
File "/home/pi/oprint/lib/python3.7/site-packages/octoprint/printer/standard.py", line 1654, in on_comm_print_job_done
thread.start()
File "/usr/lib/python3.7/threading.py", line 847, in start
_start_new_thread(self._bootstrap, ())
RuntimeError: can't start new thread
...
Yeah there's issues with your system somewhere. Safe mode is definitely worth a try as well to make sure a plugin is not interfering - it looks like sometimes it runs out of memory as well which definitely should not happen on your Pi.