Here's a bit more information on it. I've got the slave server configured for multiple services, each of them using the "redistribute" option:
redistribute alert trap.alert mainmonitor On the master server, once I've reset it, none of those servers will ever go green/good in mon.cgi - they stay in blue/unchecked status. If I force a failure on one of those services, the master server will show that service going red. Once I re-enable the service, it will then show green. But the other services for that slave server will never change from "unchecked" state on the master server's mon.cgi. Also, if I then re-set the mon process on the master server, all items will go back to blue and will not change again unless I force a failure. Also, I'm logging all output to a file on both the master and slave server via these commands: logdir = /var/log/mon historicfile = /var/log/mon/history In the slave server, the "history" file shows this for an outage event: alert Store13-2 DRBD_Status 1152819579 /opt/mon/alert.d/trap.alert (mainmonitor) DRBD_Not_Running upalert Store13-2 DRBD_Status 1152819594 /opt/mon/alert.d/trap.alert (mainmonitor) DRBD_Not_Running On the master server, it will only log this for that same event: trapalert Store13-2 DRBD_Status 1152819578 /opt/mon/alert.d/mail.alert ([EMAIL PROTECTED]) DRBD_Not_Running Thanks, Tim -----Original Message----- From: David Nolan [mailto:[EMAIL PROTECTED] Sent: Thursday, July 13, 2006 2:32 PM To: Tim Carr; mon@linux.kernel.org Subject: RE: Problem getting traps to work correctly --On Thursday, July 13, 2006 14:20:38 -0500 Tim Carr <[EMAIL PROTECTED]> wrote: > Gotcha. I threw that in, and it seems to work correctly, except I can't > tell if it is or not. I'm watching the log file, and it shows alerts > being sent on an up/down event, but I'm not seeing alerts every 15s > showing up when things are working correctly. Is that expected > behavior? > > Thanks, > Tim > I refer to the server that sends the traps as a slave server, and the server collecting the traps as the master server. Your master server should receive a trap on every status update on the slave server, i.e. a trap every 15s in your example. The master should only alert based on its alert behavior. This makes receving updates via traps almost functionally equivelant to other monitor tests that you run on your master server. If thats not the behavior you're seeing please let me know. -David _______________________________________________ mon mailing list mon@linux.kernel.org http://linux.kernel.org/mailman/listinfo/mon
