Opened 2 years ago
Last modified 14 months ago
#1044 new defect
unknown_limit not working
| Reported by: | Marki | Owned by: | nobody |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | master | Version: | 1.4.5 |
| Severity: | normal | Keywords: | |
| Cc: |
Description
Using munin 1.4.5-3~bpo50+1 on debian lenny, with rrd files from older munin (2-4 years) - don't know if that matters. After upgrade I receive several times a day report about UNKNOWNs. I have set unknown_limit to 3 and according to debug it is active. But my problem is that the part of LimitsOld?.pm responsible for this is never called. I have added some more debug code to there (around line 349), and it seems that $onfield->{"state"} is never defined... Do you have any idea why?
# First we'll need to check whether the user wants to ignore
# a few UNKNOWN values before actually changing the state to
# UNKNOWN.
if ($unknown_limit > 1) {
DEBUG "[DEBUG] Marki start of unknown; onfield/state= ".$onfield->{"state"};
if (defined $onfield and defined $onfield->{"state"}) {
if ($onfield->{"state"} ne "unknown") {
if (defined $onfield->{"num_unknowns"}) {
Change History (2)
comment:1 Changed 14 months ago by german
comment:2 Changed 14 months ago by german
The reason why it is not working is as follows:
It seems that on certain ocasions (i've noticed it with Fork yes ) munin-update will not retrive any information about a pluggin, the plugin gets deleted and munin-limits does not save any information about it in the limits file, that is the reason why $onfield->{"state"} is never defined as Marki said. Is there a reason why munin-update might be deleting the plugins?

Hi. I just wanted to say that I have the exact same issue. I find it difficult to debug....