RRD graphing
-
Not sure here, but both the SVG traffic graph and the RRD quality graphs appear to be working normally.
Only issue being the empty items in the drop down. They work though, the labels are just empty.
-
RRD graphs do not work for me. the page has graphs headers but no graphs.
SVG traffic works well however interface traffic graph on the dashboard has a problem. The LAN graph is ok but the WAN shows incorrect info on my setup -
OOPS found the problem. RRD graph backend disabled by default on a new install. Going to RRD graph ->setting->enable RRD backend, now I have rrd graphs.
Any reason for having RRD graph backend disabled by default on a new fresh install? -
No particular reason. The tag is not part of our default config.xml
-
Thanks databeestje,
hmmmm…still no luck with the latest upgrade, yes RRD backend is running.
could you let me know which build do you use? Let me do fresh once again with your specific build.BTW the SVG problem was seen on the dashboard, not the traffic graph tab. because dashboard tries to
pull the value from pseudo "pppoe0" but traffic graph tab pulls "em0", which is real wan i/f in my case.
ie)
dashboard: http://192.168.33.1/graph.php?ifnum=pppoe0&ifname=wan&timeint=3
traffic tab: http://192.168.33.1/graph.php?ifnum=em0&ifname=wan&timeint=3
(192.168.33.1 is my setup for the LAN side of course)Not sure here, but both the SVG traffic graph and the RRD quality graphs appear to be working normally.
Only issue being the empty items in the drop down. They work though, the labels are just empty.
-
It's a good thing you said it's a pppoe connection. Now I know where to look. The em0 interface is the pppoe parent interface?
-
It's a good thing you said it's a pppoe connection. Now I know where to look. The em0 interface is the pppoe parent interface?
yup, em0 for WAN and em1 for LAN.
how about RRD Quality tab? Mine is still doesn't seem to work, it's all RED. It's been RED since the very begining of 1.3-AA and I believe someone has also posted the same sometimes ago.
-
how about RRD Quality tab? Mine is still doesn't seem to work, it's all RED. It's been RED since the very begining of 1.3-AA and I believe someone has also posted the same sometimes ago.
If you can't ping the default gateway of the interface, the graph will be red. There was previously a manual add to the config to change the monitor IP to something else, but I remember there being an option in the 1.3 gui to change this. I'm just too lazy to boot up a 1.3 test box and find where it is.
-
how about RRD Quality tab? Mine is still doesn't seem to work, it's all RED. It's been RED since the very begining of 1.3-AA and I believe someone has also posted the same sometimes ago.
If you can't ping the default gateway of the interface, the graph will be red. There was previously a manual add to the config to change the monitor IP to something else, but I remember there being an option in the 1.3 gui to change this. I'm just too lazy to boot up a 1.3 test box and find where it is.
I of course ping the default gateway, but in fact, because I am getting IP address via PPPoE so the addresses will change every(not exactly) boot then I just can't configure those gateway/monitor IP in the System:Gateways. Description for the monitor IP says "Enter a alternative address here to be used to monitor the link. This is used for the quality RRD graphs as well as the load balancer entries. Use this if the gateway does not respond to icmp requests." so I put some real address one of my co-lo box but RRD still red. This used to work without any extra config since 1.2, I will try 1.2.1 and see how it is done in 1.2.1.
Thanks for your info anyway.
-
If all is wel this should now be fixed for dynamic interfaces!
Please test!
-
Hello,
If all is wel this should now be fixed for dynamic interfaces!
Please test!
Thanks for follow up, however, I no have time playing with 1.2.1 since then so go with 1.3-AA and I'm actually stuck to configure the addresses which "dynamically assigned" by my ISP. Configuring System>Routing>Gateways requires addresses to be static. It can't be done if there's some sort of auto-discovery method, or even alias, or whatever the way $WAN can be used for gateway.
I of course statically configured addresses just for now and tested then I saw the config for the "apinger" successfully created in /var/etc and rrd graph is also created in /var/db/rrd/apinger-<monitor_ip_addr>.rrd and is updated correctly, but in fact, when I click Quality tab in RRD with my hope to see the apinger graph, nope, it just returns me wan-quality.rrd graph which I continuously seeing the ALL RED graph.
It could be my config for the Gateway wrong, I only set "WAN" for the interface, "TEST" for the name, address of my WAN interface for gateway, don't check default gateway, and one of my co-lo address for monitor_ip. That's all.
Could someone tell me correct way to configure this Gateway tab please?
cheers,
EDIT : I meant to say that how I can specify the "Gateway address" which
obtained by PPPoE and will be changed every boot.EDIT2: It looks fine in the Status:Gateways I see green and updated every
10 seconds or so, but somehow continuously getting "php: : Could not find
gateway for interface(wan)." in syslog.EDIT3: And…now the Quality RRD graph is all WHITE...means empty? or nothing?
Much better than all red but I just dunno :P</monitor_ip_addr> -
Hi,
Been playing with the 20080923-0645, and can't stop "php: : Could not find gateway for interface(wan)." messages in the syslog. It seems to be harmless but annoying and hogs syslog…I've deleted Gateway and apinger related but still getting these. Nothing happens either for Quality RRD Graph, it doesn't matter if Gateway/apinger configured or not, no graph, complete white(or blank). Grab some new build in the weekend and see if there's any progress...
cheers,
-
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.
-
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,
-
That's fixed too.
-
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,
-
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-PRERELEASEcheers,
-
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
-
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-PRERELEASEI will revert to previous build.
cheers, -
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.
