Re: [hobbit] Hobbit 4.0.4 released - Alert Script Issue

[Peter Welter <peter.welter (at) gmail.com>]

Status update:

After adapting the hobbit-alert.cfg to a minimum, enabling the trace
facility, it becomes clear to me that after restarting Hobbit, the
downtime for a service is completely recalculated. It finds a match
for a service whch is down for an 1hour and 17 minutes and it says:

00003590 2005-08-17 09:46:33 Matching host:service:page
'burad12:raid:DNO/SAPEPROC' against rule line 196
00003590 2005-08-17 09:46:33 Failed '$UNIXDAG' (min. duration 0<360)
00003590 2005-08-17 09:46:33 Matching host:service:page
'burad12:raid:DNO/SAPEPROC' against rule line 197
00003590 2005-08-17 09:46:33 Failed '$UNIXTEST' (min. duration 0<1800)

Hmmm... I am restarting Hobbit now and then, fi. because 'hobbit.sh
rotate' does not work at my installation and the rotatelogs for linux
moves the notification.log to notification.log.1 which keeps being
used without restarting.

So, monitoring this logs seems to clarify things to me... Now let's
trim the point where a script is being called.To be continued...

2005/8/17, Peter Welter <peter.welter (at) gmail.com>:
> 2005/8/17, Henrik Stoerner <henrik (at) hswn.dk>:
> > On Wed, Aug 17, 2005 at 04:56:59AM +0200, Peter Welter wrote:
> > You might want to add "--trace=/tmp/alerttrace.log" to the hobbitd_alert
> > command in hobbitlaunch.cfg. That will give you a closer watch on how
> > each alert is handled by the alert module.
> Thanks, I will do so now.
> 
> > Do the missing alerts show up in the notifications.log file ?
> No, unfortunately.
> 
> I'll keep you posted.
>