Unraid webgui, ssh and local terminal go unresponsive and simply timeout. Some docker services keep running, while the rest goes unresponisive or simply gets connection errors. Plex keeps running without issues and according to Plex CPU usage is never higher than 50-60% during the freeze.

 

Already replaced one of my cache SSD's as one was failing SMART and thought that was the culprit. But the problem has been just as frequent after I replaced it. I have not made any changed to the servers configuration that seems to have caused the issue either. It has been running steady for about a year without any big issues.

 

I have attached diagnostics from the last two occurances, which are also the only times any diagnostics has been able to be generated during a manual powerdown. 

 

First freeze I am not sure when it happened, but I forced a shutdown at March 29 01:30

Second freeze happened at about March 29 05:11

 

Fixes already tried:

Replaced SSD

Replaced Flash (had errors on flash in earlier freeze)

Redid CPU pinning; unpinned all dockers from first core

Memtest passed

SMART on Cache passed

 

 

The errors that I've seen repeated in the logs:

Quote

Mar 29 06:16:34 Tower winbindd[2142]: [2025/03/29 06:16:34.444369,  0, traceid=978] ../../source3/winbindd/winbindd_samr.c:111(open_internal_lsa_conn)
Mar 29 06:16:34 Tower winbindd[2142]:   open_internal_lsa_conn: Could not connect to lsarpc pipe: NT_STATUS_IO_TIMEOUT
Mar 29 06:22:57 Tower winbindd[2142]: [2025/03/29 06:22:57.039075,  0, traceid=995] ../../source3/winbindd/winbindd_samr.c:71(open_internal_samr_conn)
Mar 29 06:22:57 Tower winbindd[2142]:   open_internal_samr_conn: Could not connect to samr pipe: NT_STATUS_CONNECTION_DISCONNECTED

Quote

Mar 29 01:34:30 Tower php-fpm[9713]: [WARNING] [pool www] child 24765 exited on signal 9 (SIGKILL) after 32.575692 seconds from start
Mar 29 01:35:00 Tower php-fpm[9713]: [WARNING] [pool www] child 25430 exited on signal 9 (SIGKILL) after 44.673531 seconds from start
Mar 29 01:35:09 Tower php-fpm[9713]: [WARNING] [pool www] child 26178 exited on signal 9 (SIGKILL) after 36.996556 seconds from start
Mar 29 01:35:38 Tower php-fpm[9713]: [WARNING] [pool www] child 26920 exited on signal 9 (SIGKILL) after 29.619983 seconds from start

 

Any help is appreciated!

tower-diagnostics-20250329-0144.zip tower-diagnostics-20250329-1040.zip

Edited April 19, 20251 yr by Kinstrald

1 hour ago, Kinstrald said:

Mar 29 01:35:00 Tower php-fpm[9713]: [WARNING] [pool www] child 25430 exited on signal 9 (SIGKILL) after 44.673531 seconds from start
Mar 29 01:35:09 Tower php-fpm[9713]: [WARNING] [pool www] child 26178 exited on signal 9 (SIGKILL) after 36.996556 seconds from start
Mar 29 01:35:38 Tower php-fpm[9713]: [WARNING] [pool www] child 26920 exited on signal 9 (SIGKILL) after 29.619983 seconds from start

 

In my experience, these errors can be the result of the server being close to exhausting the memory, GUI can become extremely slow, like 1 minute to open the dashboard, try limiting the memory for VMs/docker services, or adding a little more RAM.

 

It could also be one or more containers hogging the CPU, try pinning only some cores to them, and leave cores 0/1 available for Unraid.

 

Also, recommend trying a couple of other things, go to Settings - Global share settings and set the Number of fuse File Descriptors to the max, and enable this:

https://docs.unraid.net/unraid-os/release-notes/7.0.0/#excessive-flash-drive-activity-slows-the-system-down

2 minutes ago, JorgeB said:

Also, recommend trying a couple of other things, go to Settings - Global share settings and set the Number of fuse File Descriptors to the max, and enable this:

https://docs.unraid.net/unraid-os/release-notes/7.0.0/#excessive-flash-drive-activity-slows-the-system-down

I'll give this a try and see if it helps.

Already did the CPU pinning freeing 0/1 for Unraid.

 

Free RAM usually sits around 10GB out of a total 32GB, I have had an issue with RAM before increasing to 32GB. But then I got errors of the RAM being exhausted during transcoding.

 

Also the webGUI goes completely unreachable, no response from either webGUI or through SSH. 

I can type in the local terminal but I can't even log in. I can trype in username, but it timeouts before I can type in a password.

Just had the same lockup again today. This time I wasn't able to get the full diagnostics, but the syslog is filled with the same two errors from before.

See if it still happens with docker and VM services disabled.

The issue seems to have been the RAM. After many attempts to get a proper log of the moments before the freeze, I saw a spike in RAM usage. Shortly after the RAM usage went down, but the system never recovers, needing a forced shutdown to come back.

 

 

I will be installing more RAM and give antoher update if this solved everything. In the meantime I have disabled all nonessential docker containers to limit RAM usage. Currently on day 3 of uptime, so its looking good.

No issues since increasing RAM. Still not sure what caused the sudden increase in RAM usage. But it has been running stable now.