Scott Moseman | 6 Jan 2006 18:52
Picon

Alerts cause Smokeping to stop working

Using an older version of Smokeping...

# ../bin/smokeping -v
$Id: Smokeping.pm,v 1.5 2004/10/21 21:10:51 oetiker Exp $

I created this rule...

+6pct3hrs
type = loss
pattern = >6%,*36*,>6%
comment = 6+% loss for 3 hours

For all devices, so I apply at the top...

menu = Top
alerts = 6pct3hrs

Everything is fine and dandy until 3 hours comes around.  At that
point I get my alarms for the various devices that have been down
(good) -- but Smokeping also stops collecting data for all of the
other devices now!  All graphs come to a halt.  The Smokeping daemon
is still running but it's not gathering any data.  I can stop/start
the daemon and this situation will happen again.

Am I doing something wrong?  Is this a bug fixed in a later version of
Smokeping?  I did a scan through the CHANGES for the newer versions
and could not find anything that seemed like it was a bug fix for a
related problem.  Maybe I'm missing something?

Thanks,
(Continue reading)

Niko Tyni | 13 Jan 2006 20:07
Picon
Picon

Re: Alerts cause Smokeping to stop working

On Fri, Jan 06, 2006 at 11:52:41AM -0600, Scott Moseman wrote:
> Using an older version of Smokeping...
> 
> # ../bin/smokeping -v
> $Id: Smokeping.pm,v 1.5 2004/10/21 21:10:51 oetiker Exp $

> Everything is fine and dandy until 3 hours comes around.  At that
> point I get my alarms for the various devices that have been down
> (good) -- but Smokeping also stops collecting data for all of the
> other devices now!  All graphs come to a halt.  The Smokeping daemon
> is still running but it's not gathering any data.  I can stop/start
> the daemon and this situation will happen again.
> 
> Am I doing something wrong?  Is this a bug fixed in a later version of
> Smokeping?  I did a scan through the CHANGES for the newer versions
> and could not find anything that seemed like it was a bug fix for a
> related problem.  Maybe I'm missing something?

Hi,

the 1.x series is quite deprecated by now; please try the latest 2.x
version (currently 2.0.5). I don't remember seeing this particular
bug, but there have been several changes to the alert code and
last I checked, the alerts were working for me.

If the problem persists, please include the output of 'smokeping -debug'
along with your configuration file.

If you want to stay with the old version, you'll have to debug this
yourself. A good start is still 'smokeping -debug' and possibly running
(Continue reading)


Gmane