MammothJerk

quick reply 😁 here ya go { "request": { "method": "GET", "url": "api/datasources/proxy/1/query", "params": { "db": "telegraf", "q": "SELECT last(\"raw_value\") AS \"Power On Hours\" FROM \"smart_attribute\" WHERE (\"name\" = 'Power_On_Hours') AND time >= now() - 12h GROUP BY \"device\" LIMIT 10", "epoch": "ms" }, "data": null, "precision": "ms" }, "response": { "results": [ { "statement_id": 0 } ], "executedQueryString": "SELECT last(\"raw_value\") AS \"Power On Hours\" FROM \"smart_attribute\" WHERE (\"name\" = 'Power_On_Hours') AND time >= now() - 12h GROUP BY \"device\" LIMIT 10" } }

Thanks for your great work, this works awesome The only issue i have is the "Drive Life" power_on_hours being the only graph not working, any idea what the problem is and/or how to troubleshoot it? all my drives has the power_on_hours attribute but it's not being imported somehow

Recently i decided i wanted to setup tunnels on my 2 local unraid boxes to route all of their traffic through my VPN provider but for now it does not seem to be possible. It seems like you can only use EITHER the remote tunneled access OR the VPN tunneled access, you cannot use them both at the same time so im either unable to access my local network from remote OR my local unraid boxes will not go through the VPN. Is there a way to enable both "VPN tunneled access" AND "Remote tunneled access" at the same time? or a function that works similarly?

Currently i'm running the reverseproxy docker with duckDNS docker for updating my IP and it's working great. I can access both dockers on my 2 local unraid boxes through a duckdns domain that gets authenticated through Organizr 2FA. With Wireguard VPN Manager i can access my network through the "Remote tunneled access" if i need to access any of the unraid webUI's for any reason or anything else on my network. it also works as a VPN for my remote location where it looks like i am connecting from my home address. Now recently i decided i wanted to setup tunnels on my 2 local unraid boxes to route all of their traffic through my VPN provider but for now it does not seem to be possible. Firstly it seems like you can only use EITHER the remote tunneled access OR the VPN tunneled access, you cannot use them both at the same time so im either unable to access my local network from remote OR my local unraid box will not go through the VPN. Secondly it doesnt appear that i can use the reverseproxy when the "VPN tunneled access" is turned on because i would have to forward port 443 and 80 through my VPN provider which doesnt seem feasible. So i sort of have 2 questions. Is there a way to enable both "VPN tunneled access" AND "Remote tunneled access" at the same time? or a function that works similarly? Is there a way to use reverseproxy if the host is connected to a VPN that cannot forward ports?

I'm also using Mullvad and running into the same issue as Monkeysphere and notcarl I also had a question, is it possible to have "Remote tunneled access" and "VPN tunneled access" at the same time? i always want my unraid box to connect to the internet via my VPN but i also wanna be able to connect to my LAN remotely, and also take advantage of the VPN. Is this possible? the "Remark: this must be the only peer in the tunnel and sole active tunnel when in use" on VPN tunneled access seem to indicate this is currently not possible, but would it be feasible to implement?

I figured out what the issue is in libtorrent max_peerlist_size is set to 3000, increasing that solved my issue... for now... 😁

This is the only real issue i've had so far. as long as i dont access any label that has 1000+ torrents in it it works as smooth as can be. Is there another client i should be using if i have this many torrents? i haven't changed these settings for a long time so i wouldnt think they are the cause..

Hey, i have an issue where whenever i restart my container i have a lot of torrents that have been paused, and i have to manually restart them, this has several issues where sometimes i will get an HnR warning and sometimes a torrent will just stop downloading completely. I recently reached 6000 torrents in my client so i was wondering if there way maybe a cap there or something? any help pointing me in the right direction would be nice, thanks. Here are my settings

Good news, i split up my cache and changed the filesystem to xfs, now downloading for 15~minutes @ 50megabytes/second and my cpu is sitting at around 40% with periodical 100% spikes on any of the cores, which is pretty normal usage. @SundarNET do you reckon the btrfs cache pool was your issue as well? perhaps your appdata folder is stored on the cache pool? edit: i've actually noticed that all of my dockers are more responsive now, definitely seems to be an issue with btrfs cache pool...

My internet speed is 1000/1000 megabit and unraid is showing 100% CPU on transfers around 20-30 megabytes, if i cap the speed to around 10 megabytes my CPU is fine. I'm using a btrfs cache pool, i was going to change it in the next unraid release but i should be fine with a bit lower space until then. I'll change it to xfs and see what happens. I'm indeed using a Xeon CPU as well. Tried installing unraid on an old pc running a 4770k and im DLing at around 30 megabytes/s and i'm not seeing any CPU spikes. Though since it's a completely different system and CPU is not the only thing being different im not sure how valuable this information is.

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?

i believe the problem was gone in rc3, but with the update to rc4 and rc5 the problem came back (not as bad as before) and only seems to affect dockers. tower/Docker page will not load, any docker currently running hangs and i am unable to access them through webui, any command i send to any docker gets executed after the mover completes. idk if this is a separate problem though? i dont have issues navigating the webui or the SMB shares it seems to be specifically the dockers. It is also intermittent. could it have something to do with having the system and appdata folder on the cache? and with mover moving stuff off of the cache it taking up all the bandwidth?

It appears to have been fixed for me, webui loads as quick as normal, no dockers are behaving weird or slow, and streaming does not slow down. If i run into any problems i will update you on it