Cheshire Cat Computing

Hi

I upgraded a monitoring box to AMD Opteron based hardware and Gentoo. My graphs now seem to show about 10% of the correct value. I am just starting to look into it now but thought worth checking if there have been other reports of issues on x86_64.

I'll post any results.

Linux 2.6.19-gentoo-r5 #6 SMP Sat Mar 3 15:03:09 EST 2007 x86_64 Dual-Core AMD Opteron(tm) Processor 2218 AuthenticAMD GNU/Linux

mrtg-2.15.0 - Multi Router Traffic Grapher

RRDtool 1.2.15 Copyright 1997-2006 by Tobias Oetiker


Roger Longden

This may be a bits/bytes problem.

Take a look at the .cfg file (you dont give me any info so I have to guess) and it may be that routers2 is incorrectly guessing that the thing being monitored is a network interface, and therefore defaulting to bits rather than bytes, or vice-versa.

You can use

routers.cgi*Options[xxxx]: bits

or

routers.cgi*Options[xxxx]: bytes

to force things one way or the other. Also, you can use

routers.cgi*Mode[xxxx]: generic

to tell it not to make any assumptions at all.

If you've still a problem, let me know
1) the .cfg file contents
2) if the graph displayed values match the contents of the RRD (do an rrdtool dump on the .rrd file)
3) Is the problem in the collection (previous values still displaying correctly) or in the display (historical values now graph as less than previously)?
4) The version of Perl you are using (this might affect some maths routines)

Steve

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

Hi Steve

Thanks for your time, it helped me find the cause of the unexpected behavior very quickly.

I had set "bytes = yes" in routers2.conf. The values on the graphs displayed correctly reflecting this setting, but the axis label still said "traffic in bps". I set back to "bytes = no" and the graphs make sense again. Perhaps I have misunderstood the intended effect of this setting.

Roger