Navigation

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

    Updated from 2.0.3 to 2.1 - Traffic/Packets RRD Graph not working

    Installation and Upgrades
    4
    7
    1697
    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.
    • M
      moyorakkhi last edited by

      Hello,

      I've done auto upgrade from 2.0.3 to 2.1. All other things working properly. But none of the Traffic and Packets RRD Graphs working. System log showing this error:

      php: /status_rrd_graph_img.php: Failed to create graph with error code 1, the error is: ERROR: No DS called 'inpass6' in '/var/db/rrd/wan-traffic.rrd'/usr/bin/nice -n20 /usr/local/bin/rrdtool graph /tmp/wan-traffic.rrd-week.png --start 1379314809 --end 1379919609 --step 3600 --vertical-label "bits/sec" --color SHADEA#eeeeee --color SHADEB#eeeeee --title "`hostname` - WAN :: Traffic - 1 week - 1 hour average" --height 200 --width 620 DEF:wan-in_bytes_pass=/var/db/rrd/wan-traffic.rrd:inpass:AVERAGE:step=3600 DEF:wan-out_bytes_pass=/var/db/rrd/wan-traffic.rrd:outpass:AVERAGE:step=3600 DEF:wan-in_bytes_block=/var/db/rrd/wan-traffic.rrd:inblock:AVERAGE:step=3600 DEF:wan-out_bytes_block=/var/db/rrd/wan-traffic.rrd:outblock:AVERAGE:step=3600 DEF:wan-in6_bytes_pass=/var/db/rrd/wan-traffic.rrd:inpass6:AVERAGE:step=3600 DEF:wan-out6_bytes_pass=/var/db/rrd/wan-traffic.rrd:outpass6:AVERAGE:step=3600 DEF:wan-in6_bytes_block=/var/db/rrd/wan-traffic.rrd:inblock6:AVERAGE:step=3600 DEF:wan-out6_bytes_block
      

      I didn't go for the RRD data reset yet. Wondering if this issue can be resolved without resetting data.

      Looks like this Bug is still there: https://redmine.pfsense.org/issues/2651

      1 Reply Last reply Reply Quote 0
      • L
        lianderson last edited by

        The same problem with me.

        And the Quality graphic is in wrong scale. (e.g. : appears 100ms 200ms 300ms - but response is 0.10ms 0.20ms)

        Tks

        1 Reply Last reply Reply Quote 0
        • stephenw10
          stephenw10 Netgate Administrator last edited by

          If you have a ppp WAN connection you will find that the interface has been renamed in 2.1. What was previously named WAN is now called WAN_pppoe (or something similar). You might find that the graphs are there but under a different title.
          You are using some local device for gateway monitoring I presume? <1ms is too low for a real remote gateway. Unless you have some fancy hook up I'm unaware of maybe.  ;)

          Steve

          1 Reply Last reply Reply Quote 0
          • L
            lianderson last edited by

            My gateway monitoring is wrong. Has checked only the local gateway. The responses is very short.

            Scale OK after configure gateway monitor for the internet IP.

            The question of the Traffic and Packets graphs permanence.

            Tks

            1 Reply Last reply Reply Quote 0
            • L
              lianderson last edited by

              One client is with version RC1:

              2.1-RC1 (amd64)
              built on Thu Aug 15 03:12:29 EDT 2013
              FreeBSD 8.3-RELEASE-p9

              And the Graphs working fine!

              Tks

              1 Reply Last reply Reply Quote 0
              • L
                lianderson last edited by

                php: /status_rrd_graph_img.php: Failed to create graph with error code 1, the error is: ERROR: Could not parse color in ''/usr/bin/nice -n20 /usr/local/bin/rrdtool graph /tmp/wan-traffic.rrd-week.png –start 1380291333 --end 1380896133 --step 3600 --vertical-label "bits/sec" --color SHADEA#eeeeee --color SHADEB#eeeeee --title "hostname - WAN :: Traffic - 1 week - 1 hour average" --height 200 --width 620 DEF:wan-in_bytes_pass=/var/db/rrd/wan-traffic.rrd:inpass:AVERAGE:step=3600 DEF:wan-out_bytes_pass=/var/db/rrd/wan-traffic.rrd:outpass:AVERAGE:step=3600 DEF:wan-in_bytes_block=/var/db/rrd/wan-traffic.rrd:inblock:AVERAGE:step=3600 DEF:wan-out_bytes_block=/var/db/rrd/wan-traffic.rrd:outblock:AVERAGE:step=3600 DEF:wan-in6_bytes_pass=/var/db/rrd/wan-traffic.rrd:inpass6:AVERAGE:step=3600 DEF:wan-out6_bytes_pass=/var/db/rrd/wan-traffic.rrd:outpass6:AVERAGE:step=3600 DEF:wan-in6_bytes_block=/var/db/rrd/wan-traffic.rrd:inblock6:AVERAGE:step=3600 DEF:wan-out6_bytes_block=/var/db/rrd/wan-traffic.rrd

                1 Reply Last reply Reply Quote 0
                • A
                  alpaca last edited by

                  Have got the same problem.
                  Is there a fix? I couldn't see anything in the bug reports.

                  Regards,
                  Sebastian

                  1 Reply Last reply Reply Quote 0
                  • First post
                    Last post