October 5, 20187 yr Author pidfile in rc.vnstat is telling the pid is supposed to be found Yeah I am going to double check things as I thought I was altering it. But I’ll double check everything and cut a new release tomorrow
October 5, 20187 yr ok, got it working what I did was: changed PIDFILE=/var/run/vnstat/vnstat.pid and in the start line added -p $PIDFILE rest was untouched and this is what I get i have to Shift Reload Page to get the graphs to update, leaving to another menu and coming back, it does not update Edited October 5, 20187 yr by MyKroFt
October 6, 20187 yr Still not working.... Installed latest version, after installation I see in the logs: Oct 5 21:42:57 Tower vnstatd[24665]: vnStat daemon 1.18 started. (pid:24665 uid:0 gid:0) Oct 5 21:42:57 Tower vnstatd[24665]: Monitoring: bond0 (2000 Mbit) eth0 (1000 Mbit) eth1 (1000 Mbit) The settings page says Stopped Try to start and the log says: Oct 5 21:46:44 Tower vnstatd[31073]: Error: pidfile "/var/run/vnstat.pid" lock failed (Resource temporarily unavailable), exiting. no PID of 31073 is running, but PID 24665 (vnstatd) is running /etc/rc.d/rc.vnstat status returns vnstat daemon is not running.
October 6, 20187 yr 8 hours ago, dorgan said: Just pushed out an updated version that should correct this. I dont see a new version, just check plugins page and latest version is 2018.10.03?
October 6, 20187 yr 42 minutes ago, dukiethecorgi said: Mine shows 2018.10.05 Because you installed that version from scratch 54 minutes ago, MyKroFt said: I dont see a new version, just check plugins page and latest version is 2018.10.03? Because there's an error in the .plg file @dorgan, <!ENTITY pluginURL "$gitURL;/&name;.plg"> should be <!ENTITY pluginURL "&gitURL;/&name;.plg"> Once this is fixed, anyone who has previously installed the plugin will need to uninstall and then reinstall it for any future updates to be found.
October 6, 20187 yr Author Thanks, I’ll get this corrected. And take a look at the plugin again. Maybe uninstall, restart the server and reinstall the plugin and get this all corrected.
October 6, 20187 yr I just tried same as the other users and still is not working. I even deleted the plugin and restarted the server. This looks promising, I'll check next week to see if it's up. I'm using Version: 6.6.1 Edited October 6, 20187 yr by gacpac
October 6, 20187 yr 8 hours ago, dorgan said: Thanks, I’ll get this corrected. And take a look at the plugin again. Maybe uninstall, restart the server and reinstall the plugin and get this all corrected. That's what I tried, removed old version and installed from scratch
October 6, 20187 yr Author It has to be something that’s cached in my setup. Because I’ve removed and reinstalled the plugin multiple times and it works just fine. So I’ll uninstall it and restart the server before reinstalling again. Hopefully that will help me track down the issue.
October 6, 20187 yr Author @dukiethecorgi @gacpac @Squid - Alright, I fixed some paths and I believe all the right config files and pid paths are now being put in place. 2018.10.06a is out Edited October 6, 20187 yr by dorgan
October 6, 20187 yr Hi, so I just installed 2018.10.06a and get the same message as others were earlier. Oct 6 15:06:03 UnraidTower vnstatd[15224]: Error: pidfile "/var/run/vnstat.pid" lock failed (Resource temporarily unavailable), exiting /etc/rc.d/rc.vnstat status vnstat daemon is not running. /etc/rc.d/rc.vnstat start Starting the vnstat daemon... Error: pidfile lock: Resource temporarily unavailable Thoughts?
October 6, 20187 yr Author Hi, so I just installed 2018.10.06a and get the same message as others were earlier. Oct 6 15:06:03 UnraidTower vnstatd[15224]: Error: pidfile "/var/run/vnstat.pid" lock failed (Resource temporarily unavailable), exiting /etc/rc.d/rc.vnstat status vnstat daemon is not running. /etc/rc.d/rc.vnstat start Starting the vnstat daemon... Error: pidfile lock: Resource temporarily unavailable Thoughts? It shouldn’t even be using that location. I wonder, can you try a restart of unraid, and see if things come up properly?
October 6, 20187 yr One reboot later and still the same I am afraid. Oct 6 15:29:02 UnraidTower vnstatd[11262]: Error: pidfile "/var/run/vnstat.pid" lock failed (Resource temporarily unavailable), exiting. Linux 4.18.10-unRAID. /etc/rc.d/rc.vnstat start Starting the vnstat daemon... Error: pidfile lock: Resource temporarily unavailable /etc/rc.d/rc.vnstat status vnstat daemon is not running. Anything else you need let me know.
October 6, 20187 yr Fresh install, I saw your first post on this and have been waiting till you thought you had it sorted.
October 6, 20187 yr Author Fresh install, I saw your first post on this and have been waiting till you thought you had it sorted.Hmm something seriously weird here, as I’ve now uninstall, restarted machine and then reinstalled and things are working just fine.Can you me what it says for DBLocation in /etc/vnstat.conf and what it says for PIDFILE in /etc/rc.d/rc.vnstat?
October 6, 20187 yr rc.vnstat CONFIGFILE=/etc/vnstat.conf PIDFILE=/var/run/vnstat/vnstat.pid DAEMON=vnstatd vnstat.conf # location of the database directory DatabaseDir "/var/lib/vnstat" # file used as daemon pid / lock file PidFile "/var/run/vnstat.pid" Added the pid lock file location from vnstat.conf as well.
October 6, 20187 yr Author rc.vnstat CONFIGFILE=/etc/vnstat.conf PIDFILE=/var/run/vnstat/vnstat.pid DAEMON=vnstatd vnstat.conf # location of the database directory DatabaseDir "/var/lib/vnstat" # file used as daemon pid / lock file PidFile "/var/run/vnstat.pid" Added the pid lock file location from vnstat.conf as well. Ok the PIDFILE location looks good, let me try to have the install manual create that folder. DatabaseDir is not correct, which means it’s not copying the vnstat.conf from /user/local/emhttp/plugins/network stats/vnstat.conf over to /etc/vnstat.conf
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.