NRPE: Unable to read output (after upgrading sudo to 1.7.2p1-6.el5_5)

[Ben O'Hara]

I found the same problem with sudo after an update.

Seems the comment line in the sudoers file causes a synax with
#comment, you need a space, so # comment works ok.

Ben

On Wed, May 19, 2010 at 5:48 PM, Yungwei Chen <yungwei at resolvity.com> wrote:
> Hi,
>
>        I have been using a check_ldap_fd command on a nagios client without any problem. That command requires superuser permission.
>        After upgrading sudo to 1.7.2p1-6.el5_5, the command stops working.
>
>        Running the following command on my nagios server always shows the following:
>        [TEST:root at serv1 ~]# /usr/lib/nagios/plugins/check_nrpe -H 192.168.12.2 -c check_ldap_fd
>        NRPE: Unable to read output
>
>        This is the command defined in /etc/nagios/nrpe.cfg on the nagios client:
>        command[check_ldap_fd]=/usr/bin/sudo /usr/lib/nagios/plugins/check_ldap_fd -w 250 -c 500
>
>        I also made the following changes to /etc/sudoers on the nagios client in order to make the command work:
>        #Defaults    requiretty
>        nagios ds2 = NOPASSWD:/usr/lib/nagios/plugins/check_ldap_fd
>
>        Any ideas? Thanks.
>
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> 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
>



-- 
"Scientology ... is not a religion."

- L. Ron Hubbard (Creator of Scientology)

------------------------------------------------------------------------------

_______________________________________________
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