Pub

I just updated them as I was doing some searching and looks like I might have had the setting improperly setup. I did not have local syslog rotation enabled I did not have remote syslog server IP setup as my server IP Do these settings look correct now? syslog is a share setup only to write to cache

I have been having an issue where my system becomes unresponsive intermittently. I lose access to the GUI, I can't access the console directly from the machine using keyboard, I can ping the server IP and get a response. My VM's were still accessible but dockers were unreachable. In the past I had an issue with the USB drive so I swapped that out with a new one last night after I was forced to a manual reboot. The system came back online and began a parity check which was using 100% of resources during that time and made it impossible to do anything. So I went to sleep, woke up to the whole server being locked up again, this time no VM's were accessible, GUI unreachable. So this morning I did another force reboot and stopped the parity check so I could pull a new diagnostics. I setup the syslog to copy to my cache drive in its own share, but upon reboot I did not see anything in there. There is a syslog in my diagnostics zip but it looks like its only from the reboot as of this morning. I'm not sure what I am looking for in the log to help me diagnose the issue. Any help to get me going in the right direction would be great. Thanks tower-diagnostics-20241026-1246.zip