nrpe problem

[Jim Mozley]

*This message was transferred with a trial version of CommuniGate(tm) Pro*
Sorry, but the only thing I can suggest is trying to run this as a daemon to
see if this works, unless your inetd.conf is incorrect.

>  In /etc/inetd.conf :
>  # NRPE FOR NAGIOS
>  nrpe stream tcp nowait forum /usr/local/nagios/nrpe -c
>  /usr/local/nagios/nrpe.cfg --inetd

An example from Solaris of an entry has the full path name of the daemon
then the daemon followed by its options. Example below for tftpd:

tftp    dgram   udp6    wait    root    /usr/sbin/in.tftpd      in.tftpd -s
/opt/tftpboot

So should your entry be:

nrpe stream tcp nowait forum /usr/local/nagios/nrpe nrpe -c
/usr/local/nagios/nrpe.cfg --inetd

Anyone else any ideas?

Regards,

Jim

----- Original Message ----- 
From: "Sylvain Padoan" <sylvain.padoan at sihpic.fr>
To: <Nagios-users at lists.sourceforge.net>
Sent: Wednesday, June 11, 2003 9:25 AM
Subject: Re: [Nagios-users] nrpe problem


when a try to start nrpe with   /usr/local/nagios/nrpe -c nrpe.cfg --inetd
In /var/log/messages:
Jun 11 10:15:15 forum nrpe[1368]: Added
command[check_users]=/usr/local/nagios/libexec/check_users -w 5 -c 10
Jun 11 10:15:15 forum nrpe[1368]: Added
command[check_disk]=/usr/local/nagios/libexec/check_disk -w 80 -c 75 -p
/dev/rd/c0d0p3
Jun 11 10:15:15 forum nrpe[1368]: Added
command[check_procs]=/usr/local/nagios/libexec/check_procs -w 60 -c 100
Jun 11 10:15:15 forum nrpe[1368]: Handling the connection...
Jun 11 10:15:15 forum nrpe[1368]: Could not read request from client,
bailing out...

what is the problem? (Could not read request from client, bailing out...)
  ----- Original Message ----- 
  From: Sylvain Padoan
  To: nagios-users at lists.sourceforge.net
  Sent: Wednesday, June 11, 2003 9:39 AM
  Subject: [Nagios-users] nrpe problem


  I run nrpe in my inetd.
  In nrpe.cfg :
  debug=1 (I don't see deference if debug=0 !!)
  command[check_users]=/usr/local/nagios/libexec/check_users -w 5 -c 10

  In /etc/inetd.conf :
  # NRPE FOR NAGIOS
  nrpe stream tcp nowait forum /usr/local/nagios/nrpe -c
  /usr/local/nagios/nrpe.cf
  g --inetd

  a user in my remote host : forum (group=users)

  In /etc/services
  nrpe            5666/tcp                        # nrpe for NAGIOS


  I don't know.
  tanks,

  sylvain


  ----- Original Message -----
  From: "Jim Mozley" <jim.mozley at exponential-e.com>
  To: "Sylvain Padoan" <sylvain.padoan at sihpic.fr>
  Sent: Tuesday, June 10, 2003 6:42 PM
  Subject: Re: [Nagios-users] nrpe probleme


  > *This message was transferred with a trial version of CommuniGate(tm)
Pro*
  > Have you checked nrpe.cfg and set the appropriate values in this?
  >
  > Jim
  >
  > ----- Original Message -----
  > From: "Sylvain Padoan" <sylvain.padoan at sihpic.fr>
  > To: <nagios-users at lists.sourceforge.net>
  > Sent: Tuesday, June 10, 2003 4:31 PM
  > Subject: [Nagios-users] nrpe probleme
  >
  >
  > hello,
  >
  > when i want to excecute a plugin in my nagios serveur to a remote host,
  > nagios said:
  >
  > nagios:/usr/local/nagios # ./libexec/check_nrpe -H 126.0.22.71 -c
  > check_users
  > CHECK_NRPE: Error receiving data from host.
  >
  >
  > but when i want to excecute a plugin in my remote host, nagios said :
  (it's
  > ok!)
  >
  > root at forum:/usr/local/nagios/libexec >
  > /usr/local/nagios/libexec/check_users -w 5 -c 10
  > USERS OK - 1 users currently logged in
  >
  >
  > my version of nagios : 1.0 in SuSE 7.2
  >
  > Any ideas ? Thanks a lot.
  >
  >
  > sylvain
  >




-------------------------------------------------------
This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at 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