The OctoPrint server is currently not running - Please Help!

Get Help
1

What is the problem?

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?

See above

Complete Logs

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

2

In the log, I noticed this error:

OSError: [Errno 28] No space left on device octoprint

So, after some more searching, I ran df -h and got this:

Filesystem      Size  Used Avail Use% Mounted on
/dev/root        59G   59G     0 100% /
devtmpfs        779M     0  779M   0% /dev
tmpfs           908M     0  908M   0% /dev/shm
tmpfs           908M  8.5M  900M   1% /run
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           908M     0  908M   0% /sys/fs/cgroup
/dev/mmcblk0p1  253M   48M  206M  19% /boot
tmpfs           182M     0  182M   0% /run/user/1000

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?

3

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.

4

Thanks - apologies in advance as my ignorance is going to show here, but I really appreciate any help you can give.

I ran ls -l /var/log and got this:

pi@octopi:~ $ ls -l /var/log
total 58835304
-rw-r--r-- 1 root root        7876 Nov  1 18:11 alternatives.log
drwxr-xr-x 2 root root        4096 Jan 28 22:52 apt
-rw-r----- 1 root adm         6559 Jan 31 11:21 auth.log
-rw-r----- 1 root adm        54034 Jan 30 23:17 auth.log.1
-rw-r----- 1 root adm         2127 Jan 23 23:17 auth.log.2.gz
-rw-r----- 1 root adm         2477 Jan 16 21:37 auth.log.3.gz
-rw-r--r-- 1 root root           0 Aug 20 05:47 bootstrap.log
-rw-rw---- 1 root utmp         768 Jan 28 23:04 btmp
-rw-r----- 1 root adm       103097 Jan 31 11:01 daemon.log
-rw-r----- 1 root adm      2121332 Jan 30 23:49 daemon.log.1
-rw-r----- 1 root adm       153399 Jan 24 00:00 daemon.log.2.gz
-rw-r----- 1 root adm       135413 Jan 17 01:48 daemon.log.3.gz
-rw-r----- 1 root adm         3450 Jan 31 10:43 debug
-rw-r----- 1 root adm        21761 Jan 30 16:49 debug.1
-rw-r----- 1 root adm          642 Jan 21 07:25 debug.2.gz
-rw-r----- 1 root adm          799 Jan 16 21:37 debug.3.gz
-rw-r--r-- 1 root root      157098 Jan 28 22:54 dpkg.log
-rw-r--r-- 1 root root       24048 Nov  1 18:12 faillog
-rw-r--r-- 1 root root         538 Nov  1 18:11 fontconfig.log
-rw-r----- 1 root adm        11218 Jan 31 10:47 haproxy.log
-rw-r----- 1 root adm      8386849 Jan 30 23:53 haproxy.log.1
-rw-r----- 1 root adm        84402 Jan 22 00:00 haproxy.log.10.gz
-rw-r----- 1 root adm       133911 Jan 20 23:58 haproxy.log.11.gz
-rw-r----- 1 root adm       561044 Jan 20 00:00 haproxy.log.12.gz
-rw-r----- 1 root adm       154064 Jan 19 00:00 haproxy.log.13.gz
-rw-r----- 1 root adm       688498 Jan 18 00:01 haproxy.log.14.gz
-rw-r----- 1 root adm       423176 Jan 17 01:48 haproxy.log.15.gz
-rw-r----- 1 root adm       240686 Jan 16 00:00 haproxy.log.16.gz
-rw-r----- 1 root adm       496978 Jan 15 00:00 haproxy.log.17.gz
-rw-r----- 1 root adm       253772 Jan 14 00:00 haproxy.log.18.gz
-rw-r----- 1 root adm       190259 Jan 13 00:00 haproxy.log.19.gz
-rw-r----- 1 root adm        25281 Jan 11 17:00 haproxy.log.20.gz
-rw-r----- 1 root adm       405629 Jan 30 00:00 haproxy.log.2.gz
-rw-r----- 1 root adm       655684 Jan 29 00:00 haproxy.log.3.gz
-rw-r----- 1 root adm       813014 Jan 28 00:00 haproxy.log.4.gz
-rw-r----- 1 root adm       412414 Jan 27 00:00 haproxy.log.5.gz
-rw-r----- 1 root adm       200388 Jan 26 00:00 haproxy.log.6.gz
-rw-r----- 1 root adm       516967 Jan 25 00:00 haproxy.log.7.gz
-rw-r----- 1 root adm       281401 Jan 24 00:00 haproxy.log.8.gz
-rw-r----- 1 root adm       417400 Jan 23 00:00 haproxy.log.9.gz
-rw-r----- 1 root adm  29233896637 Jan 31 10:43 kern.log
-rw-r----- 1 root adm    879983378 Jan 31 00:00 kern.log.1
-rw-r----- 1 root adm        27448 Jan 22 10:18 kern.log.2.gz
-rw-r----- 1 root adm        38395 Jan 16 21:37 kern.log.3.gz
-rw-rw-r-- 1 root utmp      292584 Jan 31 10:48 lastlog
-rw-r----- 1 root adm       105580 Jan 31 10:43 messages
-rw-r----- 1 root adm       628997 Jan 31 00:00 messages.1
-rw-r----- 1 root adm        32648 Jan 24 00:00 messages.2.gz
-rw-r----- 1 root adm        47128 Jan 17 01:48 messages.3.gz
drwxr-xr-x 2 root adm         4096 Nov  1 18:12 nginx
drwx------ 2 root root        4096 Aug 20 05:47 private
-rw-r--r-- 1 root root          61 Aug 20 05:47 regenerate_ssh_host_keys.log
-rw-r----- 1 root adm  29234648764 Jan 31 11:17 syslog
-rw-r----- 1 root adm    878901553 Jan 31 00:00 syslog.1
-rw-r----- 1 root adm        26571 Jan 30 00:00 syslog.2.gz
-rw-r----- 1 root adm       130812 Jan 29 00:00 syslog.3.gz
-rw-r----- 1 root adm       110094 Jan 28 00:00 syslog.4.gz
-rw-r----- 1 root adm        91081 Jan 27 00:00 syslog.5.gz
-rw-r----- 1 root adm        53435 Jan 26 00:00 syslog.6.gz
-rw-r----- 1 root adm        13809 Jan 25 00:00 syslog.7.gz
-rw-r----- 1 root adm         4080 Jan 31 10:43 user.log
-rw-r----- 1 root adm        34507 Jan 30 16:49 user.log.1
-rw-r----- 1 root adm         1285 Jan 22 10:18 user.log.2.gz
-rw-r----- 1 root adm         1662 Jan 16 21:37 user.log.3.gz
-rw-r--r-- 1 root root        7725 Jan 31 10:43 webcamd.log
-rw-r--r-- 1 root root       57997 Jan 30 16:49 webcamd.log.1
-rw-r--r-- 1 root root        1011 Jan 21 07:26 webcamd.log.2.gz
-rw-r--r-- 1 root root        1167 Jan 16 21:37 webcamd.log.3.gz
-rw-rw-r-- 1 root utmp       74880 Jan 31 10:48 wtmp

I don't know what any of that means nor do I know what can be deleted or how to delete it. Is the number before the date the file size?

5

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.

1 Like
6

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.

7

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.

8

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...

3 Likes
9

Thanks for all the advice and for hanging in there with a noob. I really appreciate it!