Probem with nrpe and sudo on rhel5 servers

[Andrew Norris]

Have you tried commenting out the following line in sudoers?

"Defaults    requiretty"

I got hit by that one moving ssh checks from centos4 to centos5.

Nicole Hähnel wrote:
> Hi,
> 
> I wrote a plugin to check running ipsec tunnels on our gateways.
> The plugin needs to have access to /proc/net/ipsec_eroute, so I have to
> run nrpe command with sudo.
> 
> sudoers (for testing):
> nagios          ALL=(ALL)       NOPASSWD: ALL
> 
> nrpe.conf:
> command[check_tunnel]=sudo /usr/lib/nagios/plugins/check_tunnel
> --tunnels $ARG1$
> 
> I tested the plugin on the gateway, it works fine,
> but with nagios I get "NRPE: Unable to read output".
> Running the plugin without sudo, nagios has an output,
> but 0 running tunnels.
> 
> Looks like a problem with sudo command on rhel5 servers.
> Any ideas?
> 
> 
> Thanks!
> 
> Nicole
> 
> 
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> 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
> 

-- 
Andrew Norris
Systems Administrator
Locus Telecommunications
andrewn at locus.net
(201)-947-2807 ext. 1135

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
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