error during OMV 6 version update: "dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device"

Searching the forum didn't give hits, maybe its a new error.

OMV6.0.6 reported a "new version available" so I started "Upgrade system" and get many error messages:

Processing triggers for openmediavault (6.0.7-1) ...

dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device

root cause is filesystem folder2ram is 100% full, how would I fix this?

I thought log files would be cleaned up automatically

Currently the docs for v6  are not available (error: SORRY This page does not exist yet.)

Searching for folder2ram on Wiki gave no hits either.

pi@nas64-6:~ $ df

Filesystem 1K-blocks Used Available Use% Mounted on

/dev/root 30406220 3273672 25867424 12% /

devtmpfs 1777356 0 1777356 0% /dev

tmpfs 1943052 0 1943052 0% /dev/shm

tmpfs 777224 89300 687924 12% /run

tmpfs 5120 4 5116 1% /run/lock

tmpfs 1943052 56 1942996 1% /tmp

/dev/mmcblk0p1 258095 30393 227702 12% /boot

folder2ram 1943052 1943052 0 100% /var/log

pi@nas64-6:/var/log $ ls -l

total 1106804

-rw-r--r-- 1 root root 208 Jan 2 14:24 alternatives.log

-rw-r--r-- 1 root root 5262 Dec 31 01:05 alternatives.log.1

-rw-r--r-- 1 root root 857 Nov 28 23:23 alternatives.log.2.gz

drwxr-xr-x 2 root root 180 Jan 4 14:41 apt

-rw-r----- 1 root adm 28672 Jan 4 15:09 auth.log

-rw-r----- 1 root adm 91748 Dec 31 01:05 auth.log.1

-rw-r----- 1 root adm 7926 Dec 18 19:28 auth.log.2.gz

-rw-r--r-- 1 root root 0 Oct 30 14:43 bootstrap.log

-rw-rw---- 1 root utmp 0 Jan 2 13:37 btmp

-rw-rw---- 1 root utmp 800 Dec 30 21:23 btmp.1

drwxr-x--- 2 _chrony _chrony 40 Nov 28 22:37 chrony

drwxr-xr-x 2 clamav clamav 80 Nov 28 23:05 clamav

drwxr-xr-x 2 root root 100 Jan 3 17:37 cron-apt

-rw-r----- 1 root adm 348160 Jan 4 15:08 daemon.log

-rw-r----- 1 root adm 933158 Jan 2 13:38 daemon.log.1

-rw-r----- 1 root adm 75530 Dec 19 16:13 daemon.log.2.gz

-rw-r----- 1 root adm 1531 Jan 2 14:24 debug

-rw-r----- 1 root adm 10826 Dec 31 01:05 debug.1

-rw-r----- 1 root adm 2370 Dec 18 19:28 debug.2.gz

-rw-r--r-- 1 root root 0 Jan 4 14:42 dpkg.log

-rw-r--r-- 1 root root 27157 Dec 30 20:28 dpkg.log.1

-rw-r--r-- 1 root root 12877 Nov 28 23:10 dpkg.log.2.gz

-rw-r--r-- 1 root root 32064 Dec 18 16:20 faillog

-rw-r--r-- 1 root root 484 Nov 28 22:36 fontconfig.log

drwxr-sr-x+ 4 root systemd-journal 80 Nov 28 22:29 journal

-rw-r----- 1 root adm 40960 Jan 4 11:15 kern.log

-rw-r----- 1 root adm 278450 Dec 31 01:05 kern.log.1

-rw-r----- 1 root adm 56013 Dec 18 19:28 kern.log.2.gz

-rw-rw-r-- 1 root utmp 296592 Jan 4 14:42 lastlog

-rw-r----- 1 root adm 1864 Jan 4 14:17 mail.info

-rw-r----- 1 root adm 481 Dec 31 00:17 mail.info.1

-rw-r----- 1 root adm 315 Dec 18 19:17 mail.info.2.gz

-rw-r----- 1 root adm 1864 Jan 4 14:17 mail.log

-rw-r----- 1 root adm 481 Dec 31 00:17 mail.log.1

-rw-r----- 1 root adm 315 Dec 18 19:17 mail.log.2.gz

-rw-r----- 1 root adm 535744512 Jan 4 15:09 messages

-rw-r----- 1 root adm 20709743 Dec 31 01:05 messages.1

-rw-r----- 1 root adm 8318561 Dec 18 19:28 messages.2.gz

drwxr-xr-x 2 minidlna minidlna 80 Dec 19 16:13 minidlna

-rw-r----- 1 root adm 353 Nov 28 22:40 monit.log

drwxr-xr-x 2 root adm 280 Jan 4 00:00 nginx

drwxr-xr-x 2 root root 40 Nov 26 13:15 openmediavault

-rw-r--r-- 1 root root 357 Dec 22 14:52 phoronix-test-suite-benchmark.log

-rw------- 1 root root 337 Jan 2 14:24 php7.4-fpm.log

-rw------- 1 root root 2023 Dec 31 01:05 php7.4-fpm.log.1

-rw------- 1 root root 407 Dec 18 19:28 php7.4-fpm.log.2.gz

drwx------ 2 root root 40 Oct 30 14:43 private

drwxr-xr-x 2 root root 100 Dec 19 16:13 proftpd

drwxr-xr-x 3 root root 60 Oct 30 14:30 runit

drwxr-xr-x 2 root root 100 Dec 31 00:00 salt

drwxr-x--- 3 root adm 360 Jan 4 12:33 samba

-rw-r----- 1 root adm 536096768 Jan 4 15:09 syslog

-rw-r----- 1 root adm 21664980 Jan 2 13:38 syslog.1

-rw-r----- 1 root adm 8432049 Dec 19 16:13 syslog.2.gz

-rw-r--r-- 1 root root 0 Nov 28 22:39 tallylog

-rw-r----- 1 root adm 8192 Jan 4 08:17 user.log

-rw-r----- 1 root adm 3916 Dec 31 01:05 user.log.1

-rw-r----- 1 root adm 381 Dec 18 19:28 user.log.2.gz

drwxr-xr-x 2 root root 40 Jan 3 2020 watchdog

-rw-rw-r-- 1 root utmp 38000 Jan 4 14:42 wtmp

pi@nas64-6:/var/log $

right that cured the issue, I wonder if log files can be configured to limit their size.

The real root cause was SMB file access auditing was enabled and I performed massive file moves over the last 2 days.

As the result log files grew to a size never seen before and exhausted all available space on file system folder2ram

Zitat von ryecoaaron

Look in /etc/logrotate.d/.

The config for syslog seems in /etc/logrotate.d/rsyslog.

But there are only basic settings unrelated to size.

Would you happen to know if adding a size 100M and change frequency from weekly to daily would prevent this issue?

pi@nas64-6:/etc/logrotate.d $ cat rsyslog

/var/log/syslog

/var/log/mail.info

/var/log/mail.warn

/var/log/mail.err

/var/log/mail.log

/var/log/daemon.log

/var/log/kern.log

/var/log/auth.log

/var/log/user.log

/var/log/lpr.log

/var/log/cron.log

/var/log/debug

/var/log/messages

{

rotate 4

weekly

missingok

notifempty

compress

delaycompress

sharedscripts

postrotate

/usr/lib/rsyslog/rsyslog-rotate

endscript

}

pi@nas64-6:

Zitat von ryecoaaron

If you are going to do a lot of logging, you shouldn't be using tmpfs for storage.

Well, it wasn't intentional. I'd see it as a "side effect" of the install script or flash media plugin in combination with debugging a file share access issue and forgetting to reset SMB auditing after fixing this issue.
It resulted in Web GUI access issues, hence I wonder if adding a size limit would "harden" OMV against this type of user error (that happens UNintentional BUT occasionally).

What is your view?