Gday again,
Have had another go at this and it seems to work when you add options:
unknaszero.
Around line 1700 in the mrtg script it mentions
$threshval{$dir} = 0 if not defined $threshval{$dir} and
$$rcfg{'options'}{'unknaszero'}{$router};
warn "WARNING: can't do threshold checking for target
$router($dir) -- No valid current data\n"
unless defined $threshval{$dir};
my $value = $threshval{$dir};
and I added unknaszero to the localhost.eth0 options, but has this fixed the
problem or just
made it ignore the threshold completely ?
Im just wondering now if anyone has rrdtool 1.2.11 and mrtg 2.12.2 and
thresholds actually working ?
After fixing my rrdtool perl issue and upgrading successfully,
I am starting to re-run my mrtg scripts and have found an
issue it seems with Thresholds.
WARNING: can't do threshold checking for target localhost.eth0(i) -- No
valid current data
WARNING: can't do threshold checking for target localhost.disk1(i) -- No
valid current data
WARNING: can't do threshold checking for target localhost.disk2(i) -- No
valid current data
WARNING: can't do threshold checking for target localhost.load1(i) -- No
valid current data
Looking at the data and the graphs produced there is actual values returned
no problem
with these scripts.
Just wondered if anyone had stumbled onto this and solved it.
The .cfg files ran perfectly under mrtg 2.12.2 and rrdtool 1.0.45.
Thanks again
Martin
--
Unsubscribe mailto:[EMAIL PROTECTED]
Archive http://lists.ee.ethz.ch/mrtg
FAQ http://faq.mrtg.org Homepage http://www.mrtg.org
WebAdmin http://lists.ee.ethz.ch/lsg2.cgi
