NRPE does nothing with configured with --disable-ssl

[Marc Powell]

> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> admin at lists.sourceforge.net] On Behalf Of Hosey, Chester
> Sent: Wednesday, August 03, 2005 1:35 PM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] NRPE does nothing with configured with
--disable-
> ssl
> 
> Hello!
> 
> I'm trying to use NRPE on an aging AIX 4.3 machine. I'm having openssl
> issues, and tried to configure NRPE with --disable-ssl while sorting
out
> the openssl problems.
> 
> Unfortunately it seems that under Linux as well as AIX, when
configured
> with --disable-ssl NRPE exists silently both when given -d and -i on
the
> command line.
> 
> Specifically, I tried the following commands:
> 
> ./configure --disable-ssl
> make
> src/nrpe -c nrpe.cfg -i
> 
> I am returned immediately to the command prompt.

This is expected behavior. In your default syslog message file you'll
probably find an error such as --

Aug  3 14:17:44 gemini nrpe[13238]: Could not read request from client,
bailing out...

That's because using -i, nrpe is told that it has been called directly
by [x]inetd and is expecting incoming data packets from the client, not
input from STDIN.

nrpe -d should launch it in daemon mode in the background and return you
to the command prompt. If it doesn't, again, check your messages file.

--
Marc


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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