[Mon-devel] mon 1-1-pre - two simultaneous alerts
Brought to you by:
trockij
From: Ed R. <er...@pa...> - 2005-04-28 16:29:02
|
Check out this excerpt from the mon log on my test machine, running the currently tagged Mon 1.1-pre on NetBSD 2.0 (with my fix for dep_ok() as noted previously on this list): Apr 28 11:57:55 testhost mon[8003]: failure for staff-important-servers fancy_service 1114703875 bighost littlehost loghost Apr 28 11:57:55 testhost mon[8003]: calling alert hey.alert for staff-important-servers/fancy_service (/usr/local/mon/alert.d/hey.alert,eravin) bighost littlehost loghost Apr 28 11:57:55 testhost mon[8003]: calling alert mymail.alert for staff-important-servers/fancy_service (/usr/local/mon/alert.d/mymail.alert,er...@pa...) bighost littlehost loghost Apr 28 11:57:55 testhost mon[8003]: calling alert hey.alert for staff-important-servers/fancy_service (/usr/local/mon/alert.d/hey.alert,eravin) bighost littlehost loghost Note how the hey.alert gets called twice. Here's the mon.m4 definition of the periods in use for this service: period HEYDAY: wd {Sun-Sat} hr {6am-11am} alert hey.alert eravin upalert hey.alert eravin alertafter 2 numalerts 1 period HEYNIGHT: wd {Sun-Sat} hr {11am-6am} alert hey.alert eravin upalert hey.alert eravin alertafter 2 numalerts 1 period MAIL: wd {Sun-Sat} alert mymail.alert er...@pa... upalert mymail.alert er...@pa... alertafter 2 numalerts 1 I might expect the hey.alert to get called twice if this alarm was sent at exactly 11 AM. But note the time in the monlog messages above, it was well after 11 AM. Furthermore, I've tested this same config several times, and once again just now. Only the time above did I see two alerts generated instead of one. So it looks like there's a race condition of some kind. Note that the duplicated alerts, along with a non-duplicated alert, were sent at the same second - I suspect that is significant. Any ideas? |