Hey guys,

Please could someone be of assistance - I am having random freezing of my one UnRaid server - it occurs anywhere between a few hours to a few days of runtime

 

Here are my Logs:

 

athenaeum-diagnostics-20230903-1402.zip

Enable the syslog server and post that after a crash.

I think I have? I haven't had the machine on in a while - the most recent one I have attached

Syslog included with the diagnostics starts over with every reboot.

Ok, here is the most recent diagnostics export from the server. 

I have the syslog setting to copy to flash - the last one present I have attached in the first post (and will post the the next one from that when the next crash happens) 

athenaeum-diagnostics-20231108-2035.zip

Crashed again last night. 
Here is the most recent log from the flash drive:

 

athenaeum-diagnostics-20231109-1023.zip

And the persistent syslog from the syslog server?

I thought I had enabled it

These are my Syslog Server settings - am I doing something wrong?

 

Ah, would it be this file?

syslog

I think this should never happen:

Nov  9 12:42:41 Athenaeum ntpd[10567]: bind(20) AF_INET 192.168.0.20#123 flags 0x19 failed: Address already in use
Nov  9 12:42:41 Athenaeum ntpd[10567]: unable to create socket on br0 (62) for 192.168.0.20#123
Nov  9 12:42:41 Athenaeum ntpd[10567]: failed to init interface for address 192.168.0.20

 

You sure you not accidentally assigned a static address

 

You also need to look into this on unless you yanked out the plug - crusty wallsocket maybe?

Nov  9 11:38:45 Athenaeum apcupsd[5004]: Power failure.
Nov  9 11:38:47 Athenaeum apcupsd[5004]: Power is back. UPS running on mains.

I live in South Africa - we have an electricity crisis, and 'Load Shedding' - basically rolling blackouts.

Lots of fun

 

The IP address is reserved in the Router (UniFI system) - I know they've recently reserved x.x.x.20 as a fall back. Going to change the reservation to another IP

8 minutes ago, sjoerd said:

I think this should never happen:

No, that's not normal, though probably not the reason for the lock ups, still needs to be fixed, check network config.

Another crash in the early hours of this morning. Here is the new syslog

syslog

I have changed the IP reservation on the router, network time was out a little (9minutes) so I have corrected that as well.

 

Unfortunately there's nothing relevant logged, this usually points to a hardware issue, one thing you can try is to boot the server in safe mode with all docker/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.

Thank you

It looks like it is a hardware issue - either MoBo or CPU

I had tried a RAM swap several weeks ago, but persited with the issues

 

I swapped the CPU and MoBo for some old spares I had lying around, and now I have had no crashes.

 

Thank you for the help