On 1/27/06, Ed Ravin <[EMAIL PROTECTED]> wrote:
> You've reset Mon and the service shows up in the listing, right? Just
> checking, sometimes folks skip that step.
Yup, shows up and shows green for all services in the group.
> 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?
Now this is curious. I restarted mon, then checked the "last run
time" as you suggested, and it looks like mon is in fact NOT running
the monitor. So the $8mil question becomes: why? The script is
executable, is in a readable directory, etc. etc.
I also ran mon without -f and with -f and it's not showing up in the
debug output either.
Here's the full group entry
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
service ping
description Make sure TACACS is working
interval 15m
monitor fping.monitor
period wd {Sun-Sat}
alert mail.alert [EMAIL PROTECTED]
upalert mail.alert -S "Service is back up" [EMAIL PROTECTED]
alertevery 15m
What's interesting is, the ping service is working just fine, but the
tacacs service isn't running at all.
> 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.
Sure, it's here: http://www.packetslave.com/code/tacacs.monitor.txt
_______________________________________________
mon mailing list
mon@linux.kernel.org
http://linux.kernel.org/mailman/listinfo/mon
