Hi list,
I'm experiencing some problems with ePN on one of my home-brew plugins
(check_rsync, I included the link to Nagiosexchange below) that is
somehow failing under ePN. I haven't had the time to investigate this
but it is not my concern.
What happens beside the ePN problem is that somehow the plugin prints a
normal output into Nagios status (it says "rsync [...] failed with error
3" which is an auth error - probably the credentials not being passed
correctly to the command)
Even more odd, at each run not only the "Status Data Age" get reset to
current time, but also the "Current State Duration". In other words the
plugin always shows critical but "Current State Duration" always equals
"Status Data Age".
This was very confusing and I only realized it was failing under ePN
when I looked at the Nagios logs. They shows plenty on lines like these
(I shortened them a bit... Notice the same timestamp for the same server
on the same service):
[1173757417] SERVICE ALERT: server;Rsync;UNKNOWN;HARD;3;**ePN
check_rsync: "untie attempted while 1 inner references still exist at
perl5/5.8.8/IPC/Open3.pm line 197,".
[1173757417] SERVICE ALERT: server;Rsync;CRITICAL;HARD;3;CRITICAL: Rsync
command rsync --port=873 rsync://1.2.3.4 failed with error 3
Looks like for some reason two results are coming back at each check. If
possible I'd suggest making sure only one result is written on the pipe
per check fork.
Thomas
The check_rsync page on NagiosExchange:
http://www.nagiosexchange.org/Misc.54.0 ... _pi1[ext]=
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]