RRD Graphs
-
I found another bug, but it's definitely fixed now. :-)
Either apply this by hand, or wait for the next new snapshot:
https://rcs.pfsense.org/projects/pfsense/repos/mainline/commits/21934843352aa1dee730f59b06d35f1619c0ab3e -
I'll wait for the next update.
I'm just testing and providing feedback.
Thanks !!!
-
Sorry.Ā Been away.
Just updated to
2.0-BETA4
built on Sun Aug 8 11:22:28 EDT 2010
FreeBSD 8.1-RELEASEGraphs are looking good.
-
Still no good for me.
-
Anything else I can try. I have the snapshot from sunday etc.
-
Today's seem fineā¦2.0-BETA4
built on Tue Aug 10 02:57:56 EDT 2010 -
I did another full delete of the RRD graphs and left in for 15 mins. The graphs only captured 2 mins worth of data and then stopped.
-
Am I best off rolling back to 2.0 beta 1 when it worked?
-
No. It works for everyone else, there must be something specific about your setup.
And BETA1 is ancient by BETA standards. So many things are better now than they were back then.
-
I have e-mailed you my config to see if something is a miss.
-
Do the graphs work if you use the pfsense_ng theme instead of the_wall like you have set?
I didn't see anything that jumped out at me in that config as being wrong for rrds, but I know that some of the themes have their own RRD colors and such that might not be working properly.
-
I too have this issue.Ā applying the patch listed back in July though ā¦. does solve the issue for me.
however the Traffic Graphs do not function for me.
I have tested it with the brand new build .... -
OMGĀ -Ā you killed theĀ Status: Traffic Graph !!!
2.0-BETA4 (i386) built on Thu Aug 12 07:38:24 EDT 2010 FreeBSD 8.1-RELEASE
Also you can see this on theĀ pfSense Dashboard.
Not sure when this happened over the past couple/few days.
Regardsā¦Martin
-
the gettext import has caused quite a bit of fallout, RRD and SVG graphs currently broken.
-
Yesterday 08/11/2010 the snapshot update has really broken RRD Graphs here.
Today runing 2.0-BETA4 (i386) built on Thu Aug 12 05:28:01 EDT 2010 the RRD Graph is working
with defaults.
No RRD graphs for themesā¦ but it's working.
Still, you can change color graph editing status_rrd_graph_img.php
As always, just do it if you know what you're doing.
-
Right I have just got the lastest snapshot the Traffic graphs on the dashboard are not working as yet but the RRD graphs I have the quality working there was a 2 minutes worth on the system then stopped and nothing on the traffic.
I also changed to the suggested theme with no luck.
Sys log dump
Aug 13 09:30:37 kernel: timecounter TSC must not be in use when changing frequencies; change denied
Aug 13 09:30:37 last message repeated 7 times
Aug 13 09:30:33 php: /status_rrd_graph_img.php: rrdcolors.inc.php for theme pfsense_ng does not exist, using defaults!
Aug 13 09:30:33 kernel: timecounter TSC must not be in use when changing frequencies; change denied
Aug 13 09:30:32 last message repeated 3 times
Aug 13 09:30:31 php: /status_rrd_graph_img.php: rrdcolors.inc.php for theme pfsense_ng does not exist, using defaults!
Aug 13 09:30:30 kernel: timecounter TSC must not be in use when changing frequencies; change denied
Aug 13 09:30:30 php: /status_rrd_graph_img.php: rrdcolors.inc.php for theme pfsense_ng does not exist, using defaults!
Aug 13 09:30:30 kernel: timecounter TSC must not be in use when changing frequencies; change denied
Aug 13 09:30:30 kernel: timecounter TSC must not be in use when changing frequencies; change denied
Aug 13 09:30:30 php: /status_rrd_graph_img.php: rrdcolors.inc.php for theme pfsense_ng does not exist, using defaults! -
Is there any resolution for this in my case?
-
At the moment I think there are once again some issues with RRDs in general, so it may not be just you. I haven't tried a snap from today but late last week there were several reports that things weren't working right in the GUI. The graph data files were being updated but not drawn properly.
-
Do you know when this is scheduled to be fixed.
-
This appeared to be specific to people that used openvpn tunnels. This caused the updated process to hang.
This is now fixed.
