turn off epn

[Marc Powell]

> -----Original Message-----
> From: nagios-users-bounces at lists.sourceforge.net [mailto:nagios-users-
> bounces at lists.sourceforge.net] On Behalf Of zack kenton
> Sent: Wednesday, September 26, 2007 4:05 PM
> To: nagios-users at lists.sourceforge.net
> Subject: Re: [Nagios-users] turn off epn
> 
> Hi Chris
> 
> So I've done this in two different ways. The first being simply
putting
> /usr/bin/perl before the command, like /usr/bin/perl
> $USER&/contrib/check_oracle_instance.pl.....and i also tried your
method,
> which is basically the same...now I'm getting "no output" instead of
the
> epn error I was previously getting...but this occurs with 2 different
perl
> scripts so I dont think its unique to the oracle script

This is the correct way to disable use of ePn without recompiling. The
implication is that your scripts really are bombing or otherwise showing
an error. When you tested, did you do so as the nagios user? Environment
or permissions problems are commonly the culprit.

You might want to redirect STDOUT and STDERR to a file to see what it's
doing. You should be able to do so by adding '> /tmp/output 2>&1' to the
end of the command definition then checking the contents of /tmp/output
after nagios has run the plugin.

--
Marc

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
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