skunk Posted March 19 Share Posted March 19 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! Quote Link to comment
JorgeB Posted March 19 Share Posted March 19 The should be an unzipped syslog.txt file in the /logs folder. Quote Link to comment
skunk Posted March 20 Author Share Posted March 20 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. Quote Link to comment
JorgeB Posted March 20 Share Posted March 20 Post a screenshot from the syslog server settings. Quote Link to comment
skunk Posted March 20 Author Share Posted March 20 screenshot attached. thank you! Quote Link to comment
itimpi Posted March 20 Share Posted March 20 You have not actually set the syslog server to be enabled ! Quote Link to comment
skunk Posted March 21 Author Share Posted March 21 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. Quote Link to comment
trurl Posted March 21 Share Posted March 21 Have you filled your log space? Attach Diagnostics to your NEXT post in this thread. Quote Link to comment
skunk Posted March 21 Author Share Posted March 21 diagnostics attached. thanks! tower-diagnostics-20240320-2151.zip Quote Link to comment
itimpi Posted March 21 Share Posted March 21 6 hours ago, skunk said: 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. in this screenshot the server is enabled to ‘listen’ but you have not set at least one of the last two fields which are required to actually make it start writing anything. Quote Link to comment
skunk Posted March 21 Author Share Posted March 21 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! Quote Link to comment
Frank1940 Posted March 21 Share Posted March 21 You have a condition that I have never seen before! There is no syslog in your Diagnostics file!!! So it is not surprising that there is no syslog file in the /logs directory of the flash drive. I am going to ping @JorgeB as he can usually figure these types of problems out... Quote Link to comment
JorgeB Posted March 21 Share Posted March 21 That's strange, does this output something? tail -f /var/log/syslog Quote Link to comment
skunk Posted March 21 Author Share Posted March 21 6 hours ago, JorgeB said: That's strange, does this output something? tail -f /var/log/syslog no, nothing. I know I've had a syslog server working at one point. Any idea where I go from here? Thank you! Quote Link to comment
trurl Posted March 21 Share Posted March 21 Do you have a current flash backup? Quote Link to comment
skunk Posted March 21 Author Share Posted March 21 4 minutes ago, trurl said: Do you have a current flash backup? 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. Quote Link to comment
trurl Posted March 21 Share Posted March 21 Looks like you have an FSCK file on flash. That file happens when a file is corrupt. Whatever can be guessed about its contents gets put into FSCK. Was that file also on your backup? Reboot and see if syslog works. If not, maybe something important got corrupted on flash. Your config folder from your backup is all you need to get your configuration on a new install. Maybe you already know since you changed flash drives. Quote Link to comment
skunk Posted March 22 Author Share Posted March 22 1 hour ago, trurl said: Looks like you have an FSCK file on flash. That file happens when a file is corrupt. Whatever can be guessed about its contents gets put into FSCK. Was that file also on your backup? Yes 1 hour ago, trurl said: Reboot and see if syslog works. If not, maybe something important got corrupted on flash. Tried that. no luck 1 hour ago, trurl said: Your config folder from your backup is all you need to get your configuration on a new install. Maybe you already know since you changed flash drives. 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? Quote Link to comment
trurl Posted March 22 Share Posted March 22 What happens if you boot in SAFE mode? Quote Link to comment
skunk Posted April 11 Author Share Posted April 11 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! Quote Link to comment
JorgeB Posted April 11 Share Posted April 11 Post the output of ls -lh /var/log Quote Link to comment
skunk Posted April 12 Author Share Posted April 12 On 4/11/2024 at 8:52 AM, JorgeB said: Post the output of ls -lh /var/log 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:~# Quote Link to comment
Recommended Posts
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.