Server locks up with no access

[vmax5000]

I built a new server and it runs great for a few weeks and then locks up, when it locks up I can't access it from the server with a monitor and keyboard, it won't reboot with ctrl-alt-del and it won't do a graceful shutdown by pressing the power button on the server. The only way to get it working again is to force a shutdown with the power button. This has happened 3 times since building the server. When the server starts up it starts running a parity sync, while the sync is running it takes about 3 mins to switch tabs or click on a docker GUI. I enabled the syslog server when the trouble occurred the first time, but I don't see any files after I boot up. After the parity sync finishes the server run great and switching tab or looking a docker pages is instant!

ultimate-diagnostics-20240411-0918.zip

[itimpi]

It might be worth posting a screenshot of your syslog server settings so we can check them

[vmax5000]

Ok, here is the screenshot.

 

Thanks

[itimpi]

Those show that server is in ‘listening’ mode.     As the syslog server link mentions you need to set the Mirror to Flash option or put your servers address into the Remote Server field to actually get anything written.

[vmax5000]

Ok, I will make the change. It will probably be a week or two before another crash happens. I will post again after the next crash.

Thanks

[vmax5000]

Here are the new SysLog settings.

[itimpi]

With those setting you end up with the a syslog fole in the ‘logs’ folder on the flash drive and in the ‘appdata’ share.    The file from the ‘logs’ folder is automatically included in any diagnostics.

[vmax5000]

Server crashed again last night, I have the syslog file and the most resent diag dump from the flash drive.

Thanks

syslog ultimate-diagnostics-20240411-0918.zip

[JorgeB]

Constant call traces, start by running memtest, if nothing is found, and because memtest is only definitive if it finds errors, try with just one stick of RAM, if the same try with a different one, that will basically rule out bad RAM, if issues persist, another thing you can try is to boot the server in safe mode with all docker containers/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.

[vmax5000]

Looks like a bad ram stick, I ran memtest86 with one stick and memory passed. When I put the other stick in and ran memtest86 with both in it is showing failures. I have opened a ticket with corsair.

Thanks