[Nagiosplug-help] NRPE and NRPE NT problems

[Mike Feetham]

If the event log says the NRPE commands are running (On the NT side of
things) then your setup seems to be good.  What commands have you created on
your hosts, and does the service account have proper permissions to run
these commands?

Have you tried manually running the commands on the hosts?  Make sure they
are returning only one line of text to STDOUT, and also check that they are
using the appropriate exit codes.
 

Mike Feetham

-----Original Message-----
From: nagiosplug-help-admin at lists.sourceforge.net
[mailto:nagiosplug-help-admin at lists.sourceforge.net] On Behalf Of Joshua
Wales
Sent: Wednesday, July 21, 2004 10:04 AM
To: Nagiosplug-help at lists.sourceforge.net
Subject: [Nagiosplug-help] NRPE and NRPE NT problems

I'm running nagios 1.2 on a red hat enterprise 3 server with plugin
version 1.3.1 and nrpe 2.0 running on a unix test machine and nrpe_NT
running on a windows xp test machine. All my regular checks are working
but the nrpe checks are not.

        The NRPE NT checks all return "no output available" even though
they run successfully on the windows NRPE machine itself. The NRPE
checks returne "NRPE: Unable to read output" even though the
checks are successful on the Sun NRPE machine.
      I have no idea what is going wrong between them here, but any advice
would be appreciated. I haven't been working with linux/unix very
long, so please bare with me. Thank you and God bless.

Josh Wales


-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
Nagiosplug-help mailing list
Nagiosplug-help at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagiosplug-help
::: Please include plugins version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null