Update to 1.41 - froze after successful update (20h) - service not running - Dashboard plugin?!

Hi there my Octoprint stopped working after the update 1.41.

What is the problem?

After the update / upgrade to 1.41 everything worked fine for about 20h. Than my Raspberry Pi (3B) froze completely inclusive SSH access. So I powercycled all. I guess that's part of the problem. No I just got the warning "The OctoPrint server is currently not running". So the webserver and ssh server is up and running.

What did you already try to solve it?

I tryed to restart the process without success. and checked to logs. But I am bit confuesed with the info message:
2020-08-05 13:16:18,088 - octoprint.plugins.dashboard - INFO - cmd_results: 9V
So I guess I need to disable the dashboard plugin - but how?

Complete Logs

2020-08-05 12:50:58,972 - octoprint.plugins.dashboard - INFO - cmd_results: 9V
2020-08-05 12:51:02,167 - octoprint.plugins.dashboard - INFO - cmd_results: 9V
2020-08-05 12:51:05,248 - octoprint.plugins.dashboard - INFO - cmd_results: 9V
2020-08-05 12:51:09,557 - octoprint.plugins.dashboard - INFO - cmd_results: 9V
2020-08-05 12:51:09,727 - octoprint.plugins.enclosure - INFO - Failed to execute python scripts, try disabling use SUDO on advanced section of the plugin.
2020-08-05 12:51:09,728 - octoprint.plugins.enclosure - WARNING - An exception o f type ValueError occurred on log_error. Arguments:
('need more than 1 value to unpack',)
2020-08-05 12:51:12,625 - octoprint.plugins.dashboard - INFO - cmd_results: 9V

In case you'll need the whole log - let me know.

Additional information about your setup

Custom build printer
running Klipper
Raspberry Pi3b - new SD card - orginal Raspberry Pi PSU

In the meantime I removed the Dashboard package - no success.

Can you post the full logs, as they contain information about the underlying environment that is useful - could be something completely different, info messages don't usually mean something's wrong. Just drop the whole octoprint.log file here

octo.zip (1.3 MB)

ok added the last logs

I take it you are seeing this screen when trying to connect?

What happens when you run the commands suggested there?

What happens when you run

~/oprint/bin/octoprint serve --debug

Hi foosel,

yes you're right I can see the screen you shared.

If I check for a running python process there is no return at all. I checked also with "top/htop". And there is a python process and the mjpeg stream process but I can see the octoprint one. So I tried to restart the octoprint service unfortunately without success.

I tried you command:

~/oprint/bin/octoprint serve --debug


2020-08-06 11:01:46,938 - octoprint.settings - ERROR - Could not write test file to /home/pi/.octoprint/logs
Traceback (most recent call last):
  File "/home/pi/oprint/local/lib/python2.7/site-packages/octoprint/settings.py", line 1855, in _validate_folder
    f.write("test")
IOError: [Errno 28] No space left on device
2020-08-06 11:01:46,941 - octoprint.startup - CRITICAL - Could not initialize settings manager: Folder at /home/pi/.octoprint/logs doesn't appear to be writable, please fix its permissions
2020-08-06 11:01:46,941 - octoprint.startup - CRITICAL - There was a fatal error starting up OctoPrint.
Could not initialize settings manager: Folder at /home/pi/.octoprint/logs doesn't appear to be writable, please fix its permissions
There was a fatal error starting up OctoPrint.

Since your command basiclly said my disc is full I also share my disk usage

Filesystem     1K-blocks     Used Available Use% Mounted on
/dev/root       29768896 29658444         0 100% /
devtmpfs          443140        0    443140   0% /dev
tmpfs             447748        0    447748   0% /dev/shm
tmpfs             447748     6076    441672   2% /run
tmpfs               5120        4      5116   1% /run/lock
tmpfs             447748        0    447748   0% /sys/fs/cgroup
/dev/mmcblk0p1    258095    52238    205857  21% /boot
tmpfs              89548        0     89548   0% /run/user/1000

So I guess I just have to delete to old logs or somehow get some space free?!

Thank you for your help

edit
It seems this is the error which flooded my kern.log and the syslogas well
"brcmfmac: brcmf_sdio_htclk: HT Avail request error: -5"

Yeah, you need to clean up some stuff. I suggest to take a look at your uploads and your timelapse folder, logs should clean up after themselves usually. A full file system will mean that OctoPrint can't work.

1 Like

Thank you @foosel

My Octoprint is up again. I just deleted a few logs and one timelapse (50Mb). Can I do something to prevent this from happening in the future?

BTW Thanks for your help I really love your work. Expect a tip ;-D

Not much apart from keeping an eye on your file usage. OctoPrint reports the amount of free space beneath the file list.

1 Like