skunk

root@Tower:~# ls -lh /var/log total 96K -rw------- 1 root root 0 Feb 15 17:12 btmp -rw-r--r-- 1 root root 0 Apr 28 2021 cron -rw-r--r-- 1 root root 0 Apr 28 2021 debug -rw-r--r-- 1 root root 84K Apr 11 21:23 dmesg -rw-r--r-- 1 root root 2.1K Apr 12 06:02 docker.log -rw-r--r-- 1 root root 0 Feb 13 2021 faillog -rw-r--r-- 1 root root 0 Apr 7 2000 lastlog drwxr-xr-x 4 root root 140 Apr 12 06:02 libvirt/ -rw-r--r-- 1 root root 0 Apr 28 2021 maillog -rw-r--r-- 1 root root 0 Apr 11 21:23 mcelog -rw-r--r-- 1 root root 0 Apr 28 2021 messages drwxr-xr-x 2 root root 40 Aug 10 2022 nfsd/ drwxr-x--- 2 nobody root 60 Apr 11 21:23 nginx/ lrwxrwxrwx 1 root root 24 Feb 15 17:11 packages -> ../lib/pkgtools/packages/ drwxr-xr-x 5 root root 100 Apr 11 21:23 pkgtools/ drwxr-xr-x 2 root root 280 Apr 11 21:23 plugins/ drwxr-xr-x 2 root root 60 Apr 11 21:23 preclear/ drwxr-xr-x 2 root root 40 Apr 12 06:02 pwfail/ lrwxrwxrwx 1 root root 25 Feb 15 17:12 removed_packages -> pkgtools/removed_packages/ lrwxrwxrwx 1 root root 24 Feb 15 17:12 removed_scripts -> pkgtools/removed_scripts/ lrwxrwxrwx 1 root root 34 Apr 11 21:23 removed_uninstall_scripts -> pkgtools/removed_uninstall_scripts/ drwxr-xr-x 2 root root 40 Jan 30 2023 sa/ drwxr-xr-x 3 root root 300 Apr 11 21:23 samba/ lrwxrwxrwx 1 root root 23 Feb 15 17:11 scripts -> ../lib/pkgtools/scripts/ -rw-r--r-- 1 root root 0 Apr 28 2021 secure lrwxrwxrwx 1 root root 21 Feb 15 17:11 setup -> ../lib/pkgtools/setup/ -rw-r--r-- 1 root root 0 Apr 28 2021 spooler drwxr-xr-x 3 root root 60 Sep 26 2022 swtpm/ -rw-r--r-- 1 root root 0 Apr 28 2021 syslog -rw-r--r-- 1 root root 0 Apr 11 21:22 vfio-pci -rw-r--r-- 1 root root 0 Apr 11 21:22 vfio-pci-errors -rw-rw-r-- 1 root utmp 6.8K Apr 11 21:23 wtmp root@Tower:~#

No luck in SAFE mode. Nothing is being output to the flash drive and tail -f /var/log/syslog doesn't output anything. How can I get my syslog back? What drastic measures might I have to take? The server has been randomly rebooting every 5-7 days and without a syslog I can't troubleshoot this issue. THank you!

Yes Tried that. no luck Wiped the key and made a new instance using USB flash creator. Copied the backed up "config" folder over when complete. Seem to be having the same issue. Nothing currently being written to the logs folder on the flash, i've also enabled the local syslog to write to a share on the array and nothing being written there. Is there a way to "reinstall" the syslog server?

Yes! I did a full back up on the 15th of March and changed to a new flash drive. I also upgraded to 6.12. I just checked my backup and I can see there is a syslog file in there.

no, nothing. I know I've had a syslog server working at one point. Any idea where I go from here? Thank you!

The last two fields? Can you please tell me what the names of said fields are? Everything appears to be turned on here. Thank you!

diagnostics attached. thanks! tower-diagnostics-20240320-2151.zip

what am i missing here? See attached. There is nothing in my "media" folder and no logs being written to /logs folder in the flash.

screenshot attached. thank you!

is it possible it can't write the syslog while a parity rebuild is going on? I can't seem to think of anything else. There is no syslog.txt file in the /logs folder.

Really wanted to avoid having to start a new topic for this but my server has been crashing for weeks now and I can't seem to figure out why I'm unable to capture my syslog server to flash. I've enabled "Mirror syslog to flash:" in settings. However, when I download the logs folder from my flash drive and unzip the "tower-diagnostics-xxx.zip" the "syslog.txt" file is empty. Am I missing something obvious here? Thank you!

adding this (WebUI\Password_PBKDF2="@ByteArray(ARQ77eY1NUZaQsuDHbIMCA==:0WMRkYTUWVT9wVvdDtHAjU9b3b7uB8NR1Gur2hmQCvCDpm39Q+PsJRJPaCU51dEiz+dTzh8qbPsL8WkFljQYFQ==)") to my config file worked. Thank you so much!! Now should I go ahead and change the password to something more secure to prevent this from happening in the future?

Not sure if I am doing this right as I can't seem to start a new topic in this forum. Short of it is I have qbittorrent running on my unraid box. Ran an update on the docker container tonight and now can't login to the webUI. Getting "invalid username or password". I never changed the un/pw from default which was un: admin pw: adminadmin. What gives? how can I log back in? Is there a new un or pw that I should be using?

Servers been up for 10 days without a crash. I think that was the issue. Thank you again!! I’ve marked it as the solution.

Thank you! I have changed this to ipvlan. Will wait to see if I get another crash now. Hope this works out!