March 27, 20224 yr On 10/22/2015 at 3:59 AM, trurl said: Nothing to clear, since /var/log is in RAM. Must be something with your configuration filling it up. Maybe boot in SAFE mode and see if it still happens. thanks to trurl's reminder, after I clear syslog the usage of log is back to normal. rm -rf syslog.* echo "" > syslog
March 27, 20224 yr Community Expert On 3/31/2021 at 9:58 PM, trurl said: This is a pretty old thread.... Filling log is usually a sign of some other problem that needs to be addressed.
September 15, 20223 yr Ich öffne das Terminal des Unraid-Servers und gebe folgendes ein: nano /boot/config/go Folgendes füge ich am Ende der Datei ein: mount -o remount,size=384m /var/log Strg-x, y, Enter Dann diesen soeben eingegebenen Befehl separat im Terminal noch einmal eingeben (somit spart man sich den Neustart): mount -o remount,size=384m /var/log Diese Informationen habe ich aus einem Wiki eines anderen Benutzers. Hier der komplette Link zum Wiki: https://knilixun.wordpress.com/ram-protokoll-auf-100/ Alles was nach der Zeile ######## kommt habe ich ebenfalls ausgeführt und scheint zu funktionieren. Edited September 15, 20223 yr by Fabian Hammer
May 18, 20233 yr Log full... Tools/Syslog: Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 4096 bytes) in /usr/local/emhttp/plugins/dynamix/include/Syslog.php on line 18 The /var/log/syslog.1 is going bananas. BTW, why "syslog.1"? master@SERVER:~# df -h /var/log Filesystem Size Used Avail Use% Mounted on tmpfs 128M 128M 0 100% /var/log master@SERVER:~# du -sm /var/log/* 1 /var/log/Xorg.0.log 0 /var/log/btmp 0 /var/log/cron 0 /var/log/debug 1 /var/log/dhcplog 1 /var/log/dmesg 1 /var/log/docker.log 0 /var/log/faillog 0 /var/log/lastlog 1 /var/log/libvirt 0 /var/log/maillog 0 /var/log/messages 0 /var/log/nfsd 1 /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 1 /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 122 /var/log/syslog.1 7 /var/log/unraid-api 1 /var/log/vfio-pci 1 /var/log/wtmp Edited May 18, 20233 yr by mizifih more information added from Tools/Syslog
May 18, 20233 yr syslog.1 is the rotated syslog (after syslog reaches "x" size, a new syslog is started and the old one gets labelled as syslog.1 (.2 .3 etc) To clear you have to reboot, but ultimately there is something being logged excessively indicating some sort of issue and posting your diagnostics would help
May 18, 20233 yr 10 minutes ago, Squid said: syslog.1 is the rotated syslog (after syslog reaches "x" size, a new syslog is started and the old one gets labelled as syslog.1 (.2 .3 etc) To clear you have to reboot, but ultimately there is something being logged excessively indicating some sort of issue and posting your diagnostics would help It's taking forever at syslog.1.txt, way more than usual. Got stuck at the line below. grep -Po 'file: \K[^"]+' '/savannah-diagnostics-20230518-0944/logs/syslog.1.txt' 2>/dev/null|sort|uniq Edited May 18, 20233 yr by mizifih
May 18, 20233 yr 43 minutes ago, Squid said: syslog.1 is the rotated syslog (after syslog reaches "x" size, a new syslog is started and the old one gets labelled as syslog.1 (.2 .3 etc) To clear you have to reboot, but ultimately there is something being logged excessively indicating some sort of issue and posting your diagnostics would help Yeah... It's stuck. Tried to solve it by stopping the Docker Service, but didn't work. And looks like my mover is going bananas as well, it's disabled because "mover is running", but my cache stays at 100%, even after stopping the Docker service. Edited May 18, 20233 yr by mizifih
June 2, 20233 yr On 5/18/2023 at 8:41 AM, Squid said: syslog.1 is the rotated syslog (after syslog reaches "x" size, a new syslog is started and the old one gets labelled as syslog.1 (.2 .3 etc) To clear you have to reboot, but ultimately there is something being logged excessively indicating some sort of issue and posting your diagnostics would help Did someone know where the answer is in this threat ???? And did someone knows how to find what is filling the logs ? bugz-diagnostics-20230602-1204.zip
June 2, 20233 yr Community Expert 12 minutes ago, Jimmy said: Did someone know where the answer is in this threat ???? Well, the "answer" is to reboot. That will clear log. But why does it fill? Lots of possible explanations. Your diagnostics are after reboot, so your log is already cleared. Would need to see diagnostics when you have the problem.
June 4, 20233 yr On 6/2/2023 at 12:12 PM, trurl said: Well, the "answer" is to reboot. That will clear log. But why does it fill? Lots of possible explanations. Your diagnostics are after reboot, so your log is already cleared. Would need to see diagnostics when you have the problem. Yes my bad, I will remake it when it will be at 100%.
June 16, 20233 yr On 6/2/2023 at 12:12 PM, trurl said: Well, the "answer" is to reboot. That will clear log. But why does it fill? Lots of possible explanations. Your diagnostics are after reboot, so your log is already cleared. Would need to see diagnostics when you have the problem. Did someone know where the answer is in this threat ???? And did someone knows how to find what is filling the logs ? Here are my Diag and my logs with the problem bugz-diagnostics-20230616-1139.zip bugz-syslog-20230616-1540.zip Edited June 19, 20233 yr by Jimmy
January 13, 20242 yr On 5/18/2023 at 8:41 AM, Squid said: syslog.1 is the rotated syslog (after syslog reaches "x" size, a new syslog is started and the old one gets labelled as syslog.1 (.2 .3 etc) To clear you have to reboot, but ultimately there is something being logged excessively indicating some sort of issue and posting your diagnostics would help Hello, I seem to also be having a concern with the GUI system log showing 100% I have been attempting to figure out where the concern may be. I have posted diagnostics to assist. Thank you. unraid-diagnostics-20240113-1058.zip
January 13, 20242 yr Community Expert Have you made sure you are up-to-date with the ‘connect’ plugin (if you are using it) as the last release was meant to clear an excessive logging issue.
January 13, 20242 yr 3 hours ago, itimpi said: Have you made sure you are up-to-date with the ‘connect’ plugin (if you are using it) as the last release was meant to clear an excessive logging issue. Hello, I previously installed all plugins (today) before I saw this concern happen.... 'connect' was one of them. Saw in the 'connect' release notes before pushing the plugin update, that there were changes to 'connect' due to community feedback. Once updated, I noted the system log went to 100% Edited January 13, 20242 yr by bombz
January 15, 20242 yr Community Expert The logs in your diagnostics are not large. What do you get from command line with this? du -h /var/log
January 15, 20242 yr 9 hours ago, trurl said: The logs in your diagnostics are not large. What do you get from command line with this? du -h /var/log Hello, Here is the output of the command: 0 /var/log/pwfail 127M /var/log/unraid-api 0 /var/log/preclear 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/nmbd 0 /var/log/samba/cores/smbd 0 /var/log/samba/cores 1.1M /var/log/samba 0 /var/log/plugins 0 /var/log/pkgtools/removed_uninstall_scripts 4.0K /var/log/pkgtools/removed_scripts 12K /var/log/pkgtools/removed_packages 16K /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 Appreciate your feedback, hope it helps with a resolution. Thank you.
January 15, 20242 yr Community Expert On 1/13/2024 at 11:06 AM, itimpi said: Have you made sure you are up-to-date with the ‘connect’ plugin (if you are using it) as the last release was meant to clear an excessive logging issue. Looks like this is the cause. Since you are on the latest version now, reboot and see if it happens again.
January 16, 20242 yr 14 hours ago, trurl said: Looks like this is the cause. Since you are on the latest version now, reboot and see if it happens again. 10-4 seems better now, had to pick an off-peek time to reboot, was considering performing a reboot sooner, and thought to add some info for the community, just incase :-) seems better now... 0 /var/log/pwfail 8.0K /var/log/unraid-api 0 /var/log/preclear 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/nmbd 0 /var/log/samba/cores/smbd 0 /var/log/samba/cores 36K /var/log/samba 0 /var/log/plugins 0 /var/log/pkgtools/removed_uninstall_scripts 4.0K /var/log/pkgtools/removed_scripts 4.0K /var/log/pkgtools/removed_packages 8.0K /var/log/pkgtools 4.0K /var/log/nginx 0 /var/log/nfsd 0 /var/log/libvirt/qemu 0 /var/log/libvirt/ch 0 /var/log/libvirt 428K /var/log Thank you again for your assistance! Edited January 16, 20242 yr by bombz
January 25Jan 25 My log is full, and I know why, because the massive log was deliberately activated for the dry run of my “Mover Tuning” plugin to test it. Now I have deactivated the log for it, but my log is still full.1. What can I do to empty or rotate the log during operation without having to restart?2. How can I increase the size of the log?Attached is my anonymized diagnostic and, in addition, my log:root@Alent:~# du -sm /var/log/* 0 /var/log/btmp 0 /var/log/cron 0 /var/log/debug 1 /var/log/dmesg 1 /var/log/docker.log 0 /var/log/faillog 0 /var/log/file.activity 0 /var/log/fileactivity-watcher.log 1 /var/log/fileactivity-watcher.log.1.gz 1 /var/log/fileactivity.log 1 /var/log/gitcount 1 /var/log/gitflash 1 /var/log/gitflash1 1 /var/log/graphql-api.log 0 /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 1 /var/log/phplog 11 /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 11 /var/log/samba 0 /var/log/scripts 0 /var/log/secure 0 /var/log/setup 0 /var/log/spooler 0 /var/log/swtpm 2 /var/log/syslog 21 /var/log/syslog.1 84 /var/log/syslog.2 2 /var/log/unbalanced.log 0 /var/log/unraid-api 0 /var/log/vfio-pci 0 /var/log/vfio-pci-errors 1 /var/log/wtmp alent-diagnostics-20260125-1430.zip Edited January 25Jan 25 by AceBurn90
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.