I set up Octoprint a few weeks ago and everything has been running just fine but suddenly this morning, I get "The OctoPrint server is currently not running" error. It was working just fine last night before I went to bed, but it's down this morning.
What did you already try to solve it?
I've looked on here for help but haven't found anything that gets me back up and running.
Following the instructions on the page that loads, it says to verify that the process is running: ps -ef | grep -i octoprint | grep -i python - but nothing happens when I enter this command. I've tried rebooting with no luck as well.
Have you tried running in safe mode?
I don't know how to. I tried running octoprint safemode but it says command not found. I'm sure this is my error, but I'm new to this so need some hand holding here.
Did running in safe mode solve the problem?
Octoprint Log - 1.31.21.zip (14.0 KB)
I tried to paste the log here, but it wouldn't let me post (over the character limit) so I hope I'm doing this right. Let me know if I need to share this some other way...
Additional information about your setup
OctoPrint 1.5.3, Raspberry SC15184 Pi 4 Model B 2019, Ender 5 Pro, Marlin 2.0, Google Chrome, Mac OSX 11.1
So, it looks like my card is full but I have no idea how. I've never done a timelapse (just got my camera set up a few days ago for monitoring, but haven't started any timelapses yet). What might cause this and how do I fix it?
This is probably an annoying problem with the wifi chip, funnily enough. If you head into the filesystem, under /var/log/ you will likely find the files that have used up the space - the wifi on the Pi4 can produce a ton of errors, and use every bit of space to log them.
You can delete the old logs (with dates or 1 or 2 etc after them) or the current ones, to try and free up some space. Running ls -l /var/log will show you what's there, and the file sizes so you can delete them. I can't off the top of my head remember the commands to show the largest files.
Yes - you have two massive syslog and kern.log files.
Delete them using sudo rm /var/log/syslog and sudo rm /var/log/kern.log then reboot the Pi. If the issue comes back, you will have a problem (most likely with the wifi driver/chip) that would need to be sorted. Sometimes it is a one-off.
Thank you! That got me up and running again - really appreciate your help.
Do I need to clear the other files out? Is there a way to ensure the log files don't grow to be that massive again? I only set this up 2-3 weeks ago so I don't want to be doing this again in 2-3 weeks if I can help it.
They all turned up in one day by the looks of it - the OS will rotate the files to make sure that they don't build up over a long period of time. If it happens again, try and find some way to read the files and see what it is complaining about. Most of the time it is one-off errors in the wifi stuff, which don't come back. If they do come back, then maybe you have bad software/drivers or bad hardware.
Make sure to run sudo apt update and sudo apt upgrade so you get the latest bugfixes in packages etc. You're running OctoPi 0.18, so it is pretty recent but it never hurts to upgrade.
Sorry, I'm late to the party, but a good diagnostic for a full card is something like:: sudo du -a / | sort -n -r | head -n 20
which will list the 20 biggest files and directories which usually points to the problem...