TheOgre

Okay so, after following your suggestion @Squid, it made me think to try a Live ISO and see if the network issues persists with a known working live drive. Well, it did not, and this led me down the road of trying the network stuff again. Turns out, I have a malfunctioning network switch. It seems to be passing SOME requests, but dropping everything else. After running a very long cable to the main ap, everything works just fine in unraid. Thanks for the nudge that got me to the solution!!

I have not made any tweaks to networking via that plugin, however, I just tried as you said and disabled it but no changes. I also tried booting in safe mode with no plugins and it is still not working. The very odd thing is, monitor my dhcp server, it does get the request and is assigned an IP, br0 then holds onto that IP, but eth0 drops it and gets the "device interrupt 20 memory [ADDR]" note underneath.

Having very odd issues with networking on this machine. Upgraded my main computer and repurposed my old one to replace my existing unraid server. Everything went flawlessly for about 2 days, now, networking is not working with no changes to the server or my network stack. ifconfig from the terminal shows eth0 with 10.0.0.35 as well as in the webUI (accessed via booting GUI mode), but diagnostics shows that it does not have an IP. An interesting discrepancy. I am uploading 2 diagnostic files. The first is when I initially accessed the server after networking went down, which shows "e1000e 0000:00:19.0 eth0: Detected Hardware Unit Hang" as the only issue I can see. However, these issues are showing up even when the server was still working fine and was accessible. Have tried swapping cables, different ports on the switch, rebooting the entire network stack. Changing DHCP settings. Nothing seems to change. I have noticed that the first minute or 2 after booting in GUI mode, I can access the network/internet from the server, then it suddenly goes down. The ui still shows it has an ip address, and if I unplug the network cable, it shows the link goes down, plug it back in, it comes back up full 1000mbps full duplex, however, still doesn't have access and ifconfig at that point shows it has no IP either. I am completely unsure what is happening, especially considering this was working just fine for 2 days straight. Is it possible the on-board NIC is dying? I can order a NIC card and put in, just will take some time to get here. Any help would be greatly appreciated. System specs: 4790k ASUS Z97-a Onboard Intel i218-v NIC 24gb DDR3 1866mhz ogreserv-diagnostics-20220129-1412.zip ogreserv-diagnostics-20220129-1547.zip

I have tried this docker container twice over the past few months and neither times has BlueIris actually opened. The docker container starts fine, i am able to see the noVNC feed and access the desktop, but nothing ever comes up, when right clicking, and selecting anything in the BlueIris applications tab, none of those commands do anything, and nothing shows in top either. Does this container actually work without pre-configuration? Or am I completely missing something that allows BlueIris to start? Any help would be appreciated as I am trying to dump Zoneminder for something that works and doesn't seem to have constant issues.

Still having some issues with this plugin regarding background tasks, however this issue is a bit more important and without a mitigation on my own versus my previous problem: The issue I am having now is that a script I am running in the background, that monitors system ram usage and restarts a docker container to prevent the system from completely running out of ram, seems to ONLY work when I log into the webui. Let me preface this by saying, I know restarting a container due to a ram issue is usually not an acceptable fix but in this situation, Zoneminder is having major memory leak issues on versions past 1.34 and even the developer is trying to fix it but has yet to come to a conclusion on how to, thus this is a temporary fix as it only needs restarting once in a while. The script in question: #!/bin/bash threshold=250 # Minimum amount of memory left when you should start killing, in MB browser="firefox-bin" # Change this to whatever you use, firefox is actually firefox-bin echo "Monitoring RAM usage and restarting Zoneminder docker when remaining RAM falls below 250mb" while true; do available=$(free -m | head -2 | tail -1 | awk '{print $7}') if [ "$threshold" -ge "$available" ]; then docker restart Zoneminder echo "RAM usage exceeded, restarting Zoneminder docker....one moment" fi sleep 20 done The oddest thing about this, was this exact script was working for a few weeks, and suddenly does not work unless the server has an active GUI connection to it open. For instance, the server will creep up in memory until it reaches the 250mb left mark, then the script restarts the container, but this doesn't happen anymore until after I log into the unraid webui. I try to access any service/docker running on the machine, and it fails due to the server being out of ram, but when I load into the webui, system CPU and RAM usage is pegged at 100% but after a few short moments, the script kicks in and restarts the process. I don't see any reason for this behavior and why it started not working randomly (guess that's most IT problems lol) but I have tried everything from recreating the script, restarting the server, and even increasing the RAM threshold within the script to no avail. Any help would be greatly appreciated!

Recently started using the plug-in and am running into an issue where, if the script is started in the background, aborting the script does not kill the process. It's a simple RAM monitoring script with an if statement if that makes any difference.

I aswell am having issues today relating to it seems the PIA port forwarding API. Getting curl error code 56 when starting the docker container. Issue is resolved following disabling port forwarding. Any workaround for the issue to get back up and running, or just have to wait on PIA? Thanks for the great work! Edit: Have tried switching to 3 other servers (Germany, Spain, and Israel) as others have tried, with no luck. Now receiving exit code 52 and getting the same result. Have tried both third and fourth generation.