/var/log is getting full (currently 100 % used) ERROR

[RayRyu]

Hello,

I'm happy with my Unraid server, but I keep getting this error repeatedly. I've solved it by rebooting the server.

What should I do?

Thanks in advance.

ray-unraid-diagnostics-20230228-1141.zip

[itimpi]

It might be worth seeing what output you get with

du -sh /var/log/*

from the command line to see if the culprit can be identified.

[RayRyu]

51 minutes ago, itimpi said:

It might be worth seeing what output you get with

du -sh /var/log/*

from the command line to see if the culprit can be identified.

 

This timje, it shows as below :

0       /var/log/btmp
0       /var/log/cron
0       /var/log/debug
288K    /var/log/dmesg
8.0K    /var/log/docker.log
0       /var/log/faillog
0       /var/log/lastlog
20K     /var/log/libvirt
0       /var/log/maillog
0       /var/log/mcelog
0       /var/log/messages
0       /var/log/nfsd
0       /var/log/nginx
0       /var/log/packages
0       /var/log/pkgtools
0       /var/log/plugins
0       /var/log/pwfail
0       /var/log/removed_packages
0       /var/log/removed_scripts
0       /var/log/sa
52K     /var/log/samba
0       /var/log/scripts
0       /var/log/secure
0       /var/log/setup
0       /var/log/spooler
0       /var/log/swtpm
0       /var/log/syslog
128M    /var/log/syslog.1
0       /var/log/unraid-api
0       /var/log/vfio-pci
8.0K    /var/log/wtmp

 

So far, I've deleted syslog.1 but the error did occur again and again...

 

Edited February 28, 2023 by RayRyu

[itimpi]

The diagnostics you posted earlier showed a MUCH smaller syslog.1 file so I was thinking there might be another culprit.      I can only suggest that looking at the contents of that file might give a clue as I would guess there is some error sequence continually repeating.   It might be a case of zipping up a large version of that file (it should compress well) and posting that if you cannot work out for yourself what is happening.

[RayRyu]

This is "syslog.1"

syslog.1.zip