David Nolan wrote:
--On Thursday, April 20, 2006 09:10:53 -0400 Brendan Mullen
<[EMAIL PROTECTED]> wrote:
The problem was traced to a locally modified version of the qpage alert.
If I had used the qpage.alert that shipped with the version of Mon I was
using, I would have been fine.
The locally modified qpage.alert worked on an older version of Mon, but
not 1.0pre5 The page would be sent but never show up in the alert
history, and then would be sent again. and again...
Interesting. Can you explain the cause of the failure? Was qpage.alert
exiting with an error code that made Mon think it need to re-try the alert?
The cause of the failure was the ! infront of the system command calling
qpage below. The mon daemon this qpage.alert worked on was 1.27 from
Sat Sep 8 2001. with a moncmd version output of 9745. I think this is
the .99.2 stable version.
Here is the section from our qpage.alert which may have been modified
from the shipped version.
else
if (!system ("/usr/local/bin/qpage -p $pagedest " .
"'$ALERT $opt_g/$opt_s: $summary ($wday $mon $day $tm)'" .
"2>/dev/null"))
{
die "could not open pipe to qpage: $?\n";
}
}
}
The qpage alert in the distributed version of mon I was using does not
have this ! infront of the system command. Otherwise the qpage.alerts
are identical (except for the path being explicit to our local environment).
The error code was (sorry this may not be exact):
Child alert failed http:WATCHNAME error code 255.
-Brendan
_______________________________________________
mon mailing list
mon@linux.kernel.org
http://linux.kernel.org/mailman/listinfo/mon
