Cacti

hi everyone, i'm just sharing this solution for anyone who might be stuck with an old version like mine for whatever reason and running into this problem. PROBLEM: after upgrading to firefox 3.5 from firefox 3.0.10, the zoom box would overlay a blue box that was obscuring the graph such that you cou...

hi folks, here's the more detailed analysis. CORE PROBLEM: in /usr/share/cacti/site/lib/rrd.php, we have the function rrdtool_function_graph. the faked $cf_id which is hardwired to "1" on line 822 causes the "data store cache check" to fail for any data sources that do not use &q...

hi folks, ok, i found the problem and patched it in my version to work. against debian sarge "0.8.6c-7sarge3", this patch works for ALL_DATA_SOURCES_NODUPS. *** /usr/share/cacti/site/lib/rrd.php-orig Sat Apr 8 08:21:03 2006 --- /usr/share/cacti/site/lib/rrd.php Mon Jan 22 10:34:23 2007 ***...

update: after having set the maximum to 1.1, i now see values larger than 1.00000 <!-- 2007-01-11 13:00:00 PST / 1168549200 --> <row><v> 1.0000000000e+00 </v></row> <!-- 2007-01-11 13:05:00 PST / 1168549500 --> <row><v> 9.9337763012e-01 </v></row> <!-- 2007-01-11 13:10:00 PST / 1168549800 --> <row><...

gandalf wrote:

jlg wrote: 2. note to #1 above: i can use "rrdtool tune <file.rrd> --maximum <ds>:1.1" to set the value to "1.1". so the limitation is in cacti.

jlg

Please create a bug report at http://bugs.cacti.net for that issue
Reinhard

will do...

jlg

more updates: 1. cacti complains if i try to set the data source "maximum value" to any number with a decimal point. at least...in the version that i'm running which is debian sarge's version which i understand is a probably 1 or 2 years old. so i had to set it to "2". btw, it wo...

for the benefit of others, i will answer my own question here. ***YES*** you should allow for some fudge factor due to interpolation. in my case, there is no way to get more than 1.000000 seconds out of a time period of 1.000000 seconds. so i had set my data source maximum to "1". and most...

hi folks, i have a snmp stat that reports "seconds of use" as a counter. this stat internally wraps at 43,000 seconds. when it wraps, the graph has a huge spike since this is nowhere near the 32 & 64 bit counter wrap limits that rrdtool can automatically handle. so researching the prob...

for the benefit of those reading this thread, note that making the change does not change the names of data sources or graphs that have already been created. you must drop and recreate graphs to pick up the new setting. jlg I do not agree. You may select those Graphs you need to update from Graph M...

RRDTool does not care for COUNTER32/64. But the mysql update may perhaps fail due to size limitations. Please check this. To do so, capture the mysql insert statement fpr poller_output and run this manually to check for errors Reinhard hi Reinhard, do you have a link that describes how to capture t...

Change Settings -> Visual -> Maximum Field Length to your needs Reinhard thanks Reinhard...that did the trick. for the benefit of those reading this thread, note that making the change does not change the names of data sources or graphs that have already been created. you must drop and recreate gra...

hi folks, i have a "Suggested Values" for my Data Template name which looks like this: |host_description| - DeviceIO Bytes - |query_diskIODevice| but the "query_diskIODevice" gets cutoff. for example, "ide/host2/bus1/target0/lun0/disc" gets cutoff to "myhost - Devi...

If I'm not mistake the link that you provide above is about resizing existing RRAs of existing RRDs. What I would like to know is about how to create RRA to support 5 minute average for daily, weekly, monthly and yearly. Any help would be great. hi sizulku, this example might help you...here is wha...

further analysis: i can see from the dump, that i the rrd file is being updated. this is a snippet from a dump: <!-- 2006-12-27 23:25:00 PST / 1167290700 --> <row><v> 0.0000000000e+00 </v><v> 0.0000000000e+00 </v></row> <!-- 2006-12-27 23:30:00 PST / 1167291000 --> <row><v> 1.7009587514e+01 </v><v> ...

You may need to tweak the data sources MAXIMUM values - in the Data Template - in all existing rrd files using "rrdtool tune --maximum" Reinhard hi reinhard, i confirmed that the MAXIMUM values should not be a problem. in the Data Template, "Maximum Value" == 0. and from the rrd...