URGENT REPOST: CHECK_NRPE: Received 0 bytes fromdaemon ErrorMessage

Steve Shipway s.shipway at auckland.ac.nz
Wed Dec 20 01:06:09 CET 2006


I would say that you need to use inetd, OR an init.d script, but not
both.  If you try to then you'll get errors when they try and start up.
 
Your 'unable to read output' error seems to indicate that you have a
timeout.  I don't know what plugin you are attempting to run remotely,
but check to make sure that the timeout on check_nrpe (A), on the
nrpe.cfg file (B) and for the remotely run plugin (C) are set as C<B<A.
Your error message seems to be timeout A.
 
Another possibility is that your check_nrpe is running in non-ssl mode,
but your nrpe daemon is running in SSL mode...  I notice that you have
given the -n option (non-SSL) in your init.d definition, but not in your
inetd.conf definition!  Are you using -n in your check_nrpe?  Pick one
and use it throughout...
 
Steve
--
Steve Shipway
ITSS, University of Auckland
(09) 3737 599 x 86487
s.shipway at auckland.ac.nz


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20061220/11b5e20e/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
-------------- next part --------------
_______________________________________________
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


More information about the Users mailing list