>If you look at p1.pl, which is in the Nagios bin directory you can >enable ePn logging (EPN_LEAVE_MESSAGES or something similar for debug >level) and have epn log each command execution to a log file ... This >often will make the source of an epn error more obvious.
Ok, looks like there are some factors surrounding when the o0utput even gets dumped? Plugin was touched, now I am waiting... >The other thing to do is add > >Use warnings; Got that in the plugin as per the guidelines. >As any output to STDERR will cause ePN to halt execution. Works fine:/ >That said, 'not execute properly' errors are often permissions or path >errors, so when you test from the CLI make sure you run the script as >the same user your Nagios damon runs as. Actually, it is 'exit' not execute, it has perms granting execution for all. We'll see what happens after I come back to it. Thanks for the help! jlc ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Nagios-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
