Turning on the cfid option in xymond_alert might be useful as well.
-jc
--cfid If this option is present, alert messages will include a line
with "cfid:N" where N is the linenumber in the alerts.cfg file that caused
this message to be sent. This can be useful to track down problems with
duplicate alerts.
On Wed, October 1, 2014 6:02 am, Novosielski, Ryan wrote:
Two places to look to troubleshoot are the notifications.log, to check to
see whether Xymon actually sent multiples or not, (could be your mail
server, theoretically) and the "info" test on the server in question to
see what the notifications settings parsed to. You can also look at the
config report for that kind of info.
--
____ *Note: UMDNJ is now Rutgers-Biomedical and Health Sciences*
|| \\UTGERS |---------------------*O*---------------------
||_// Biomedical | Ryan Novosielski - Senior Technologist
|| \\ and Health | user-46c89e614701@xymon.invalid - 973/972.0922 (2x0922)
|| \\ Sciences | OIRT/High Perf & Res Comp - MSB C630, Newark
`'
From: Xymon [xymon-bounces at xymon.com] On Behalf Of Andrey Chervonets
[user-e7fb5c02322c@xymon.invalid]
Sent: Wednesday, October 01, 2014 8:35 AM
To: xymon at xymon.com
Subject: [Xymon] Double, triple notifications
For some tests and hosts I receive several notification copies (identical)
- sometimes two, sometimes three.
I had reviewed the configuration, but can not detect where is the problem.
1) How can I debug which rule worked out for each copy?
2) Feature request - I suppose it should be quite easy to avoid redundant
notification copies before sending,
for example using
cat (rows-list of recepients) | sort | uniq
P.S. XyMon version 4.3.17 on CentOS (64-bit) if this makes sense.
Best regards,
Andrey Chervonets
SIA CoMinder
http://www.cominder.eu/