I just compiled and installed RC1 on a Red Hat EL5.5 server this AM, and have come across a strange issue – don't know if it's my configuration or something with the new version
It seems like it isn't following the DURATION flag for alerts
I have some rules for a host, it matches on two lines:
./xymond_alert --test hostname.subdomain.domain.com disk
00003158 2011-01-24 13:51:05 send_alert hostname.subdomain.domain.com:disk state Paging
00003158 2011-01-24 13:51:05 Matching host:service:page 'hostname.subdomain.domain.com:disk:unified-tex' against rule line 128
00003158 2011-01-24 13:51:05 *** Match with 'HOST=% SERVICE=%disk|inode|procs|temperature|bbd|http|conn|ssh' ***
00003158 2011-01-24 13:51:05 Matching host:service:page 'hostname.subdomain.domain.com:disk:unified-tex' against rule line 134
00003158 2011-01-24 13:51:05 *** Match with 'HOST=% SERVICE=%disk|inode|procs|temperature' ***
here is the alerts.cfg relevent sections:
128 HOST=% SERVICE=%disk|inode|procs|temperature|bbd|http|conn|ssh
129 MAIL=user-ac2e53899896@xymon.invalid DURATION>20 REPEAT=60 COLOR=red RECOVERED
134 HOST=% SERVICE=%disk|inode|procs|temperature
135 MAIL=user-c96a031d3d93@xymon.invalid TIME=06:0000:2359 DURATION>720 REPEAT=120 COLOR=red RECOVERED
136 MAIL=user-c96a031d3d93@xymon.invalid TIME=12345:0000:0559 DURATION>720 REPEAT=120 COLOR=red RECOVERED
137 MAIL=user-c96a031d3d93@xymon.invalid TIME=12345:0600:1759 DURATION>60 REPEAT=120 COLOR=red RECOVERED
138 MAIL=user-c96a031d3d93@xymon.invalid TIME=12345:1800:2359 DURATION>720 REPEAT=120 COLOR=red RECOVERED
What i am expecting from these rules/matches is
email mailing-list if it's been red for > 20 minutes, and email on recovery
additionally
on Sat, Sunday, if it's been red for > 720 minutes, email my phone
on M-F, email my phone if it's been red for > 720 minutes & before 6am
after 7am, red > 60 minutes, after 6pm > 7200 minutes again
What is happening is
When a red even occurs, it immediately sends an email to user-ac2e53899896@xymon.invalid , and an email to user-c96a031d3d93@xymon.invalid
Does anyone know if this is my configuration that needs fixing , or something with 4.3.0?
-Sean
This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.