since the last 2 Updates i have sporadic crashes and freezes. So i check the log-files:
only one line in the log file was noticeable:
octoprint.plugins.pi_support - WARNING - Fetching the current throttle state via "/usr/bin/vcgencmd get_throttled" doesn't work.
and recently after the last Update i have a pop-up-message with a not to this problem:
And the OP only crashes if i print via OP. If i print from SD-Card i have no crashes, and can watch the print with the cam for hours. noting happens. SO i guess theres a problem with the PI, the OS or OP. But no clue, because theres no nice logfile-info.
OctoPrint version, OctoPi version, printer, firmware, browser, operating system, ... as much data as possible
OP Version 1.7.3
Octopi: Version 1.0.0, running on Raspberry Pi 4 Model B Rev 1.4
printer is a Ender v3 Pro
FW ist Marlin 2.0.8.2
Browser Google Chrome
Did the same issues occur on the stable OctoPi build? Since you are testing a new OS image here it would make sense to rule out that being the problem.
thank the for he requst.
so I know, i did not change anything and have no clue since when this version is on my system.
Normaly i only check for updates and let them install. this is no conscious adaptation i did.
could it be, that this version was active from the start of using OP?
The OctoPi 1.0.0 release candidate was only published a couple of days ago, so if you have been using 1.0.0 for longer than that then you must have installed a development nightly build at some point. I have no idea when you would have done that. You also have the 64 bit variant of it, which is different than the 32 bit one and may have more issues. I would recommend using the stable 0.18 to test with.
OctoPrint cannot check for throttling situations reported by your Pi. vcgencmd doesn't work as expected. Make sure the system user OctoPrint is running under is a member of the "video" group.
Also tried to install /OctoPrint-USBRelayControl-master.zip to address USB Camera - Failed
I had the same issues. I don't know too much on what to do, I just originally followed the instructions given when I had to upgrade from a previous version that wasn't using the latest python. So I guess I will have to find directions on how to go back to a different version.
To anyone getting this message on OctoPi 1.0.0, especially 64bit
This is a known issue on the OctoPi release candidate and will be fixed in the next one, please stop reporting this issue here. Only report a problem if you are seeing it with the stable OctoPi 0.18.0.
Now that works you get the warning.