Hi there, I'm getting this message in Fix Common Problems with my syslog getting to 100%.  I've rebooted a few times to clear the syslog but within a day or two the log is back to 100%. 

"/var/log is getting full (currently 66 % 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 Diagnostics."

 

Attached is my diagnostics.  I'm clueless on how to resolve without rebooting.  Any help would be appreciated, thanks!

unraid-diagnostics-20240112-1511.zip

Try booting in safe mode and/or closing any browser windows open to the GUI, only open when you need to use it then close again.

I been having the same issue and can't track down and thing. Log is at 100$ cpu was maxing out while watch movie on Plex, and only one stream going. I have 3 streams going before and never had an issue. Have netdata but really dont  understand everything I'm reading.

conwayserver-diagnostics-20240119-1947.zip

Running the command

du -h /var/log

Should identify the culprit.

 

if you have the Connect plugin installed then are you up-to-date as the last update fixed an excessive logging issue, and have you rebooted since then to reset the log space?

Hello I'm having the same problem.

Here are my diagnostics and the results of "du -h /var/log".

root@Orion:~# du -h /var/log
0       /var/log/pwfail
0       /var/log/preclear
0       /var/log/unraid-api
0       /var/log/.pm2/modules
4.0K    /var/log/.pm2/pids
0       /var/log/.pm2/logs
24K     /var/log/.pm2
0       /var/log/swtpm/libvirt/qemu
0       /var/log/swtpm/libvirt
0       /var/log/swtpm
0       /var/log/samba/cores/rpcd_winreg
0       /var/log/samba/cores/rpcd_classic
0       /var/log/samba/cores/rpcd_lsad
0       /var/log/samba/cores/samba-dcerpcd
0       /var/log/samba/cores/winbindd
0       /var/log/samba/cores/smbd
0       /var/log/samba/cores
136K    /var/log/samba
0       /var/log/sa
0       /var/log/pm2
0       /var/log/plugins
0       /var/log/pkgtools/removed_uninstall_scripts
24K     /var/log/pkgtools/removed_scripts
2.7M    /var/log/pkgtools/removed_packages
2.7M    /var/log/pkgtools
8.0K    /var/log/nginx
0       /var/log/nfsd
0       /var/log/libvirt/qemu
0       /var/log/libvirt/ch
0       /var/log/libvirt
128M    /var/log
root@Orion:~#

orion-diagnostics-20260326-2010.zip

Here are the results of du -sm /var/log/*

root@Orion:~# du -sm /var/log/*
0       /var/log/btmp
0       /var/log/cron
0       /var/log/debug
1       /var/log/dhcplog
1       /var/log/dmesg
0       /var/log/docker.log
0       /var/log/faillog
1       /var/log/graphql-api.log
1       /var/log/lastlog
0       /var/log/libvirt
0       /var/log/maillog
0       /var/log/messages
0       /var/log/nfsd
1       /var/log/nginx
0       /var/log/packages
3       /var/log/pkgtools
0       /var/log/plugins
0       /var/log/pm2
0       /var/log/preclear
0       /var/log/pwfail
0       /var/log/removed_packages
0       /var/log/removed_scripts
0       /var/log/removed_uninstall_scripts
0       /var/log/sa
1       /var/log/samba
0       /var/log/scripts
0       /var/log/secure
0       /var/log/setup
0       /var/log/spooler
0       /var/log/swtpm
125     /var/log/syslog
1       /var/log/tailscale-utils.log
1       /var/log/tailscale.log
0       /var/log/unraid-api
0       /var/log/vfio-pci
0       /var/log/vfio-pci-errors
1       /var/log/wtmp
root@Orion:~#

I tried truncating it and increasing the size but it keeps filling up.

root@Orion:/var/log# mount -t tmpfs tmpfs /var/log -o size=8G,remount
root@Orion:/var/log# truncate -s 0 /var/log/syslog
root@Orion:/var/log# du -h /var/log
0       /var/log/pwfail
0       /var/log/preclear
0       /var/log/unraid-api
0       /var/log/.pm2/modules
4.0K    /var/log/.pm2/pids
0       /var/log/.pm2/logs
24K     /var/log/.pm2
0       /var/log/swtpm/libvirt/qemu
0       /var/log/swtpm/libvirt
0       /var/log/swtpm
0       /var/log/samba/cores/rpcd_winreg
0       /var/log/samba/cores/rpcd_classic
0       /var/log/samba/cores/rpcd_lsad
0       /var/log/samba/cores/samba-dcerpcd
0       /var/log/samba/cores/winbindd
0       /var/log/samba/cores/smbd
0       /var/log/samba/cores
144K    /var/log/samba
0       /var/log/sa
0       /var/log/pm2
0       /var/log/plugins
0       /var/log/pkgtools/removed_uninstall_scripts
24K     /var/log/pkgtools/removed_scripts
2.7M    /var/log/pkgtools/removed_packages
2.7M    /var/log/pkgtools
8.0K    /var/log/nginx
0       /var/log/nfsd
0       /var/log/libvirt/qemu
0       /var/log/libvirt/ch
0       /var/log/libvirt
6.5G    /var/log

Your screenshots do not show what is taking up the 6.5GB in /var/log mentioned in the last screenshot. Whatever it is is almost certainly the problem.

What command do I run to find out what eating all the space in /var/log?

I ran "tail -f /var/log/syslog" and it looks like this entry just keep repeating.


Mar 26 20:50:19 Orion kernel: get_swap_device: Bad swap file entry 3fff7ffffffff

orion-diagnostics-20260326-2057.zipAttaching another diagnostic file.

What do you get from command line with this?

ls -lah /var/log

After we figure this out I recommend you put logspace back to its normal size. 8G is not a fix.

16 hours ago, trurl said:

After we figure this out I recommend you put logspace back to its normal size. 8G is not a fix.

What is it's normal size?