On boot/reboot vnstat fails to start from systemd. Restart after boot, works fine. From CLI: ### A few minutes after reboot. [root@number1 ~]# systemctl -l --no-pager status vnstat ● vnstat.service - vnStat - a lightweight network traffic monitor Loaded: loaded (/usr/lib/systemd/system/vnstat.service; enabled; vendor preset: disabled) Active: inactive (dead) since Thu 2021-03-11 23:09:17 EST; 9min ago Process: 15217 ExecStart=/usr/sbin/vnstatd -d (code=killed, signal=HUP) Process: 15244 ExecReload=/bin/kill -HUP $MAINPID (code=exited, status=0/SUCCESS) Main PID: 15217 (code=killed, signal=HUP) CPU: 9ms Mar 11 23:09:14 number1.jameswhitby.net systemd[1]: Started vnStat - a lightweight network traffic monitor. Mar 11 23:09:16 number1.jameswhitby.net systemd[1]: Reloading vnStat - a lightweight network traffic monitor. Mar 11 23:09:17 number1.jameswhitby.net systemd[1]: vnstat.service: Can't open PID file /run/vnstat/vnstat.pid (yet?) after reload: Operation not permitted Mar 11 23:09:17 number1.jameswhitby.net systemd[1]: Reloaded vnStat - a lightweight network traffic monitor. Mar 11 23:09:17 number1.jameswhitby.net systemd[1]: vnstat.service: Succeeded. [root@number1 ~]# systemctl -l --no-pager restart vnstat [root@number1 ~]# systemctl -l --no-pager status vnstat ● vnstat.service - vnStat - a lightweight network traffic monitor Loaded: loaded (/usr/lib/systemd/system/vnstat.service; enabled; vendor preset: disabled) Active: active (running) since Thu 2021-03-11 23:20:51 EST; 10s ago Main PID: 119706 (vnstatd) Tasks: 1 (limit: 28753) Memory: 892.0K CPU: 8ms CGroup: /system.slice/vnstat.service └─119706 /usr/sbin/vnstatd -d ### A restart shows Mar 11 23:20:51 number1.jameswhitby.net systemd[1]: Started vnStat - a lightweight network traffic monitor. [root@number1 ~]# ###although done much later and several reboots later, this is the status after the restart. [root@number1 ~]# systemctl -l --no-pager status vnstat ● vnstat.service - vnStat - a lightweight network traffic monitor Loaded: loaded (/usr/lib/systemd/system/vnstat.service; enabled; vendor preset: disabled) Active: active (running) since Sat 2021-03-13 16:24:12 EST; 4h 17min ago Main PID: 1509642 (vnstatd) Tasks: 1 (limit: 28753) Memory: 1.1M CPU: 507ms CGroup: /system.slice/vnstat.service └─1509642 /usr/sbin/vnstatd -d Mar 13 16:24:12 number1.jameswhitby.net systemd[1]: Started vnStat - a lightweight network traffic monitor
This one is strange. I have vnstat and vnstatd both running ok. The file /run/vnstat/vnstat.pid does not exist, nor the directory /run/vnstat. Did you install vnstat manually or was it added by selecting monitoring of the interface in mcc? If the latter then this is a duplicate of bug 15961 which is being worked on. If the former, I have no idea how to debug this. Once enabled, its working on my system. The directory/file /run/vnstat/vnstat.pid does not exist with it working.
CC: (none) => davidwhodgins
I didn't do anything except upgrade from 7.
Hello, I might have think it can be a duplicate of bug https://bugs.mageia.org/show_bug.cgi?id=28576 , but the error message is not the same. Maybe you can try the package in updates testing ?
CC: (none) => joe_c_moi
CC: joe_c_moi => (none)
Will try the update in testing later today. Thanks
That did it. [root@number1 ~]# systemctl -l --no-pager status vnstat ● vnstat.service - vnStat network traffic monitor Loaded: loaded (/usr/lib/systemd/system/vnstat.service; enabled; vendor preset: disabled) Active: active (running) since Sun 2021-03-14 12:22:18 EDT; 26min ago Docs: man:vnstatd(8) man:vnstat(1) man:vnstat.conf(5) Process: 15278 ExecReload=/bin/kill -HUP $MAINPID (code=exited, status=0/SUCCESS) Main PID: 15248 (vnstatd) Tasks: 1 (limit: 28753) Memory: 1.1M CPU: 120ms CGroup: /system.slice/vnstat.service └─15248 /usr/sbin/vnstatd -n Mar 14 12:22:18 number1.jameswhitby.net systemd[1]: Started vnStat network traffic monitor. Mar 14 12:22:20 number1.jameswhitby.net vnstatd[15248]: Info: vnStat daemon 2.6 started. (pid:15248 uid:0 gid:0 64-bit) Mar 14 12:22:20 number1.jameswhitby.net vnstatd[15248]: Info: Monitoring (1): enp6s0 (1000 Mbit) Mar 14 12:22:20 number1.jameswhitby.net systemd[1]: Reloading vnStat network traffic monitor. Mar 14 12:22:21 number1.jameswhitby.net vnstatd[15248]: Info: SIGHUP received, flushing data to disk and reloading config. Mar 14 12:22:21 number1.jameswhitby.net systemd[1]: Reloaded vnStat network traffic monitor. Mar 14 12:22:40 number1.jameswhitby.net vnstatd[15248]: Info: Monitoring (1): enp6s0 (1000 Mbit) [
That did it.After reboot. [root@number1 ~]# systemctl -l --no-pager status vnstat ● vnstat.service - vnStat network traffic monitor Loaded: loaded (/usr/lib/systemd/system/vnstat.service; enabled; vendor preset: disabled) Active: active (running) since Sun 2021-03-14 12:22:18 EDT; 26min ago Docs: man:vnstatd(8) man:vnstat(1) man:vnstat.conf(5) Process: 15278 ExecReload=/bin/kill -HUP $MAINPID (code=exited, status=0/SUCCESS) Main PID: 15248 (vnstatd) Tasks: 1 (limit: 28753) Memory: 1.1M CPU: 120ms CGroup: /system.slice/vnstat.service └─15248 /usr/sbin/vnstatd -n Mar 14 12:22:18 number1.jameswhitby.net systemd[1]: Started vnStat network traffic monitor. Mar 14 12:22:20 number1.jameswhitby.net vnstatd[15248]: Info: vnStat daemon 2.6 started. (pid:15248 uid:0 gid:0 64-bit) Mar 14 12:22:20 number1.jameswhitby.net vnstatd[15248]: Info: Monitoring (1): enp6s0 (1000 Mbit) Mar 14 12:22:20 number1.jameswhitby.net systemd[1]: Reloading vnStat network traffic monitor. Mar 14 12:22:21 number1.jameswhitby.net vnstatd[15248]: Info: SIGHUP received, flushing data to disk and reloading config. Mar 14 12:22:21 number1.jameswhitby.net systemd[1]: Reloaded vnStat network traffic monitor. Mar 14 12:22:40 number1.jameswhitby.net vnstatd[15248]: Info: Monitoring (1): enp6s0 (1000 Mbit) Please mark as resolved, as far as I am concerned. Thanks [
Ok. Closing as a duplicate of bug 28576. Thanks for the update. *** This bug has been marked as a duplicate of bug 28576 ***
Status: NEW => RESOLVEDResolution: (none) => DUPLICATE
(In reply to Dave Hodgins from comment #1) > Did you install vnstat manually or was it added by selecting monitoring > of the interface in mcc? > If the latter then this is a duplicate of bug 15961 which is being worked on. I think you meant bug 15691 (re network accounting). (In reply to james Whitby from comment #4 #5 #6) > Will try the update in testing later today. > That did it > That did it.After reboot > Please mark as resolved, as far as I am concerned Thank you for the prompt feedback. And to Nicolas Nicolas for the update pointer. I was going to assign this to QA...