Bug 802531

Summary: vnstatd service does not run
Product: [Fedora] Fedora Reporter: bugfinder <blackcode>
Component: vnstatAssignee: Adrian Reber <adrian>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: adrian
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-16 07:41:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description bugfinder 2012-03-12 18:32:45 UTC
Description of problem:
The init.d script indicates that the service was started successfully but it does not appear in the process list and the vnstat database is never updated.

Version-Release number of selected component (if applicable):
1.11


How reproducible:
Everytime

Additional info:
I've also tried it with SELinux set in permissive mode and the result is the same.

[root@system ~]# service vnstat restart
Restarting vnstat (via systemctl):                         [  OK  ]
[root@system ~]# ps ax | grep vnstat
 3785 pts/1    S+     0:00 grep --color=auto vnstat
[root@system ~]# ls -Zal /var/lib/vnstat
total 16
drwxr-xr-x.  2 system_u:object_r:vnstatd_var_lib_t:s0 vnstat vnstat 4096 Mar 12 23:26 .
drwxr-xr-x. 42 system_u:object_r:var_lib_t:s0   root   root   4096 Mar  7 22:52 ..
-rw-r--r--.  1 unconfined_u:object_r:vnstatd_var_lib_t:s0 vnstat vnstat 2792 Mar 12 23:51 em1
-rw-r--r--.  1 unconfined_u:object_r:vnstatd_var_lib_t:s0 vnstat vnstat 2792 Mar 12 23:51 .em1

Comment 1 Adrian Reber 2012-03-13 08:57:55 UTC
Please specify the exact version of vnstat.

Comment 2 bugfinder 2012-03-13 17:12:13 UTC
vnstat-1.11-2.fc16.x86_64

Comment 3 Adrian Reber 2012-03-15 16:27:10 UTC
Please try vnstat-1.11-6 from updates-testing. It should hit updates soon.

Comment 4 bugfinder 2012-03-16 04:58:17 UTC
Just tried vnstat-1.11-6.

The problem is fixed now. Thanks!