Really happy to have this system back up and relatively stable after struggling with hardware issues the last few months. The last two days I've ended up with containers that were unresponsive. I have a pretty typical *Arr suite setup. Yesterday I was able to SSH in and stop/kill all but two containers but couldn't get the last two to shut down and had to hard down. Today a sort of similar situation occurred but the Unraid web GUI became unresponsive. I attempted to restart Nginx but (I'm a little out of my comfort zone here) it seemed like there were running containers I couldn't kill keeping that from happening. I really wanted to get the web GUI back online because I was still running a parity check from the day before. I ended up having to hard down again, deleted the docker image, and reinstalled. All of this has been a great learning experience but one common theme that kept coming up was that I probably need to figure out what's causing the containers to become unresponsive in the first place to ultimately resolve this issue. Right now I only have Plex running but am kind of lost as to how to figure out what the root cause of this issue might be. Some seem to suggest I should pin cores to certain containers? Not sure how to distribute them if that's the case. Would really appreciate any insight someone might offer. Syslog & diag attached. 

robflix-diagnostics-20241228-1821.zip RobFlix_Syslog.txt

Edited December 28, 20241 yr by RobFlix

when running the docker are they set to host mode or bridge mode.

if a docker is running a web server and set to host it replaces unraids host ports thus the web server stops function.

unraids webui uses emhttp and parts of nginx for ssl/https

Thank you for post a diag file, ill review it latter.

 

8 hours ago, bmartino1 said:

when running the docker are they set to host mode or bridge mode.

if a docker is running a web server and set to host it replaces unraids host ports thus the web server stops function.

unraids webui uses emhttp and parts of nginx for ssl/https

Thank you for post a diag file, ill review it latter.

 

It looks like everything but Plex is set to bridge mode. I assume I need to fix that for Plex?

its worth a try i'm not ware of conflict plex ports. I usual set thoese to a cusom with there own ip to allow all ports there own freedom. and for remote world access to gurnatee a static ip and port access.

Not really sure what happened but Plex did not like running on the the bridge network. The web GUI would not load. Still not sure how to troubleshoot the root issue though.

diag is only part of the picture. sadly the daig for security won't grab some docker stuff.

which plex docker?

I use: linux servers
lscr.io/linuxserver/plex

settings docker:

I use macvlan ipvlan is ok here, but toggle advance and enable preserverr and host access

 

I'm on v7 rc2 stable 6 is fine.

you should be using custom:

yours may say br0

it could be custom br0,bond0,eth0 depending on your unriad network settings.
I have bridgin and bonding off..

with custom you static set a ip address to the docker as it it were its own machine.
not the subnet my network dhcp router is 192.168.2.0/24 so i would need to set a static ip of 192.168.2.2 per example

plexe webui would then be at 192.168.2.2

in bridge mode its at unraids ip but it apears your have a port conflict. try custom interfacename