Bug 697930 - Statistics produced by vnstat are incorrect
Summary: Statistics produced by vnstat are incorrect
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: vnstat
Version: 15
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Adrian Reber
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-19 16:52 UTC by afanen01
Modified: 2011-05-25 07:51 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-25 07:51:07 UTC
Type: ---


Attachments (Terms of Use)

Description afanen01 2011-04-19 16:52:57 UTC
Description of problem:
Vnstat shows my network traffic for today as 580.37GiB (down) and 15.55GiB up, with an average rate of 79.23Mbit/s.

This is not correct, since it has been running for about 5 hours only, and my network speed is 10Mbit/s (down) and 1Mbit/s (up). The figures are clearly not correct.


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

How reproducible:
Encountered issue on a clean install.

Steps to Reproduce:

Install vnstat, create the initial configuration, and start the vnstat service. You need to give it permissive selinux policy for it to work.
  
Actual results:
monitoring works fine, but produces incorrect statistics

Expected results:
monitoring works and produces plausible statistics

Additional info:

Comment 1 Adrian Reber 2011-04-20 08:13:37 UTC
Is this only on the first day wrong or is it wrong every day?

Have you tried to set the maximum bandwidth in the config file?

I am using it on 10 and 4 GBit/s and have not seen anything like that yet.

Comment 2 afanen01 2011-04-20 18:23:11 UTC
I checked, and the maximum bandwidth was actually 0 in the config. I fixed that, deleted the database for eth0, created a new one, and restarted the service and it seems to be working working fine now.


Note You need to log in before you can comment on or make changes to this bug.