Fix common problems Error message: /var/log is getting full

[knowpistons]

I am getting the following error message from the fix common problems plug-in "/var/log is getting full (currently 54 % used) - Either your server has an extremely long uptime, or your syslog could be potentially being spammed with error messages. A reboot of your server will at least temporarily solve this problem, but ideally you should seek assistance in the forums and post your".  I got this error 3 days ago after my server was up for around 40 days now it is coming up again so it must be an issue.  I haven't really made any changes in the past week, any help would be very much appreciated. 

big-savy-diagnostics-20200811-1334.zip

[Squid]

You're being bombed by messages from the video card.  I'm assuming that you're passing through the card to one or more docker containers, but your nvidia plugin isn't up to date.  Update it and re-select 6.8.3 (nvidia) from its drop down.

[xxbigfootxx]

I've also got this issue on mine. Server has only been running for 2 days at this point. 

 

 du -sm /var/log/*
0       /var/log/btmp
0       /var/log/cron
0       /var/log/debug
1       /var/log/diskinfo.log
1       /var/log/dmesg
1       /var/log/docker.log
0       /var/log/faillog
0       /var/log/lastlog
1       /var/log/libvirt
1       /var/log/maillog
0       /var/log/messages
0       /var/log/nfsd
1       /var/log/nginx
1       /var/log/openvpnserver.log
0       /var/log/packages
0       /var/log/pkgtools
1       /var/log/plugins
0       /var/log/preclear.disk.log
0       /var/log/removed_packages
0       /var/log/removed_scripts
0       /var/log/removed_uninstall_scripts
1       /var/log/samba
0       /var/log/scripts
0       /var/log/secure
0       /var/log/setup
0       /var/log/spooler
0       /var/log/swtpm
1       /var/log/syslog
128     /var/log/syslog.1
1       /var/log/vfio-pci
1       /var/log/wtmp

 

I seem to have two syslog files, one that is named syslog1 that is using all the log memory. Can anyone tell me what that is?

zeus-diagnostics-20201009-2200.zip

[trurl]

After syslog "rolls over", a new syslog is created and the previous one is renamed syslog.1

 

Looks like the actual problem filling log is bad disk4 which you should replace.

 

Why aren't you asking about that instead???

 

Do any of your other disks show SMART warnings on the Dashboard page?

 

You must setup Notifications to alert you immediately by email or other agent as soon as a problem is detected. Don't let one unnoticed problem become multiple problems and data loss!!!