NRPE: Unable to read output

Marc Powell marc at ena.com
Wed May 28 23:18:19 CEST 2008


On May 28, 2008, at 1:56 PM, Kaushal Shriyan wrote:

> On Thu, May 29, 2008 at 12:22 AM, Marc Powell <marc at ena.com> wrote:
>

>
> NRPE provides a debug option for problems such as this. There could be
> many causes and you haven't provided any information to say which. If
> you need further assistance, please detail
>
> NRPE version
> How installed (source or package; which package)
> How is it being run (inetd, xinetd, daemon)
> (x)inetd configuration if that's being used.
> any (x)inetd errors being generated if that's being used.
> NRPE debug output when check is executed.
> NRPE configuration for the command
> Example test run of the check_total_procs command run on the
> destination host as the NRPE user.
> and, last but certainly not least, any troubleshooting/googleing
> you've already done so that we don't repeat the ground you've already
> covered.
>

>
> Hi Marc
>
> I have enabled debug=1, But not able to see anything in the syslog  
> when i restart the nrpe using the below command
>
> sudo /etc/init.d/nrpe restart
>
> Any further clue

No, not until you provide the information that's already been asked  
for. That will pretty much eliminate common problems. You're  
essentially asking us to make wild guesses based on no information and  
keep trying when they're wrong. It's a waste of time for all of us.  
I've seen 2 of the 10 in this thread; nrpe version and (no) nrpe debug  
output.

--
Marc




-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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