<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.2627" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV>Guy,</DIV>
<DIV> </DIV>
<DIV>> Just a thought: Have you set up the nagios user on the remote host?
This <BR>> is necessary, as this user is specified in your /etc/xinetd.d/nrpe
file...<BR></DIV>
<DIV>I also create a nagios user in remote host</DIV>
<DIV><BR>> If you have already set up the nagios user on the remote host,
have you <BR>> tried executing the check_load plugin on the remote host as
the nagios user? <BR></DIV>
<DIV>I tried to login as "nagios" and use the check_load plugin as below. It
works </DIV>
<DIV> </DIV>
<DIV>[nagios@Testing libexec]$ ./check_load -w 5 -c 6<BR>OK - load average:
0.00, 0.00, 0.00|load1=0.000000;5.000000;6.000000;0.000000
load5=0.000000;5.000000;6.000000;0.000000
load15=0.000000;5.000000;6.000000;0.000000</DIV>
<DIV> </DIV>
<DIV>How to check all the steps below? I get this from nagios FAQ</DIV>
<DIV> </DIV>
<DIV><!--StartFragment -->
<LI><B>Different versions</B>. Make sure you are using the same version of the
check_nrpe plugin and the NRPE daemon. Newer versions of NRPE are usually not
backward compatible with older versions. </LI>
<LI><B>SSL is disabled</B>. Make sure both the NRPE daemon and the check_nrpe
plugin were compiled with SSL support and that neither are being run without SSL
support (using command line switches). </LI>
<LI><B>Incorrect file permissions</B>. Make sure the NRPE config file (nrpe.cfg)
is readable by the user (i.e. nagios) that executes the NRPE binary from
inetd/xinetd. </LI>
<LI><B>Pseudo-random device files are not readable</B>. Greg Haygood noted the
following... "After wringing my hair out and digging around with truss, I
figured out the problem on my Solaris 8 boxen. The files /devices/pseudo/random*
(linked through /dev/*random, and provided by Sun patch 112438) were not
readable by the nagios user I use to launch NRPE. Making the character devices
world-readable solved it." </LI>
<LI><B>Unallowed address</B>. If you're running the NRPE daemon under xinetd,
make sure that you have a line in the xinetd config file that say "only_from =
xxx.xxx.xxx.xxx", where xxx.xxx.xxx.xxx is the IP address that you're connected
to the NRPE daemon from.</LI></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial
size=2>------------------------------------------------------------------------------------------------------------</FONT></DIV>
<DIV><STRONG>Different versions</STRONG></DIV>
<DIV>- I should have the same version on both remote host and nagios
server</DIV>
<DIV>- I am using nrpe-2.0</DIV>
<DIV><STRONG></STRONG> </DIV>
<DIV><STRONG>SSL is disabled</STRONG></DIV>
<DIV><STRONG>-</STRONG> How to check this?</DIV>
<DIV><STRONG></STRONG> </DIV>
<DIV><STRONG>Incorrect filer permission</STRONG></DIV>
<DIV>- I think should be correct</DIV>
<DIV>-rw-rw-rw- 1 nagios
nagios 5076 May 18 03:07 nrpe.cfg</DIV>
<DIV><STRONG></STRONG> </DIV>
<DIV><STRONG>Pseudo-random device files are not readable</STRONG>.</DIV>
<DIV>- How to check this?</DIV>
<DIV><STRONG></STRONG> </DIV>
<DIV><STRONG>Unallowed address</STRONG></DIV>
<DIV>- I think is correct</DIV>
<DIV><STRONG></STRONG> </DIV>
<DIV> # default:
on<BR> # description:
NRPE<BR> service
nrpe<BR>
{<BR>
flags =
REUSE<BR>
socket_type =
stream<BR>
wait =
no<BR>
user =
nagios<BR>
server =
/usr/local/nagios/nrpe<BR>
server_args = -c /usr/local/nagios/nrpe.cfg
--inetd<BR>
log_on_failure +=
USERID<BR>
disable =
no<BR>
only_from =
10.1.8.77<BR> }<BR></DIV>
<DIV><STRONG></STRONG> </DIV>
<DIV><STRONG>--------------------------------------------------------</STRONG></DIV>
<DIV>Any part i make mistake?</DIV>
<DIV><STRONG></STRONG> </DIV>
<DIV>Guy, Thanks for the reply and help....</DIV>
<DIV> I still need help :)<BR></DIV>
<DIV>Regards,</DIV>
<DIV>Eugene</DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV></BODY></HTML>