Using depend ...
I added depend lines to some of my services in my mon.cf, and
also dep_behavior = hm
I am using mon-1.2.0 where I added
use strict;
use warnings;
for debugging purpose.
I get
Use of uninitialized value in concatenation (.) or string at
/symlnks/common/dsnmon/2.0/mond line 5324
This happens at
} elsif ($watch{$group}-{$service}{_last_failure_time} = (time -
$watch{$group}-{$service}{dep_memory})) {
, it seems that $watch{$group}-{$service}{_last_failure_time} is
undefined.
The unix command grep _last_failure_time mon
$depval = $SUCCESS{$sref-{_op_status}}
($sref-{_last_failure_time} (time - $sref-{dep_memory}));
($sref-{_last_failure_time} (time -
$sref-{dep_memory}));
} elsif ($watch{$group}-{$service}{_last_failure_time} =
(time - $watch{$group}-{$service}{dep_memory})) {
shows that$sref-{_last_failure_time} is used but never set .
___
mon mailing list
mon@linux.kernel.org
http://linux.kernel.org/mailman/listinfo/mon
avoid duplicated alerts in a multi-host/mon context
Hello, I am using mon to monitor several services on multiple hosts in a network. Each host runs a mon daemon with a mon.cf configured according to the services to watch; this depends of the kind of apps. installed on this host. An application may need access to (a service on) an other host, so there is a watch checking for this remote service. When such a server host goes down (or crashes, or ...) , than there can (will) be several alerts raised, one on each client host. This will, for example, result in duplicated and redondant email messages. How can such a behavior avoided ?. I am thinking about forwarding all alerts to a master-mon where some filtering would happend before emitting an alert. This master-mon must be dynamically elected in order to avoid a single-point of failure, handle a failure resulting in a network split, a mail-server failure, a.s.o. . Are there features the current mon (1.2 ?) provides that can be hepful to implement such a thing ?, maybe there are better ways to achieve what I need ? Thank's for any hint. ___ mon mailing list mon@linux.kernel.org http://linux.kernel.org/mailman/listinfo/mon
latest mon source ?
I am using mon-1.1.0pre1 ($Id: mon,v 1.10 2004/11/15 14:45:16 vitroth Exp $) and would like to know what is the currently stable release and also the hopefully still under developpement release. Can it be considered safe to upgrade from release 1.10 to release 1.22 from CVS ? ___ mon mailing list mon@linux.kernel.org http://linux.kernel.org/mailman/listinfo/mon
