Texiun

Yes it was, triggered after losing connection (yet ping remained active) Starting to suspect it’s more likely the user network?

I generally always have syslogs enabled to capture crashes like this. Last crash was approx 9:22PM last night. You will see Kernal panic entries in these logs, This is from a docker image thrashing the CPU with DB writes. This was resolved after the docker img rebuild and removing the docker container in question. syslog-192.168.5.150.log

Hi Team! I've been running my unraid server for approx 3 or so years and only in the past 6 months have I started to see an issue. Purpose: Arr Stack, NGINX, Home Assistant. Server Build: 7.3.1 Fault Description: Every 2 weeks or so the Web GUI and any associated docker conainers become unresponsive on the network, I've confirmed that the network link stays up as I can continue to ping the server but I cannot connect to it via :80 or any docker containers as mentioned. Attempted Fixes tried so far: Rebuild Docker IMG, rebuilt using existing configs. Memory Tests (Confirmed to be "OK") Recently had a failed 4TB, this has been replaced with a new drive. Migrated to a new Flash drive. Changed network port on switch. Inspected the logs to the best of my ability but can only see a clean shutdown on request. Move from MACLVAN over to Custom Br0 Writing SYSLOGS to USB is always set to on. Observation: From my inspections on the logs the server is still responding to physical button shutdowns, and appears to cleanly restart when required. I am aware of the mover script running a bit too frequently, however this issue was happening prior to the introduction of the new mover script. Based on the fact I can still ping my server, I'm not convienced it's entirely a system crash or hang. I would greatly appreciate any assistance in resolving the rogue sys locks/Network connectivity phantom. Many thanks for your time <3 media-server-diagnostics-20260708-2141.zip