On Wed, 19 Apr 2006, Jon Meek wrote:
That blank line after monitor http.monitor is probably not a good thing.
yeah, that is the problem. a blank line signifies the end of a watch record.
___
mon mailing list
mon@linux.kernel.org
--On Thursday, April 20, 2006 09:10:53 -0400 Brendan Mullen
[EMAIL PROTECTED] wrote:
I was migrating our instance of Mon to a new machine running a newer
version.
The problem was traced to a locally modified version of the qpage alert.
If I had used the qpage.alert that shipped with the
On Thu, 20 Apr 2006, Brendan Mullen wrote:
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...
Hmm.
Check your logs. Mon syslogs when an alert exits
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
--On Wednesday, April 19, 2006 12:09:30 -0400 Brendan Mullen
[EMAIL PROTECTED] wrote:
Hello,
I'm using mon-1.0.0pre5, the mon-client-1.0.0pre5 and mon.cgi2.2
When an alert is triggered, it continues to page every minute like it is
paging on every watch interval.
The config looks
