On Fri, Jan 27, 2006 at 02:54:40PM -0500, Brian Landers wrote:
> I have a tacacs+ monitoring script that successfully detects failures
> when run from the command-line but not from within mon. I'm at a loss
> to troubleshoot this one and am hoping the list can help. It seems to
> be printing the failure in the proper format and setting the exit code
> properly, but mon never sees the service as down.
You've reset Mon and the service shows up in the listing, right? Just
checking, sometimes folks skip that step.
Are you using mon.cgi? Drill down into the list for the tacacs+ test.
You should see a list of things like "last time monitor was run" and
other timestampes related to when the monitor was run and what the results
were. Is Mon even running the monitor in the first place?
> -bash-2.05b$ ./tacacs.monitor username password key server1 server2
> server1
> server1: Attempt timed out!
>
> -bash-2.05b$ echo $?
> 1
That looks right.
> watch acs_servers
> service tacacs
> description Make sure TACACS is working
> interval 15m
> monitor /usr/local/mon/tacacs.monitor username password key
> period wd {Sun-Sat}
> alert mail.alert [EMAIL PROTECTED]
> upalert mail.alert -S "Service is back up" [EMAIL PROTECTED]
> alertevery 15m
That looks right too.
BTW, can you share the tacacs+ monitoring script with us? I know at least
one other Mon user (cough cough) who is interested in it.
_______________________________________________
mon mailing list
mon@linux.kernel.org
http://linux.kernel.org/mailman/listinfo/mon
