I've been having problems with the web interface and ssh going unresponsive and having to do a reset.

Generally the dockers and VM stay running but I can't do anything on the server itself. I'd appreciate any help

kamino-diagnostics-20251005-0835.zip

Enable the syslog server and post that after it happens next time.

syslog-10.0.0.54.logHere you go

Server is running out of RAM, Plex DLNA Server appears to be the reason. Also, also a lot of these are logged, likely related to the OOM issue:

Oct  5 08:28:44 Kamino php-fpm[10560]: [WARNING] [pool www] child 1413365 exited on signal 9 (SIGKILL) after 41.182448 seconds from start
Oct  5 08:28:45 Kamino php-fpm[10560]: [WARNING] [pool www] child 1414086 exited on signal 9 (SIGKILL) after 17.872038 seconds from start
Oct  5 08:29:12 Kamino php-fpm[10560]: [WARNING] [pool www] child 1414729 exited on signal 9 (SIGKILL) after 15.186986 seconds from start
Oct  5 08:29:28 Kamino php-fpm[10560]: [WARNING] [pool www] child 1414780 exited on signal 9 (SIGKILL) after 32.078075 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:

Version 7.0.0 2025-01-09 | Unraid Docs

This version of Unraid OS includes significant improvements across all subsystems, while attempting to

Thanks!

I've disabled the DLNA server, I don't know why I enabled it in the first place. I've also done the fuse file descriptors, I'm not sure what the second thing you were suggesting was as it just linked to the unraid release docs.

Will see how this goes, Thanks again.

The last few days there have been no lockups so I think this has been solved. Thanks again!

I’ve had that happen too — in my case it was bad RAM causing the lockups. Try running a memtest and check your flash drive for corruption just to rule those out

_Tutuapp

Edited January 28Jan 28 by avensis