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

    RRD graphing

    Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
    62 Posts 9 Posters 40.3k Views
    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.
    • D
      databeestje
      last edited by

      I finally added backend support in the gateway groups for the dynamic interfaces.

      Possibly failover even works.

      Not sure about the RRD graphs, it might even work.

      1 Reply Last reply Reply Quote 0
      • N
        nocer
        last edited by

        Thanks databeestje, let me grab new 2.0 snaps.

        BTW: I'm still having annoying "php: : Could not find gateway for interface(wan)." messages in the syslog. Could someone tell me how I can stop it. Gateway is of course configured properly, and always green by apinger.

        cheers,

        1 Reply Last reply Reply Quote 0
        • D
          databeestje
          last edited by

          That's fixed too.

          1 Reply Last reply Reply Quote 0
          • N
            nocer
            last edited by

            Hi,

            Finally catch the latest snap and my box has been up-to-date. I also noticed that the kernel has already moved to 7.1, WOW!

            YES - all the RRD thingy works fine now including "Quality" tab, and annoying PHP messages are gone. Thank you :D

            BTW, I happened to have found that apinger now picks my WAN address correctly but also picks a non existing address, 127.0.0.2, too then the following is logged to syslog;

            Nov 10 11:29:22 apinger: ALARM: wan(127.0.0.2) *** down ***

            Of course, apinger creates its config while booting so that deleting 127.0.0.2 from the config doesn't help(unless you never reboot). Hope this would be cleared in the next snap.

            cheers,

            1 Reply Last reply Reply Quote 0
            • N
              nocer
              last edited by

              Hi

              Apologies for frequent post…Can't get "Processor" graph correctly at this time. I normally see both # of processes and % of CPU usage but no CPU% is shown in the graph. # of processes is shown correct. Deleted all the *.rrd in /var/db/rrd and reboot the box, neither helps. I don't see the "divided by zero" errors as other members reported, yet.

              2.0-ALPHA-ALPHA
              built on Sun Nov 9 20:34:03 EST 2008
              FreeBSD 7.1-PRERELEASE

              cheers,

              1 Reply Last reply Reply Quote 0
              • D
                databeestje
                last edited by

                You should now be able to assign a different monitor IP to a dynamic interface.
                Ofcourse this needs testing.

                I update the backend rrd code to make sure it finds this new address. Otherwise it'll use the gateway.

                The processor graph I don't know. I have not tracked rrd too closely over the course of 1.3 -> 2.0

                1 Reply Last reply Reply Quote 0
                • N
                  nocer
                  last edited by

                  Hello,

                  Just up to the latest, still can't get CPU graph in RRD, and now Quality too broken again.
                  As for the gateway, 127.0.0.2 still there and can't be deleted from the gateway list.

                  2.0-ALPHA-ALPHA
                  built on Sat Nov 15 19:40:31 EST 2008
                  FreeBSD 7.1-PRERELEASE

                  I will revert to previous build.
                  cheers,

                  1 Reply Last reply Reply Quote 0
                  • M
                    mino
                    last edited by

                    Hi,

                    at first great job databeestje, i can set successfull an alternative ip for my wan interface. The "Gateway Status" in the Dashboard is now working correctly, the quality graph isnt and the single gateway status is also working correctly working. I think the messages in the logs are created by the rrd graph process.

                    cpu_grap.png
                    cpu_grap.png_thumb
                    logs.png
                    logs.png_thumb
                    quality_graph.png
                    quality_graph.png_thumb
                    status_gateways.png
                    status_gateways.png_thumb

                    Running:   2.0-ALPHA-ALPHA
                    built on Mon Jan 26 03:00:33 EST 2009
                    FreeBSD 7.1-RELEASE-p2
                    IRC Nick: mino

                    1 Reply Last reply Reply Quote 0
                    • N
                      nocer
                      last edited by

                      Hi mino,

                      Ah, I should have attached those rrd graphs…not showing cpu and quality correct. Thank you!
                      No cpu graph, no quality graph, that is happening with the latest. Both used to work fine somewhere around 8/Nov builds.

                      cheers,

                      1 Reply Last reply Reply Quote 0
                      • M
                        mino
                        last edited by

                        Okay now the quality graph is working correctly. The cpu graph problem and the log messages about "php: : Could not find gateway for interface(pptp)." are still present.

                        Running:   2.0-ALPHA-ALPHA
                        built on Mon Jan 26 03:00:33 EST 2009
                        FreeBSD 7.1-RELEASE-p2
                        IRC Nick: mino

                        1 Reply Last reply Reply Quote 0
                        • S
                          sullrich
                          last edited by

                          Fixed, thanks

                          1 Reply Last reply Reply Quote 0
                          • N
                            nocer
                            last edited by

                            Hello,

                            Hmm…doesn't seems to be fixed. Still have cpu graph issue, and quality graph back to ALL RED. Still getting

                            Nov 19 08:51:08 apinger: ALARM: wan(127.0.0.2) *** down ***

                            for the gateway 127.0.0.2 which I have never ever configured.

                            cheers,

                            EDIT: 2.0-ALPHA-ALPHA built on Tue Nov 18 17:47:36 EST 2008 FreeBSD 7.1-PRERELEASE

                            1 Reply Last reply Reply Quote 0
                            • M
                              mino
                              last edited by

                              With the latest snapshort RRD is again working but all Gateway Displays say "offline". And CPU Graph is still not working (like before).

                              Running:   2.0-ALPHA-ALPHA
                              built on Mon Jan 26 03:00:33 EST 2009
                              FreeBSD 7.1-RELEASE-p2
                              IRC Nick: mino

                              1 Reply Last reply Reply Quote 0
                              • D
                                databeestje
                                last edited by

                                127.0.0.2 is for interfaces which are dynamic and down. Atleast that's what they should be.

                                What is you wan? The gateway code is untested with pppoe or pptp. So I can't really tell.

                                dump the output from the php command

                                print_r(return_gateways_array());

                                and

                                print_r(return_gateways_status());

                                Thanks.

                                1 Reply Last reply Reply Quote 0
                                • N
                                  nocer
                                  last edited by

                                  Hi,

                                  Just loaded the latest 2.0-ALPHA-ALPHA built on Tue Nov 25 14:59:09 EST 2008 and still no CPU graph, also found the following while re-creating entire RRD graph;

                                  Nov 26 14:56:32 php: /status_rrd_graph_img.php: Failed to create graph with error code 1, the error is: ERROR: No DS called 'delay' in '/var/db/rrd/wan-quality.rrd'
                                  Nov 26 14:56:32 php: /status_rrd_graph_img.php: Failed to create graph with error code 1, the error is: ERROR: No DS called 'delay' in '/var/db/rrd/wan-quality.rrd'
                                  Nov 26 14:56:32 php: /status_rrd_graph_img.php: Failed to create graph with error code 1, the error is: ERROR: No DS called 'delay' in '/var/db/rrd/wan-quality.rrd'
                                  Nov 26 14:56:31 php: /status_rrd_graph_img.php: Failed to create graph with error code 1, the error is: ERROR: No DS called 'delay' in '/var/db/rrd/wan-quality.rrd'
                                  Nov 26 14:56:31 php: /status_rrd_graph_img.php: Failed to create graph with error code 1, the error is: ERROR: No DS called 'delay' in '/var/db/rrd/wan-quality.rrd'
                                  Nov 26 14:56:31 php: /status_rrd_graph_img.php: Failed to create graph with error code 1, the error is: ERROR: No DS called 'delay' in '/var/db/rrd/wan-quality.rrd'
                                  Nov 26 14:56:31 php: /status_rrd_graph_img.php: Failed to create graph with error code 1, the error is: ERROR: No DS called 'delay' in '/var/db/rrd/wan-quality.rrd'

                                  And,

                                  dump the output from the php command

                                  print_r(return_gateways_array());

                                  and

                                  print_r(return_gateways_status());

                                  gives me nothing ; My WAN is PPPoE.

                                  pfSense console setup


                                  0)  Logout (SSH only)
                                  1)  Assign Interfaces
                                  2)  Set interface(s) IP address
                                  3)  Reset webConfigurator password
                                  4)  Reset to factory defaults
                                  5)  Reboot system
                                  6)  Halt system
                                  7)  Ping host
                                  8)  Shell
                                  9)  PFtop
                                  10)  Filter Logs
                                  11)  Restart webConfigurator
                                  12)  pfSense PHP shell
                                  13)  Upgrade from console
                                  14)  Disable Secure Shell (sshd)

                                  Enter an option: 12

                                  Starting the pfSense shell system…...........

                                  Welcome to the pfSense php shell system
                                  Written by Scott Ullrich (sullrich@gmail.com)

                                  Type "help" to show common usage scenarios.

                                  Available playback commands:
                                       cvssync disabledhcpd enableallowallwan removepkgconfig restartdhcpd restartftphelper restartipsec

                                  pfSense shell: print_r(return_gateways_array());
                                  pfSense shell:
                                  pfSense shell: print_r(return_gateways_status());
                                  pfSense shell:
                                  pfSense shell:

                                  cheers,

                                  1 Reply Last reply Reply Quote 0
                                  • S
                                    sullrich
                                    last edited by

                                    You need:

                                    exec

                                    After the command..

                                    pfSense shell: print_r(return_gateways_array());
                                    pfSense shell: exec

                                    1 Reply Last reply Reply Quote 0
                                    • N
                                      nocer
                                      last edited by

                                      Thanks sullrich,

                                      @sullrich:

                                      You need:

                                      exec

                                      After the command..

                                      pfSense shell: print_r(return_gateways_array());
                                      pfSense shell: exec

                                      pfSense shell: print_r(return_gateways_array());
                                      pfSense shell: exec
                                      Array
                                      (
                                          [0] => Array
                                              (
                                                  [gateway] => 127.0.0.2
                                                  [interface] => wan
                                                  [monitor] => 127.0.0.2
                                                  [name] => wan
                                                  [descr] => Interface WAN Gateway
                                                  [attribute] => system
                                              )

                                      [1] => Array
                                              (
                                                  [gateway] => 210.xxx.xxx.5
                                                  [interface] => wan
                                                  [monitor] => 210.xxx.xxx.5
                                                  [name] => wan
                                                  [descr] => Interface WAN Gateway
                                                  [attribute] => system
                                              )

                                      )
                                      pfSense shell: print_r(return_gateways_status());
                                      pfSense shell: exec
                                      Array
                                      (
                                          [127.0.0.2] => Array
                                              (
                                                  [monitor] => 127.0.0.2
                                                  [gateway] => 127.0.0.2
                                                  [interface] => wan
                                                  [name] => wan
                                                  [lastcheck] => #0 Thu Jan  1 09:00:00 1970
                                                  [delay] => 0.000ms
                                                  [loss] => 100.0%
                                                  [status] => "down"
                                              )

                                      [210.xxx.xxx.5] => Array
                                              (
                                                  [monitor] => 210.xxx.xxx.5
                                                  [gateway] => 210.xxx.xxx.5
                                                  [interface] => wan
                                                  [name] => wan
                                                  [lastcheck] => #51640 Thu Nov 27 05:18:06 2008
                                                  [delay] => 4.051ms
                                                  [loss] => 0.0%
                                                  [status] => None
                                              )

                                      )
                                      pfSense shell:

                                      cheers,

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

                                        My cpu seems to have stoped charting, is this related to this topic?

                                        1 Reply Last reply Reply Quote 0
                                        • N
                                          nocer
                                          last edited by

                                          @Accounts:

                                          My cpu seems to have stoped charting, is this related to this topic?

                                          yup, and "Quality" graph too  :'(

                                          1 Reply Last reply Reply Quote 0
                                          • D
                                            databeestje
                                            last edited by

                                            the quality graphs have been changed over to a new format because we use the apinger files.

                                            This means removing the /var/db/rrd/*-quality.rrd files. And then reboot.

                                            The processor graph should have been fixed. This was a off by one.

                                            The wan being show down is definitely a issue with pppoe and pptp interfaces. This will need some time on my part. Not having a pppoe or pptp setup makes it that more time consuming.

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