MammothJerk

Only other thing i can find about this issue is people reporting a bad NIC, i've got an onboard intel-i210AT. might have to invest in a new NIC if that is the issue.

Created a completely new docker, no plugins, with same settings and adding only 6 torrents, downloading at 20-30MB/s im still maxing out my CPU.

My downloads within deluge is set to "/mnt/user/Torrents" which would go through "Host Path 1" to "/mnt/user/Torrents" which in turn would actually be written to "/mnt/cache/Torrents" since the share "Torrents" is a cache-yes share.

sure thing

My CPU is hitting 100% after upgrading internet speeds. I went from 100/100 to 1000/1000 the other week and now my unraid server is freezing up constantly with the CPU maxed out at 100%. I narrowed it down to delugeVPN writing to the cache taking up all the CPU resources, even pinning deluge to 4 specific cores doesnt help as it still uses all cores at 100% My cache is a cache pool of 2 devices, one 960gb and one 250gb for a total of 1.2TB~ Heres disk/cpu activity with 0 torrents downloading to array/cache and around 20~ torrents uploading from array Heres disk/cpu activity with 2 torrents downloading to cache capped at 30MB/s and around 20~ torrents uploading from array at around 9MB/s Heres disk/cpu activity with 2 torrents downloading to cache capped at 10MB/s and around 20~ torrents uploading from array at around 9MB/s is this expected behavior? like is my CPU too shit for my download speed? Why would writes to cache impact my CPU to this extent?

still not working admin/adminadmin on a fresh install restarted container, reinstalled it, etc. not working and i cant find the user/pass in the appdata to change either following frollays instructions doesnt help either

any idea why i would get this error? dont think i've done any changes to this file personally. It doesn't seem like the plugins respect the delay setting any longer, they will always auto update instantly. Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/ca.update.applications/include/exec.php on line 100

i hadn't done any changes for a long time then 2 days ago or so delugeVPN just completely stopped downloading/uploading anything. If i turn VPN off in the template it starts downloading/uploading instantly. and the weird thing is even when VPN is active and DelugeVPN is not downloading anything, the privoxy proxy still works for clients connected to it. My provider is Mullvad and it seems they had an update (to their desktop app from what it looks like) just around that time. that could be related somehow? Any ideas? attached the (hopefully) relevant log edit: Started a new container with the same settings and it works, so something mustve gotten screwed up within the config oh boy here i go troubleshootin again edit2: had to change incoming port for whatever reason... had been running fine for months and then just died, weird.

any idea on this one @binhex? 😁

haha i wish 😋 it's one of deluges default plugins

I'm getting a lot of spam in my deluged.log with "Session status key not valid:" thanks to the stats plugin, it starts off during the plugin load as such: 20:19:41.892 [INFO ][deluge_label.core :78 ] *** Start Label plugin *** 20:19:41.907 [INFO ][deluge.pluginmanagerbase :189 ] Plugin Label enabled... 20:19:41.914 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:19:41.914 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:19:41.914 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:19:41.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:19:42.214 [INFO ][deluge.pluginmanagerbase :189 ] Plugin Stats enabled... 20:19:42.218 [INFO ][deluge.pluginmanagerbase :189 ] Plugin Scheduler enabled... then it starts repeating constantly after all my torrents have loaded 20:19:49.616 [INFO ][deluge.core.torrentmanager :885 ] Finished loading 2032 torrents in 0:00:03.984063 20:19:49.831 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:19:49.831 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:19:50.046 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:19:50.046 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:19:50.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:19:50.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:19:50.936 [INFO ][deluge.core.rpcserver :197 ] Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. 20:19:51.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:19:51.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:19:52.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:19:52.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:19:53.138 [INFO ][deluge.core.rpcserver :171 ] Deluge Client connection made from: xxx.x.x.x:xxxxx 20:19:53.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:19:53.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:19:54.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:19:54.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:19:55.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:19:55.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:19:56.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:19:56.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:19:57.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:19:57.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:19:58.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:19:58.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:19:59.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:19:59.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:00.656 [INFO ][deluge.core.rpcserver :171 ] Deluge Client connection made from: xxx.xxx.x.xxx:xxxxx 20:20:00.749 [INFO ][deluge.core.rpcserver :197 ] Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. 20:20:00.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:00.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:01.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:01.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:02.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:02.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:03.484 [INFO ][deluge.core.rpcserver :171 ] Deluge Client connection made from: xxx.xxx.x.xxx:xxxxx 20:20:03.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:03.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:04.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:04.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:05.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:05.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:06.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:06.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:07.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:07.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:08.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:08.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:09.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:09.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:10.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:10.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:11.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:11.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:12.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:12.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:13.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:13.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:14.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:14.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:15.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:15.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:16.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:16.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:17.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:17.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:18.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:18.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:19.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:19.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:20.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:20.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:21.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:21.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:22.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:22.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:23.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:23.916 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:24.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:20:24.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:20:25.915 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:55:09.531 [INFO ][deluge.pluginmanagerbase :250 ] Plugin Stats disabled... -no errors for 5 minutes til i start it up again 20:59:43.245 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:59:43.245 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:59:43.246 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:59:43.246 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:59:43.510 [INFO ][deluge.pluginmanagerbase :189 ] Plugin Stats enabled... 20:59:44.247 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:59:44.247 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:59:45.247 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:59:45.247 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:59:46.247 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:59:46.247 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:59:47.246 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:59:47.247 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections 20:59:48.247 [WARNING ][deluge.core.core :656 ] Session status key not valid: dht_cache_nodes 20:59:48.247 [WARNING ][deluge.core.core :656 ] Session status key not valid: num_connections Disabling the stats plugin prevents this spam from occurring, and according to this topic on the deluge bug tracker i have to do something to the stats egg. the problem is i'm not sure where this egg is located in the unraid/docker/delugevpn installation. any pointers on what to do to fix this?

dang so Pihole would be useless to me since im running pretty much all my devices through the DelugeVPN proxy?

I'm trying to use Pihole as my DNS for DelugeVPN so my clients connected via proxy get the adblocking that Pihole provides. i added the Pihole local DNS ip to NAME_SERVERS but that doesnt seem to work. Pihole DNS runs through 8.8.8.8 and 8.8.4.4 currently for simplicity while trying to get the problem diagnosed. 2020-01-11 14:10:29,058 DEBG 'start-script' stdout output: [info] Adding 192.168.1.31 to /etc/resolv.conf 2020-01-11 14:10:44,077 DEBG 'start-script' stderr output: Error: error sending query: Could not send or receive, because of network error 2020-01-11 14:10:59,095 DEBG 'start-script' stderr output: Error: error sending query: Could not send or receive, because of network error 2020-01-11 14:11:19,113 DEBG 'start-script' stderr output: Error: error sending query: Could not send or receive, because of network error Any idea where to go from here?