Rysz Posted March 18 Share Posted March 18 (edited) Data Volume Monitor (DVM) for UNRAID "A plugin that lets you monitor and act on your consumed data volume utilizing vnStat." With much pride I'd like to present my latest project - the Data Volume Monitor (DVM). Dashboards, footer information, notifications, user actions (on VMs/Docker containers) and custom scripting. These are a few of the features being offered - all centred around the data volume consumption of your server. Don't want to your Syncthing container to pull in more than 50 GB a day? No problem, DVM will stop and restart the container for you within those limits. Running a few data intensive VMs and want to pull the plug when it's been too much? No problem, DVM will disconnect and reconnect specific VMs from/to the network. Want to move around some files and folders when you've pulled in too much data? No problem, set up a custom script and DVM will execute it for you when it's time. Please report back if you are experiencing any problems! This plugin was developed with older machines in mind - it's been tested on 6.8.3 and above. Edited March 18 by Rysz 5 Quote Link to comment
wuudogg Posted March 18 Share Posted March 18 This is really great. Was looking for a way to keep certain *arrs from running wild and downloading too many very high quality linux ISO downloads daily. Was trying to do this in sabnzbd as it isn't native in most of the *arr apps. This might be the ticket. Thanks 1 Quote Link to comment
stefan marton Posted March 18 Share Posted March 18 i try to install but i see this wanring : Installation already in progress Another plugin installation or update is already in progress, and this one cannot start. Wait until the current installation or update is completed and try again ! Not valid! but nothing is installing or upgrading Quote Link to comment
Rysz Posted March 18 Author Share Posted March 18 (edited) 26 minutes ago, stefan marton said: i try to install but i see this wanring : but nothing is installing or upgrading Hello, I just tried it from two different servers and it works just fine here. Maybe something got stuck in Community Apps, I found this post about the warning with a solution: Edited March 18 by Rysz Quote Link to comment
nolan879 Posted March 18 Share Posted March 18 I'm new to virtual interfaces, how can I determine which vethXXXXX interfaces goes to which of my docker containers? Any thoughts on adding a "Friendly Name" feature for interfaces? 1 Quote Link to comment
Rysz Posted March 18 Author Share Posted March 18 6 minutes ago, nolan879 said: I'm new to virtual interfaces, how can I determine which vethXXXXX interfaces goes to which of my docker containers? Any thoughts on adding a "Friendly Name" feature for interfaces? I've wanted to add this feature, but to my knowledge it's not possible without executing a command inside each Docker container and that's a boundary I'm not willing to cross also for privacy concerns. Here's a guide how to find out: https://superuser.com/questions/1183454/finding-out-the-veth-interface-of-a-docker-container Another possibility would be stopping all Dockers and then bring them up one by one and look at the interface table in between starts which new virtual interface appears when which Docker is started. 1 Quote Link to comment
nolan879 Posted March 18 Share Posted March 18 Much appreciated! I'll have to make a list of which interface is for which container in the mean time. Hope to see a custom "Friendly name" feature in the future. 1 Quote Link to comment
stefan marton Posted March 18 Share Posted March 18 4 hours ago, Rysz said: rm /tmp/plugins/pluginPending/* thanks work great 1 Quote Link to comment
Skylinar Posted March 18 Share Posted March 18 Great work, i've installed it directly to all of my servers. Thanks for the work! 1 Quote Link to comment
Rysz Posted March 19 Author Share Posted March 19 11 hours ago, nolan879 said: Much appreciated! I'll have to make a list of which interface is for which container in the mean time. Hope to see a custom "Friendly name" feature in the future. I've figured out a way to implement the feature without interacting with the Docker containers and VMs themselves. I've just pushed an update with the new setting (disabled by default), so please let me know if it works for you... 🙂 1 2 1 Quote Link to comment
Skylinar Posted March 19 Share Posted March 19 Works like a charm for me, thanks again! 1 Quote Link to comment
Squid Posted March 21 Share Posted March 21 On 3/18/2024 at 1:04 PM, stefan marton said: ! Not valid! Did that "! Not valid!" actually show up in the popup within CA? Quote Link to comment
Rysz Posted March 22 Author Share Posted March 22 Thanks for the feedback everyone - glad everything seems to be running as it should. 🙂 Quote Link to comment
shadowd1000 Posted March 22 Share Posted March 22 Just a note... Make sure to uninstall network stats plugin before installing this one. I had it installed and tried installing it. It didn't show any warnings or errors just blank installation window. Quote Link to comment
Rysz Posted March 22 Author Share Posted March 22 (edited) 35 minutes ago, shadowd1000 said: Just a note... Make sure to uninstall network stats plugin before installing this one. I had it installed and tried installing it. It didn't show any warnings or errors just blank installation window. Weird, it should show an error that it's not compatible in the installation window: Edited March 22 by Rysz Quote Link to comment
sonic6 Posted April 15 Share Posted April 15 Is it possible, that your plugin spammed my syslog with something like this: Apr 15 07:01:16 Unraid-1 lldpd[9825]: unable to bind to raw socket for interface veth052f133: No such device Apr 15 07:01:16 Unraid-1 lldpd[9827]: unable to initialize veth052f133 Apr 15 07:01:16 Unraid-1 lldpd[9825]: unable to bind to raw socket for interface vetha376979: No such device Apr 15 07:01:16 Unraid-1 lldpd[9827]: unable to initialize vetha376979 even when the Start DVM service is stopped? i got after i restarted the Docker Service (not the whole server). Also this, after i unistalled the plugin: Apr 15 07:20:44 Unraid-1 nginx: 2024/04/15 07:20:44 [error] 16158#16158: *1736042 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.6, server: , request: "GET /plugins/dwdvm/include/dwdvm_report.php?mode=footer HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.0.50:50080", referrer: "http://192.168.0.50:50080/Plugins" Apr 15 07:21:15 Unraid-1 nginx: 2024/04/15 07:21:15 [error] 16158#16158: *1736043 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.6, server: , request: "GET /plugins/dwdvm/include/dwdvm_report.php?mode=footer HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.0.50:50080", referrer: "http://192.168.0.50:50080/Plugins" Apr 15 07:22:03 Unraid-1 nginx: 2024/04/15 07:22:03 [error] 16158#16158: *1736043 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.6, server: , request: "GET /plugins/dwdvm/include/dwdvm_report.php?mode=footer HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.0.50:50080", referrer: "http://192.168.0.50:50080/Plugins" Apr 15 07:23:03 Unraid-1 nginx: 2024/04/15 07:23:03 [error] 16158#16158: *1736720 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.6, server: , request: "GET /plugins/dwdvm/include/dwdvm_report.php?mode=footer HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.0.50:50080", referrer: "http://192.168.0.50:50080/Plugins" Apr 15 07:24:03 Unraid-1 nginx: 2024/04/15 07:24:03 [error] 16158#16158: *1736998 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.6, server: , request: "GET /plugins/dwdvm/include/dwdvm_report.php?mode=footer HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.0.50:50080", referrer: "http://192.168.0.50:50080/Plugins" Apr 15 07:24:33 Unraid-1 nginx: 2024/04/15 07:24:33 [error] 16158#16158: *1736998 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.6, server: , request: "GET /plugins/dwdvm/include/dwdvm_report.php?mode=footer HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.0.50:50080", referrer: "http://192.168.0.50:50080/Plugins" Diagnostic ist attached unraid-1-diagnostics-20240415-0732.zip Quote Link to comment
Rysz Posted April 15 Author Share Posted April 15 13 minutes ago, sonic6 said: Is it possible, that your plugin spammed my syslog with something like this: Apr 15 07:01:16 Unraid-1 lldpd[9825]: unable to bind to raw socket for interface veth052f133: No such device Apr 15 07:01:16 Unraid-1 lldpd[9827]: unable to initialize veth052f133 Apr 15 07:01:16 Unraid-1 lldpd[9825]: unable to bind to raw socket for interface vetha376979: No such device Apr 15 07:01:16 Unraid-1 lldpd[9827]: unable to initialize vetha376979 even when the Start DVM service is stopped? i got after i restarted the Docker Service (not the whole server). Also this, after i unistalled the plugin: Apr 15 07:20:44 Unraid-1 nginx: 2024/04/15 07:20:44 [error] 16158#16158: *1736042 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.6, server: , request: "GET /plugins/dwdvm/include/dwdvm_report.php?mode=footer HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.0.50:50080", referrer: "http://192.168.0.50:50080/Plugins" Apr 15 07:21:15 Unraid-1 nginx: 2024/04/15 07:21:15 [error] 16158#16158: *1736043 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.6, server: , request: "GET /plugins/dwdvm/include/dwdvm_report.php?mode=footer HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.0.50:50080", referrer: "http://192.168.0.50:50080/Plugins" Apr 15 07:22:03 Unraid-1 nginx: 2024/04/15 07:22:03 [error] 16158#16158: *1736043 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.6, server: , request: "GET /plugins/dwdvm/include/dwdvm_report.php?mode=footer HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.0.50:50080", referrer: "http://192.168.0.50:50080/Plugins" Apr 15 07:23:03 Unraid-1 nginx: 2024/04/15 07:23:03 [error] 16158#16158: *1736720 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.6, server: , request: "GET /plugins/dwdvm/include/dwdvm_report.php?mode=footer HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.0.50:50080", referrer: "http://192.168.0.50:50080/Plugins" Apr 15 07:24:03 Unraid-1 nginx: 2024/04/15 07:24:03 [error] 16158#16158: *1736998 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.6, server: , request: "GET /plugins/dwdvm/include/dwdvm_report.php?mode=footer HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.0.50:50080", referrer: "http://192.168.0.50:50080/Plugins" Apr 15 07:24:33 Unraid-1 nginx: 2024/04/15 07:24:33 [error] 16158#16158: *1736998 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.6, server: , request: "GET /plugins/dwdvm/include/dwdvm_report.php?mode=footer HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.0.50:50080", referrer: "http://192.168.0.50:50080/Plugins" Diagnostic ist attached unraid-1-diagnostics-20240415-0732.zip 330.21 kB · 0 downloads No, the first message actually seems to come from the LLDP plugin which tries to send LLDP beacons from virtual interfaces (which doesn't work). That's actually useful information because that needs fixing (will push an update ASAP), so that it only does it from physical interfaces. The second message is normal after uninstallation and will only occur until the page is reloaded because after uninstallation the client side JS footer code is still there and looking for a no longer existing script until you reload the browser page at which point the code will be completely gone. Quote Link to comment
sonic6 Posted April 15 Share Posted April 15 3 minutes ago, Rysz said: actually seems to come from the LLDP plugin damn, totaly missed that plugin in my mind but good that you are also the dev of this plugin 3 minutes ago, Rysz said: will only occur until the page is reloaded ahh okay. it is gone. thank you! Quote Link to comment
Rysz Posted April 15 Author Share Posted April 15 8 minutes ago, sonic6 said: damn, totaly missed that plugin in my mind but good that you are also the dev of this plugin ahh okay. it is gone. thank you! Just updated it, should be fixed with the new update. 🙂 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.