AtomZ

Now it is showing this:

I have the same issue now too - originally I have had the issue from my post here: Not sure what's going on with the VM/libvirt side of the house

I am not sure how to handle these issues that are filling up the LIBVIRT Logs under VM manager. Any ideas? I confirmed all iso's exist. Thanks.

Alright I fixed it!!!!! - I learned something new today. It was probably simple to always know but never actually took the time to understand what the metric settings are for under network settings. Now I do. If you are running multiple physical NICs, and you want them to have to have their own subnet (I control this at layer 3) and also communicate out to the internet which requires a default gateway, you must set the metrics for your default gateways if you have multiple gateways for routing. So in my case - br0's gateway which is eth0 is set to '1' which takes the priority gateway for routing, br1 which is eth1 I set the metric for the default gateway setting to '2' which is the next default gateway but is not the priority gateway for Unraid. I hope this helps anyone in the future if they run into this and wondering why on reboot the default routing won't stay persistent if there are multiple default gateways in your system. Example:

Essentially my default route gateway gets set to br1 which is for eth1 on reboot when it should stay persistent and set the default to br0 which is eth0. Not sure why this happens.

Hi everyone - I am running into an interesting situation that I have a work around for but wondering if there is a permanent solution. - I have a PCIe NIC card that is hardlined into my router/firewall for use for my VMs to separate that network traffic on its own VLAN. This is labeled as eth1 to Unraid on its own subnet. Eth0 is set statically on my main primary subnet for the main Unraid network/management interface. Every time I reboot the server, the default routing table on Unraid gets set to the eth1 subnet and not eth0. To fix I have to disable docker and VM manager, set eth1 to none, which automatically switches the default routing to how it should be on the primary subnet, then I set eth1 back to how it should be and everything is fine. How do I keep what I have working to stay on each reboot of the server? I’m hitting a wall, thanks for any input.

Hey guys noob questions incoming LOL - Where do I change the name servers for DNS. I am still having issues and have not tried this yet. Thanks! EDIT: Neverminded that was a dumb question LOL. To change the name servers it's under the docker configuration labeled NAME_SERVERS. Changed them per above posts and everything is up and running again. Thanks.

Hey guys - I updated to 6.11.5 and now DelugeVPN is not working properly. I keep getting the following errors. Any ideas? Thanks!

Just want to confirm before upgrading that this update does not include the latest SSH requirements to Unraid and to still use the workaround of certain algorithms? Is this still planned for after the new year?

Update: I killed the VM via cli in the console. Instantly VM tab is responsive. Restarted VM and everything is running smooth. It seem this becomes an issue when the VM is on for awhile. Any ideas that may help address this if this happens again will be helpful if possible.

Hi everyone - I am running into an issue where every time I try to access my VMs tab in the webGUI, the webGUI freezes and can't access the VMs tab. Looking at the console logs I keep seeing a warning that states: [pool www] server reached max_children setting (50), consider raising it Essentially this hangs up the webGUI and then it eventually loads. When trying to access one of the VMs nothing happens. However it is still running fine. Checked if the hypervisor was running via this command virsh list --all Everything returned normal instantly with the following with no issue: What's interesting this has happened before when I was on 6.9.3 and then I put off my VM project until this week and I still have the same issue. Would it help increasing the max children field? If so how should I go about this and to what value? I do not think this is a resource issue but just in case I have a 16 core processor, 64GB RAM, TBs left in disk space etc. and I have tried multiple browsers. Please see attached diagnostics as well if needed. Any ideas on how to address this? I appreciate any help. Thanks! diagnostics.zip

Ok so I ran that command and it returned the following: curl: (52) Empty reply from server Also what's interesting now in the logs this is what is populating: 2021-08-28 20:48:08,110 DEBG 'watchdog-script' stderr output: Unhandled error in Deferred: 2021-08-28 20:48:08,113 DEBG 'watchdog-script' stderr output: Traceback (most recent call last): File "/usr/lib/python3.9/site-packages/twisted/internet/base.py", line 1433, in mainLoop reactorBaseSelf.runUntilCurrent() File "/usr/lib/python3.9/site-packages/twisted/internet/base.py", line 972, in runUntilCurrent f(*a, **kw) File "/usr/lib/python3.9/site-packages/twisted/internet/defer.py", line 477, in callback self._startRunCallbacks(result) File "/usr/lib/python3.9/site-packages/twisted/internet/defer.py", line 580, in _startRunCallbacks self._runCallbacks() --- <exception caught here> --- File "/usr/lib/python3.9/site-packages/twisted/internet/defer.py", line 662, in _runCallbacks current.result = callback(current.result, *args, **kw) File "/usr/lib/python3.9/site-packages/deluge/plugins/Blocklist-1.4-py3.9.egg/deluge_blocklist/core.py", line 444, in import_list File "/usr/lib/python3.9/site-packages/deluge/plugins/Blocklist-1.4-py3.9.egg/deluge_blocklist/core.py", line 544, in auto_detect deluge_blocklist.detect.UnknownFormatError: 2021-08-28 20:49:39,057 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '49452' 2021-08-28 21:04:39,228 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '49452' 2021-08-28 21:19:39,413 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '49452' I am not sure what's going on now LOL. Any ideas? Still cannot access the webui but running curl ifconfig.io still resolves the VPN address. Other containers are still able to to open that I have passing through delugevpn such as radarr/sonarr/sabnzb which is interesting all are also resolving the correct VPN address.

Hey Binhex thanks for the reply. I did confirm my lan network is defined correctly and should be 192.168.1.0/24. It still will not let me connect to the container unfortunately.

Hello all! This is now the second time this has happened to me. What I ended up doing the last time is removing the container entirely and reinstalling it. I cannot access the webui again nor does sonarr/radarr can access delugevpn. Everything was working well for the past 2 weeks and now the same issue. Started a few days ago. I am using PIA, I have tried multiple servers that support port forwarding, checked to make sure the server's port forwarding was up, (Canada, Netherlands, ect.) and still can't access. Checked username/pass all correct. Running curl ifconfig.io resolves the VPN address. I am now at a loss LOL. Because of this now sonarr and raddarr cannot see deulugevpn. Also turned off port forwarding and still the same issue. Any ideas would be much appreciated. Logs attached. Thanks all!supervisord.log

I ended up figuring it out. With setting xmp memory profiles in BIOS to 3600 Unraid does not like. Setting it to recommended 3200 does the trick. Hopefully this helps someone who runs into the same concern/issue in the future.

I meant to attach the diags. Here they are. Thanks! diagnostics-20210725-1544.zip

Hi everyone, New to Unraid and looking for some guidance. I installed the Fix Common Problems plugin which stated it found hardware errors. I installed mcelog but not sure where to see what it detected. Doing some digging I did find this: Also I did see this come up in system logs maybe this is the hardware error not sure what this means? I appreciate the help! Thanks!