Help NRPE 1.8 won't work

[Phil Costelloe]

From: Hagen Deike [mailto:Hagen_Deike at icon-scm.com] 
> 
> I need a little help on nrpe 1.8
> I Installed nrpe on a Linux Box running Nagios and a HP/UX 
> Server with the nrpe daemon.
> 
> On the HP/UX Server the nrpe exec is installed in /usr/sbin. 
> Path is set correct. The config file is in 
> /usr/local/nagios/etc/nrpe.cfg nrpe is loaded in inetd.conf
> 
>  nrpe stream tcp nowait daemon /usr/sbin/nrpe -c
/usr/local/nagios/etc/nrpe.cfg --inetd
> 
[snip]
> But as soon as I try to use the check_nrpe plugin I get an error...
> 
>  me at mon:/usr/lib/nagios/plugins> ./check_nrpe -H 10.x.x.x -c 
> check_load
>  CHECK_NRPE: Received 0 bytes.  Are we allowed to connect to the host?
> 
> What's wrong with it???

Second time this week this problem has come up, and it's really a
problem with the documentation which only gives an inetd.conf example
for tcpwrapper-ed systems (course all systems should be :).

Here's the format for inetd.conf entries (taken from Solaris 8)

# Syntax for socket-based Internet services:
#  <service_name> <socket_type> <proto> <flags> <user> <server_pathname>
<args>

<server pathname> is /usr/sbin/nrpe (in this case) but <args> must also
include argument 0, i.e. the server program again. So the correct
inetd.conf entry is :

nrpe stream tcp nowait daemon /usr/sbin/nrpe /usr/sbin/nrpe -c
/usr/local/nagios/etc/nrpe.cfg --inetd

I'll submit a documentation patch as soon as I get the chance.

Phil


-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger 
for complex code. Debugging C/C++ programs can leave you feeling lost and 
disoriented. TotalView can help you find your way. Available on major UNIX 
and Linux platforms. Try it free. www.etnus.com
_______________________________________________
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