• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

Vnstat2 problems

2.2 Snapshot Feedback and Problems - RETIRED
6
8
4.9k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A
    athurdent
    last edited by Nov 12, 2014, 6:27 AM

    I'm on the lastest beta, using a D200 notebook as test machine. It has only one Gigabit interface, so WAN1, WAN2 etc are tagged VLANs.
    All Interfaces (the real one an the VLANs) show up as 1000baseT <full-duplex>in ifconfig though.

    When I start a bigger download with over 100MBit, vnstats Cron job starts to send those mails until the transfer is over:

    X-Cron-Env: <shell= bin="" sh="">
    X-Cron-Env: <path= etc:="" bin:="" sbin:="" usr="" sbin="">
    X-Cron-Env: <home= var="" log="">
    X-Cron-Env: <logname=root>
    X-Cron-Env: <user=root>
    
    Info: Traffic rate for "bge0" higher than set maximum 100 Mbit (60->825, r1587 t1588), syncing.
    Info: Traffic rate for "bge0_vlan666" higher than set maximum 100 Mbit (60->825, r1559 t55), syncing.</user=root></logname=root></home=></path=></shell=>
    

    Also the graphs do not work anymore:

    Screenshot_1.png
    Screenshot_1.png_thumb</full-duplex>

    1 Reply Last reply Reply Quote 0
    • A
      athurdent
      last edited by Nov 29, 2014, 8:35 AM

      With the latest snapshots it seems completely broken. I'm using a RAM disk for /tmp and /var on that system if it matters.

      
      X-Cron-Env: <shell= bin="" sh="">
      X-Cron-Env: <path= etc:="" bin:="" sbin:="" usr="" sbin="">
      X-Cron-Env: <home= var="" log="">
      X-Cron-Env: <logname=root>
      X-Cron-Env: <user=root>
      
      Error: Unable to open database directory "/var/lib/vnstat".
      Make sure it exists and is at least read enabled for current user.
      Exiting...</user=root></logname=root></home=></path=></shell=>
      
      1 Reply Last reply Reply Quote 0
      • G
        grandrivers
        last edited by Nov 29, 2014, 4:35 PM

        this is also present

        Notice: Undefined index: totalrx in /usr/local/www/vnstat2/index.php on line 81 Notice: Undefined index: totalrxk in /usr/local/www/vnstat2/index.php on line 81 Notice: Undefined index: totaltx in /usr/local/www/vnstat2/index.php on line 82 Notice: Undefined index: totaltxk in /usr/local/www/vnstat2/index.php on line 82 Notice: Illegal string offset 'rx' in /usr/local/www/vnstat2/index.php on line 89 Notice: Illegal string offset 'tx' in /usr/local/www/vnstat2/index.php on line 90 Notice: Illegal string offset 'rx' in /usr/local/www/vnstat2/index.php on line 94 Notice: Illegal string offset 'tx' in /usr/local/www/vnstat2/index.php on line 95 Notice: Illegal string offset 'rx' in /usr/local/www/vnstat2/index.php on line 99 Notice: Illegal string offset 'tx' in /usr/local/www/vnstat2/index.php on line 100

        This page contains the following errors:

        error on line 11 at column 8: Failed to parse QName 'Notice:'
        Below is a rendering of the page up to the first error.

        pfsense 2.4 super micro A1SRM-2558F
        C2558 8gig ECC  60gig SSD
        tripple Wan dual pppoe

        1 Reply Last reply Reply Quote 0
        • M
          Mr. Jingles
          last edited by Jan 9, 2015, 4:09 PM

          ;D ;D ;D ;D ;D

          This happened to me this afternoon (pic).

          DO delete 1300 vnstat emails in a program as comfortable as ms outlook  :P

          vnstat.png
          vnstat.png_thumb

          6 and a half billion people know that they are stupid, agressive, lower life forms.

          1 Reply Last reply Reply Quote 0
          • C
            Cino
            last edited by Jan 9, 2015, 9:33 PM

            not sure if this will help but the below patch corrects the "higher than set maximum 100 Mbit" error for me.. You could change the MaxBandwidth in the patch the max you have for your system..

            
            --- /usr/local/pkg/vnstat2/vnstat2.inc	2014-06-12 21:21:08.000000000 -0400
            +++ /root/custom/misc_files/vnstat2.inc	2014-06-22 10:39:15.000000000 -0400
            @@ -91,6 +91,11 @@
             # vnstati
             ##
            
            +# maximum bandwidth (Mbit) for all interfaces, 0 = disable feature
            +# (unless interface specific limit is given)
            +MaxBandwidth 0
            +
            +
             # image colors
             CBackground     "F0F0F0"
             CEdge           "AEAEAE"
            
            
            1 Reply Last reply Reply Quote 0
            • A
              athurdent
              last edited by Jan 18, 2015, 3:25 PM

              I think one of the problems with the installation might be this around line 149 in:

              https://github.com/pfsense/pfsense-packages/blob/master/config/vnstat2/vnstat2.inc

               // Check for pbi install and arch type then create symlinks
              if (file_exists('/usr/pbi/vnstat-i386')) { exec("ln -s /usr/local/etc/vnstat.conf /usr/pbi/vnstat-i386/etc/vnstat.conf"); }
              if (file_exists('/usr/pbi/vnstat-amd64')) { exec("ln -s /usr/local/etc/vnstat.conf /usr/pbi/vnstat-amd64/etc/vnstat.conf"); }
              

              trying this manually results in:

              ln -s /usr/local/etc/vnstat.conf /usr/pbi/vnstat-i386/etc/vnstat.conf
              ln: /usr/pbi/vnstat-i386/etc/vnstat.conf: File exists
              

              So vnstat2 keeps using the standard config and fails on us. Don't know about the packages installation logic but maybe just rm'ing the standard config first would do the trick?

              1 Reply Last reply Reply Quote 0
              • M
                mir
                last edited by Jan 18, 2015, 4:02 PM

                Doing the following made it work here:
                ln -sf /usr/local/etc/vnstat.conf /usr/pbi/vnstat-amd64/etc/vnstat.conf

                1 Reply Last reply Reply Quote 0
                • J
                  jimp Rebel Alliance Developer Netgate
                  last edited by Feb 3, 2015, 7:46 PM

                  vnstat2 should be working fine now on 2.2, reinstall it and give it another try.

                  Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                  Need help fast? Netgate Global Support!

                  Do not Chat/PM for help!

                  1 Reply Last reply Reply Quote 0
                  • First post
                    Last post
                  Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.