Rrd graphs

pharlock

does the sticky mean the quality graph is fixed?
i get graphs images (not place holders) but with no data since post hackthon builds
and i do get placeholders on the traffic and packet graphs.

nocer

Hi

nope, well, actually it was yes for one time at way back in the beginning of Jan. Since then, only CPU and LAN traffic, Quality are works. It is now only CPU since post hackathon builds. This, "RRDs are gone!" situations has been repeatedly happening quite so often so just prepared to be patient and wait for developers' head-up and fix. :-[

cheers,

tohil

my box don't show any quality graphs, and traffic shaper graphs are broken after configure the shaper with the wizard. just the message "error generating rrd graphs, please check the system logs" in a image with blurry graph is showing.

an other bug is, that wireless will be shown, when i am browsing between the tabs of rrd graphs. but when you klick on settings the wireless tab disapear.

2.0-ALPHA-ALPHA
built on Sun Mar 22 06:10:09 EDT 2009
FreeBSD 7.1-RELEASE-p3

databeestje

The shaper graphs in 2.0 have never been redone for the new shaper, so that sounds about right.

Afaik all the rrd graphs should all work. When I tested during the hackathon they all looked fine to me.

@tohil, I'll look into the wireless tab popping in and out, do you actually have a wireless connection?

eri--

I fixed the wireless tab issue some days ago so do not bother checking its ok now.

For the graphs well there some more work is needed but they should work ok after a wizard run.

Angotull

Negatory - tried the wizard and still have the same issue.

nocer

Hello,

Thanks for head-up again. "CPU" shows graphs correctly, "Quality" graphs back again but others are still not, giving some nasty errors like below; (it's too long and somehow truncated…)


Apr 3 07:43:56 	
php: /status_rrd_graph_img.php: Failed to create graph with error code 1, the error is: ERROR: Could
not parse color in '9'/usr/bin/nice -n20 /usr/local/bin/rrdtool graph /tmp/wan-packets.rrd-4y.png 
--start -126489600 -e -86400 --vertical-label "packets/sec" --color SHADEA#eeeeee --color
SHADEB#eeeeee --title "`hostname` - WAN :: Packets - 4 years - 1 day average" --height 200 
--width 620 -x "MONTH:1:YEAR:1:MONTH:3:0:%b" 
DEF:"wan-in_pps_pass=/var/db/rrd/wan-packets.rrd:inpass:AVERAGE" 
DEF:"wan-out_pps_pass=/var/db/rrd/wan-packets.rrd:outpass:AVERAGE" 
DEF:"wan-in_pps_block=/var/db/rrd/wan-packets.rrd:inblock:AVERAGE" 
DEF:"wan-out_pps_block=/var/db/rrd/wan-packets.rrd:outblock:AVERAGE" 
CDEF:"wan-in_pps=wan-in_pps_pass,wan-in_pps_block,+" 
CDEF:"wan-out_pps=wan-out_pps_pass,wan-out_pps_block,+" 
CDEF:"wan-out_pps_pass_neg=wan-out_pps_pass,-1,*" 
CDEF:"wan-out_pps_block_neg=wan-out_pps_block,-1,*" 
CDEF:"wan-pps_in_pass=wan-in_pps_pass,0,12500000,LIMIT,UN,0,wan-in_pps_pass,IF,86400,*" 
CDEF:"wan-pp

My WAN is a single PPPoE. Deleted /var/db/rrd/* or anything having *.rrd entirely and started from scratch several times but didn't help.

cheers,

2.0-ALPHA-ALPHA
built on Thu Apr 2 13:35:59 EDT 2009
FreeBSD 7.1-RELEASE-p4

databeestje

That error helps me a lot, now I know where to look. Which theme are you using?

Thanks!

nocer

Hi,

Currently "corporate", was "nervecenter". Observed the same error messages either. Now the pfbox won't allow me to change theme anymore by saying:

The following input errors were detected:

* You can not assign a gateway to DNS '' server which is on a directly connected network.
* You can not assign a gateway to DNS '' server which is on a directly connected network.

Which looks like that the box doesn't like dns server addrs which I manually entered for altering the one those provided by my ISP…I just wanted to change my themes. weired.

cheers,

pharlock

i didn't know running the wizard would fix anything. i tried it and my traffic and packet started working. still no quality graph or system logs. but i did an upgrade to april 3rd and everything works, but it might have just needed the reboot.
although i did get this error on startup and it is the 1st time i have seen it, but everything seems to be working anyway.

Starting syslog…Apr 5 00:15:40 syslogd: /var/log/relayd.log: No such file or directory