Henrik,
On 137 and 139 we have the catch alls for sysalert and support (support
is our red address and sysalert is where we send both to).
Mike
-----Original Message-----
From: Henrik Stoerner [mailto:user-ce4a2c883f75@xymon.invalid]
Sent: 19 June 2006 10:33
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] TIME alert problems (still)
On Mon, Jun 19, 2006 at 09:50:37AM +0100, Mike Rowell wrote:
Sun Jun 18 21:19:37 2006 xxxxx.aq (10.6.2.2) support [139] 1150661977
0
Sun Jun 18 21:24:21 2006 xxxxx.aq (10.7.2.2) sysalert [137] 1150662261
0
Sun Jun 18 21:24:21 2006 xxxxx.aq (10.7.2.2) support [139] 1150662261
0
Sun Jun 18 21:25:21 2006 xxxxx.aq (10.8.2.2) sysalert [137] 1150662321
0
Sun Jun 18 21:25:21 2006 xxxxx.aq (10.8.2.2) support [139] 1150662321
0
Sun Jun 18 22:20:01 2006 xxxxx.aq (10.6.2.2) sysalert [137] 1150665601
0
Sun Jun 18 22:20:01 2006 xxxxx.aq (10.6.2.2) support [139] 1150665601
0
HOST=*
MAIL=sysalert SERVICE=aq FORMAT=PLAIN REPEAT=1h COLOR=yellow
MAIL=support SERVICE=aq COLOR=RED FORMAT=SMS DURATION>5 REPEAT=1h
TIME=W:0900:1700 STOP
(these are lines 135 and 136 so it looks like it's ignoring them
totally, although in bb-hostsvc.sh it shows them laid out properly
with
the correct blackout times listed against the services).
What's on lines 137 and 139 of the hobbit-alerts.cfg file ? Those are
the lines that trigger these alerts, as evidenced by the "[13x]"
in the log entries.
Regards,
Henrik
This email has been scanned for all viruses by the MessageLabs service.
This email has been scanned for all viruses by the MessageLabs service.