What does that anacron error message "no space left on device" mean

hulmul · 23. Januar 2023

Hi,

since a couple of weeks i receive weekly error messages from anacron via email. But i did't understand where that error message is from, and how to handle it.

Code

/etc/cron.daily/openmediavault-cron-apt:
cat: write error: No space left on device

/usr/sbin/cron-apt: 119: printf: printf: I/O error
fold: write error: No space left on device
sendmail: fatal: root(0): No recipient addresses found in message header

I have enough space left on my raspberry. I even could not remember that i set up such a job. Checking my configuration in webgui of omv I could not found such menu.

So I would be happy if you can give me a hint, what to do with that error email.

Greets

raulfg3 · 24. Januar 2023

revise your free space on boot device.

votdev · 24. Januar 2023

Please run df -h as root user and post the output here.

hulmul · 24. Januar 2023

Zitat von votdev

Please run df -h as root user and post the output here.

Code

root@raspberrypi:/home/pi# df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/root        59G  6.0G   50G  11% /
devtmpfs        3.7G     0  3.7G   0% /dev
tmpfs           3.9G  4.0K  3.9G   1% /dev/shm
tmpfs           1.6G  167M  1.4G  11% /run
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           3.9G  8.0K  3.9G   1% /tmp
/dev/mmcblk0p1  253M   50M  203M  20% /boot
folder2ram      3.9G  3.9G     0 100% /var/log
/dev/sda1       3.6T  2.0T  1.7T  54% /srv/dev-disk-by-uuid-156236b9-5cb4-4d02-8                                                                               e7c-521bda3e034f
folder2ram      3.9G     0  3.9G   0% /var/tmp
folder2ram      3.9G  1.4M  3.9G   1% /var/lib/openmediavault/rrd
folder2ram      3.9G  2.3M  3.9G   1% /var/spool
folder2ram      3.9G   19M  3.9G   1% /var/lib/rrdcached
folder2ram      3.9G  4.0K  3.9G   1% /var/lib/monit
folder2ram      3.9G   32K  3.9G   1% /var/cache/samba
tmpfs           790M     0  790M   0% /run/user/1000

Alles anzeigen

Seems that /var/log is 100 % in use. Which is weired because ls -h shows me that only 29 MB of are used in that directory.

Soma · 24. Januar 2023

Zitat von hulmul

Seems that /var/log is 100 % in use.

On the services flash memory GUI, click sync all and see if it clears

hulmul · 7. Mai 2023

Zitat von Soma

On the services flash memory GUI, click sync all and see if it clears

Forgot the feedback. Yes ist worked fine for me.

Sean · 19. August 2023

I have the same problem, but even after the sync, I still get:

Code

Filesystem                                 Size  Used Avail Use% Mounted on
folder2ram                                 8.3G  8.3G     0 100% /var/log

When I click "sync all", it claims to sync /var/log:

Code

will now sync all mountpoints
sync of /var/log successful!
sync of /var/tmp successful!
sync of /var/lib/openmediavault/rrd successful!
sync of /var/spool successful!
sync of /var/lib/rrdcached successful!
sync of /var/lib/monit successful!
sync of /var/cache/samba successful!

Why is the ram disk still full?

And anyway, regularly syncing manually is not a real solution IMO... Isn't there a way to make sure that the ram disk is synced reguarly?

macom · 19. August 2023

Your /var/log folder is quite big. You should check why the logs are getting spammed.

Sean · 19. August 2023

Here's the content of /var/log:

Code

-rw-r--r--   1 root    root                  3456 Aug 18 12:20 alternatives.log
drwxr-xr-x   2 root    root                   100 Aug 17 13:06 apt
-rw-r-----   1 root    adm                 217088 Aug 19 11:17 auth.log
-rw-r-----   1 root    adm                 269141 Aug 13 00:00 auth.log.1
-rw-r-----   1 root    adm                  11574 Aug  6 00:00 auth.log.2.gz
-rw-r--r--   1 root    root                     0 Jul 24 12:07 bootstrap.log
-rw-rw----   1 root    utmp                   768 Aug  8 15:44 btmp
drwxr-x---   2 _chrony _chrony                 40 Jul 31 11:10 chrony
drwxr-xr-x   2 root    root                   120 Aug 13 00:00 cron-apt
-rw-r-----   1 root    adm             2444763136 Aug 19 11:09 daemon.log
-rw-r-----   1 root    adm             1198425414 Aug 13 00:00 daemon.log.1
-rw-r-----   1 root    adm               49760225 Aug  6 00:00 daemon.log.2.gz
-rw-r-----   1 root    adm                   2732 Aug 18 12:20 debug
-rw-r-----   1 root    adm                   7842 Aug  9 16:33 debug.1
-rw-r-----   1 root    adm                   2221 Aug  3 11:38 debug.2.gz
-rw-r--r--   1 root    root                 54829 Aug 17 13:06 dpkg.log
-rw-r--r--   1 root    root                 32160 Aug  7 17:14 faillog
-rw-r--r--   1 root    root                     0 Jul 24 12:07 fontconfig.log
drwxr-xr-x   3 root    root                   160 Jul 31 11:07 installer
drwxr-sr-x+  3 root    systemd-journal         60 Jul 31 11:10 journal
-rw-r-----   1 root    adm                 111932 Aug 18 19:41 kern.log
-rw-r-----   1 root    adm                 330875 Aug 11 16:34 kern.log.1
-rw-r-----   1 root    adm                 163110 Aug  5 11:17 kern.log.2.gz
-rw-rw-r--   1 root    utmp                293460 Aug 19 10:02 lastlog
-rw-r-----   1 root    adm                  12288 Aug 19 08:23 mail.info
-rw-r-----   1 root    adm                  19662 Aug 11 13:03 mail.info.1
-rw-r-----   1 root    adm                  14110 Aug  3 11:03 mail.info.2.gz
-rw-r-----   1 root    adm                  12288 Aug 19 08:23 mail.log
-rw-r-----   1 root    adm                  19662 Aug 11 13:03 mail.log.1
-rw-r-----   1 root    adm                  14110 Aug  3 11:03 mail.log.2.gz
-rw-r-----   1 root    adm                 303104 Aug 19 11:17 messages
-rw-r-----   1 root    adm                 602901 Aug 12 23:17 messages.1
-rw-r-----   1 root    adm                 199783 Aug  5 23:17 messages.2.gz
-rw-r-----   1 root    adm                      0 Jul 24 12:07 monit.log
drwxr-xr-x   2 root    adm                    460 Aug 19 00:00 nginx
-rw-rw-rw-   1 root    root                  7981 Aug 19 03:01 omv-backup.log
drwxr-xr-x   2 root    root                    40 Jul 13 13:14 openmediavault
-rw-------   1 root    root                   338 Aug 18 12:20 php7.4-fpm.log
-rw-------   1 root    root                   902 Aug  9 16:33 php7.4-fpm.log.1
-rw-------   1 root    root                   367 Aug  3 11:00 php7.4-fpm.log.2.gz
drwx------   2 root    root                    40 Jul 31 11:10 private
-rw-r-----   1 root    adm                      0 Aug 14 00:00 rsync.log
-rw-r--r--   1 root    root                471289 Aug 13 11:40 rsync.log.1.gz
drwxr-xr-x   3 root    root                    60 Jul 31 11:05 runit
drwxr-xr-x   2 root    root                    80 Aug  6 00:00 salt
drwxr-x---   3 root    adm                    880 Aug 19 08:47 samba
-rw-rw-rw-   1 root    root                  1220 Aug 11 12:32 snapraid.log
-rw-r-----   1 root    adm             2445213696 Aug 19 11:17 syslog
-rw-r-----   1 root    adm             1199227538 Aug 13 00:00 syslog.1
-rw-r-----   1 root    adm               50046040 Aug  6 00:00 syslog.2.gz
-rw-r--r--   1 root    root                     0 Jul 24 12:07 tallylog
-rw-r-----   1 root    adm                  12288 Aug 19 08:23 user.log
-rw-r-----   1 root    adm                  30469 Aug 12 08:23 user.log.1
-rw-r-----   1 root    adm                  10549 Aug  5 08:19 user.log.2.gz
-rw-rw-r--   1 root    utmp                 34944 Aug 19 10:02 wtmp

Alles anzeigen

syslog and daemon.log contain a lot of entries from backup jobs (USBbackup apparently enumerates every single file).

macom · 19. August 2023

You can delete the *.gz and *.log.1 files. Those are rotated files and less important than the current ones, which I would not delete.

Do you run the USBBackup plugin frequently, or was this an exceptional case?

macom · 19. August 2023

Or the initial run? Then future runs should create less output. You can also enable the "quite" option in the GUI of the plugin.

Sean · 19. August 2023

You guessed right, it was an initial run (after OMV reinstallation). Thanks for this! I run it manually, about once per month, so it shouldn't be a permanent problem.

However, I'm still wondering why the ramdisk is still full after syncing, and what I can do to ensure that the ramdisk is synced (and purged) more frequently and regularly. Any hints?

macom · 19. August 2023

A sync is just syncing the content on the filesystem with the content in RAM. After you deleted files on the filesystem, it might not be reflected in the ram and a sync will take care of this. But I am not sure about it. Try.

If you are worried, you can run the sync as scheduled job.

folder2ram -syncall

Sean · 19. August 2023

OK, it worked now. I'm down to 70% usage now; let's hope that the size of the logfiles becomes smaller over time. (I just wonder why syncing helped hulmul...)

Thanks again for your help!

macom · 19. August 2023

He only hat 29MB of logs.

Zitat von Sean

let's hope that the size of the logfiles becomes smaller over time

Logs are rotated by "logrotate".

What does that anacron error message "no space left on device" mean

Jetzt mitmachen!

Tags