--On Saturday, August 31, 2002 2:56 PM +0200 Philipp Steinkrüger
<[EMAIL PROTECTED]> wrote:
>
> mon gets the trap and the service is ok for 5 seconds, but when its in
> failure mode,
> its not sending alerts. mon.cgi shows this:
>
> trapgroup trap: trap timeout (FAILED, NOALERTS)
>
This is interesting, as it makes it clear that Mon doesn't think it has
executed the alert. (As opposed to it ran the alert, but the alert failed
to send mail.) This leads me to believe that either mail.alert doesn't
exist in the alert directory (as defined in the 'alertdir' directive in
mon.cfg) or mail.alert doesn't have the executable bit set.
>
> another interesting thing is that every trap is logged to syslog. refering
> to the manual this
> happens when group and service couldnt be assigned to a watch and no
> default watch
> is present. but as far as i can see i specified both service and hostgroup
> correctly.
>
Every trap is always logged to syslog, at the 'info' level. Traps which
don't match a group/service get logged at the 'error' level. You might
find it useful to set up syslog to log daemon.* to a special file, and see
if anything there indicates a problem.
-David
David Nolan <*> [EMAIL PROTECTED]
curses: May you be forced to grep the termcap of an unclean yacc while
a herd of rogue emacs fsck your troff and vgrind your pathalias!
