<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40"> <head> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <meta name=ProgId content=Word.Document> <meta name=Generator content="Microsoft Word 9"> <meta name=Originator content="Microsoft Word 9"> <link rel=File-List href="cid:filelist.xml@01C28A45.11EA9D00">  <style>  </style> </head> <body lang=EN-US style='tab-interval:.5in'> <div class=Section1> That was it.. Guess it wants the full path in there. This problem would be easily averted if they’d put a sample nrpe.cfg somewhere in the docs. I was actually looking at the nrpe.cfg file wondering if it wanted the full path earlier when I saw the permission denied. Thought maybe it was trying to run the directory instead of the actual nrpe executable. Didn’t have a chance to try it though until now. Thanks again<o:p></o:p> <![if !supportEmptyParas]> <![endif]><o:p></o:p> Gerald Wichmann<o:p></o:p> Senior Systems Development Engineer<o:p></o:p> Zantaz, Inc.<o:p></o:p> 925.598.3099 (w)<o:p></o:p> <![if !supportEmptyParas]> <![endif]><o:p></o:p> -----Original Message----- From: Carroll, Jim P [Contractor] [mailto:jcarro10@sprintspectrum.com] Sent: Tuesday, November 12, 2002 11:48 AM To: Gerald Wichmann; nagios-users@lists.sourceforge.net Subject: RE: NRPE Problems <![if !supportEmptyParas]> <![endif]><o:p></o:p> I think I know what the problem is. It's in your /etc/xinetd.d/nrpe file. Here's mine:<o:p></o:p> <o:p></o:p> $ cat nrpe # default: on # description: NRPE service nrpe { flags = REUSE socket_type = stream wait = no user = nagios server = /home/nagios/bin/nrpe server_args = -i /home/nagios/etc/nrpe.cfg log_on_failure += USERID disable = no only_from = 127.0.0.1 10.108.58.68 10.108.58.69 }<o:p></o:p> For reference, my server binary is /home/nagios/bin/nrpe, and the config file is /home/nagios/etc/nrpe.cfg.<o:p></o:p> <o:p></o:p> Make the necessary changes and see if that helps.<o:p></o:p> <o:p></o:p> jc<o:p></o:p> <div style='border:none;border-left:solid navy 1.5pt;padding:0in 0in 0in 4.0pt'> -----Original Message----- From: Gerald Wichmann [mailto:gwichman@zantaz.com] Sent: Tuesday, November 12, 2002 1:21 PM To: nagios-users@lists.sourceforge.net Cc: Carroll, Jim P [Contractor] Subject: NRPE Problems<o:p></o:p> Ok you guys were right. It was monitoring my local box not the boxes I thought it was. In my attempts to implement NRPE I seem to have done something wrong.. All the files I believe are in place and xinetd seems to start normally. But when I do a check_nrpe for some command it fails. My Nagios service page lists status as UNKNOWN and status information as “CHECK_NRPE: Error receiving data from host.” Any ideas as to what I’m missing? I can post more output as necessary but I think the below is everything.:<o:p></o:p> <o:p></o:p> [root@PS-NAT libexec]# ./check_nrpe 10.1.82.30 -c check_disk1<o:p></o:p> CHECK_NRPE: Error receiving data from host.<o:p></o:p> [root@PS-NAT libexec]#<o:p></o:p> <o:p></o:p> /var/log/messages of xinetd restarting and then a log for when I attempt the above check_nrpe:<o:p></o:p> <o:p></o:p> Nov 12 11:03:38 ps-sm-poly-00 xinetd[8359]: Exiting...<o:p></o:p> Nov 12 11:03:38 ps-sm-poly-00 xinetd[3178]: chargen disabled, removing<o:p></o:p> Nov 12 11:03:38 ps-sm-poly-00 xinetd[3178]: chargen disabled, removing<o:p></o:p> Nov 12 11:03:38 ps-sm-poly-00 xinetd[3178]: daytime disabled, removing<o:p></o:p> Nov 12 11:03:38 ps-sm-poly-00 xinetd[3178]: daytime disabled, removing<o:p></o:p> Nov 12 11:03:38 ps-sm-poly-00 xinetd[3178]: echo disabled, removing<o:p></o:p> Nov 12 11:03:38 ps-sm-poly-00 xinetd[3178]: echo disabled, removing<o:p></o:p> Nov 12 11:03:38 ps-sm-poly-00 xinetd[3178]: rsync disabled, removing<o:p></o:p> Nov 12 11:03:38 ps-sm-poly-00 xinetd[3178]: time disabled, removing<o:p></o:p> Nov 12 11:03:38 ps-sm-poly-00 xinetd[3178]: time disabled, removing<o:p></o:p> Nov 12 11:03:38 ps-sm-poly-00 xinetd[3178]: xinetd Version 2.3.0 started with libwrap options compiled in.<o:p></o:p> Nov 12 11:03:38 ps-sm-poly-00 xinetd[3178]: Started working: 2 available services<o:p></o:p> Nov 12 11:04:15 ps-sm-poly-00 xinetd[4990]: execv( /usr/sbin ) failed: Permission denied (errno = 13)<o:p></o:p> <o:p></o:p> NOTE the bottom entry. That’s what it logs anytime I try to do a check_nrpe command from the nagios server (so my log is filled with them)<o:p></o:p> <o:p></o:p> Attempt to Telnet to port 5666 on the box running NRPE (from the nagios server):<o:p></o:p> <o:p></o:p> [root@PS-NAT libexec]# telnet 10.1.82.30 5666<o:p></o:p> <a name="OLE_LINK1">Trying 10.1.82.30...</a><o:p></o:p> Connected to 10.1.82.30.<o:p></o:p> Escape character is '^]'.<o:p></o:p> Connection closed by foreign host.<o:p></o:p> [root@PS-NAT libexec]#<o:p></o:p> <o:p></o:p> Which differs from when I try to connect to a port where nothing is listening on:<o:p></o:p> <o:p></o:p> Trying 10.1.82.30...<o:p></o:p> telnet: connect to address 10.1.82.30: Connection refused<o:p></o:p> <o:p></o:p> Various files, paths, configs, permissions of NRPE setup:<o:p></o:p> <o:p></o:p> [root@ps-sm-poly-00 /root]# cat /etc/xinetd.d/nrpe<o:p></o:p> # default: on<o:p></o:p> # description: NRPE<o:p></o:p> service nrpe<o:p></o:p> {<o:p></o:p> flags = REUSE<o:p></o:p> socket_type = stream<o:p></o:p> wait = no<o:p></o:p> user = nagios<o:p></o:p> server = /usr/sbin<o:p></o:p> server_args = -i /usr/local/nagios<o:p></o:p> log_on_failure += USERID<o:p></o:p> disable = no<o:p></o:p> only_from = 10.1.82.21<o:p></o:p> }<o:p></o:p> <o:p></o:p> <o:p></o:p> [root@ps-sm-poly-00 /root]# ls -l /usr/local/nagios<o:p></o:p> total 6<o:p></o:p> drwxr-xr-x 2 root root 1304 Nov 11 22:37 libexec<o:p></o:p> -rw-r--r-- 1 root root 3303 Nov 11 22:29 nrpe.cfg<o:p></o:p> <o:p></o:p> <o:p></o:p> [root@ps-sm-poly-00 /root]# ls -l /usr/sbin/nrpe<o:p></o:p> -rwxr-xr-x 1 root root 80002 Nov 11 22:28 /usr/sbin/nrpe<o:p></o:p> <o:p></o:p> <o:p></o:p> [root@ps-sm-poly-00 /root]# cat /usr/local/nagios/nrpe.cfg<o:p></o:p> #############################################################################<o:p></o:p> # Sample NRPE Config File<o:p></o:p> # Written by: Ethan Galstad (nagios@nagios.org)<o:p></o:p> #<o:p></o:p> # Last Modified: 06-03-2002<o:p></o:p> #<o:p></o:p> # NOTES:<o:p></o:p> # This is a sample configuration file for the NRPE daemon. It needs to be<o:p></o:p> # located on the remote host that is running the NRPE daemon, not the host<o:p></o:p> # from which the check_nrpe client is being executed.<o:p></o:p> #############################################################################<o:p></o:p> <o:p></o:p> <o:p></o:p> <o:p></o:p> # PORT NUMBER<o:p></o:p> # Port number we should wait for connections on.<o:p></o:p> # NOTE: This must be a non-priviledged port (i.e. > 1024).<o:p></o:p> # NOTE: This option is ignored if NRPE is running under either inetd or xinetd<o:p></o:p> <o:p></o:p> server_port=5666<o:p></o:p> <o:p></o:p> <o:p></o:p> <o:p></o:p> # SERVER ADDRESS<o:p></o:p> # Address that nrpe should bind to in case there are more than one interface<o:p></o:p> # and you do not want nrpe to bind on all interfaces.<o:p></o:p> # NOTE: This option is ignored if NRPE is running under either inetd or xinetd<o:p></o:p> <o:p></o:p> server_address=10.1.82.21<o:p></o:p> <o:p></o:p> <o:p></o:p> <o:p></o:p> # ALLOWED HOST ADDRESSES<o:p></o:p> # This is a comma-delimited list of IP address of hosts that are allowed<o:p></o:p> # to talk to the NRPE daemon.<o:p></o:p> #<o:p></o:p> # NOTE: The daemon only does rudimentary checking of the client's IP<o:p></o:p> # address. I would highly recommend adding entries in your<o:p></o:p> # /etc/hosts.allow file to allow only the specified host to connect<o:p></o:p> # to the port you are running this daemon on.<o:p></o:p> #<o:p></o:p> # NOTE: This option is ignored if NRPE is running under either inetd or xinetd<o:p></o:p> <o:p></o:p> allowed_hosts=10.1.82.21<o:p></o:p> <o:p></o:p> <o:p></o:p> <o:p></o:p> # NRPE USER<o:p></o:p> # This determines the effective user that the NRPE daemon should run as.<o:p></o:p> # You can either supply a username or a UID.<o:p></o:p> #<o:p></o:p> # NOTE: This option is ignored if NRPE is running under either inetd or xinetd<o:p></o:p> <o:p></o:p> nrpe_user=nagios<o:p></o:p> <o:p></o:p> <o:p></o:p> <o:p></o:p> # NRPE GROUP<o:p></o:p> # This determines the effective group that the NRPE daemon should run as.<o:p></o:p> # You can either supply a group name or a GID.<o:p></o:p> #<o:p></o:p> # NOTE: This option is ignored if NRPE is running under either inetd or xinetd<o:p></o:p> <o:p></o:p> nrpe_group=nagios<o:p></o:p> <o:p></o:p> <o:p></o:p> <o:p></o:p> # DEBUGGING OPTION<o:p></o:p> # This option determines whether or not debugging messages are logged to the<o:p></o:p> # syslog facility.<o:p></o:p> # Values: 0=debugging off, 1=debugging on<o:p></o:p> <o:p></o:p> debug=1<o:p></o:p> <o:p></o:p> <o:p></o:p> <o:p></o:p> # COMMAND DEFINITIONS<o:p></o:p> # Command definitions that this daemon will run. Definitions<o:p></o:p> # are in the following format:<o:p></o:p> #<o:p></o:p> # command[<command_name>]=<command_line><o:p></o:p> #<o:p></o:p> # When the daemon receives a request to return the results of <command_name><o:p></o:p> # it will execute the command specified by the <command_line> argument.<o:p></o:p> #<o:p></o:p> # Unlike Nagios, the command line cannot contain macros - it must be<o:p></o:p> # typed exactly as it should be executed.<o:p></o:p> #<o:p></o:p> # Note: Any plugins that are used in the command lines must reside<o:p></o:p> # on the machine that this daemon is running on! The examples below<o:p></o:p> # assume that you have plugins installed in a /usr/local/nagios/libexec<o:p></o:p> # directory.<o:p></o:p> <o:p></o:p> command[check_users]=/usr/local/nagios/libexec/check_users 5 10<o:p></o:p> command[check_load]=/usr/local/nagios/libexec/check_load 5 10 15 20 25 30<o:p></o:p> command[check_disk1]=/usr/local/nagios/libexec/check_disk 80 95 /dev/hda6<o:p></o:p> command[check_disk2]=/usr/local/nagios/libexec/check_disk 80 95 /dev/hda10<o:p></o:p> command[check_disk3]=/usr/local/nagios/libexec/check_disk 80 95 /dev/sda1<o:p></o:p> command[check_zombie_procs]=/usr/local/nagios/libexec/check_procs 5 10 Z<o:p></o:p> command[check_total_procs]=/usr/local/nagios/libexec/check_procs 150 200<o:p></o:p> command[check_smtp]=/usr/local/nagios/libexec/check_smtp<o:p></o:p> <o:p></o:p> <o:p></o:p> <o:p></o:p> [root@ps-sm-poly-00 /root]# ls -l /usr/local/nagios/libexec/<o:p></o:p> total 696<o:p></o:p> -rwxr-xr-x 1 root root 2264 Jul 8 08:37 check_breeze<o:p></o:p> -rwxr-xr-x 1 root root 21557 Jul 8 08:37 check_by_ssh<o:p></o:p> -rwxr-xr-x 1 root root 21468 Jul 8 08:37 check_disk<o:p></o:p> -rwxr-xr-x 1 root root 7741 Jul 8 08:37 check_disk_smb<o:p></o:p> -rwxr-xr-x 1 root root 21554 Jul 8 08:37 check_dns<o:p></o:p> -rwxr-xr-x 1 root root 11462 Jul 8 08:37 check_dummy<o:p></o:p> -rwxr-xr-x 1 root root 3830 Jul 8 08:37 check_flexlm<o:p></o:p> -rwxr-xr-x 1 root root 19341 Jul 8 08:37 check_ftp<o:p></o:p> -rwxr-xr-x 1 root root 37436 Jul 8 08:37 check_http<o:p></o:p> -rwxr-xr-x 1 root root 19072 Jul 8 08:37 check_imap<o:p></o:p> -rwxr-xr-x 1 root root 7434 Jul 8 08:37 check_ircd<o:p></o:p> -rwxr-xr-x 1 root root 19372 Jul 8 08:37 check_load<o:p></o:p> -rwxr-xr-x 1 root root 5207 Jul 8 08:37 check_log<o:p></o:p> -rwxr-xr-x 1 root root 17699 Jul 8 08:37 check_mrtg<o:p></o:p> -rwxr-xr-x 1 root root 16036 Jul 8 08:37 check_mrtgtraf<o:p></o:p> -rwxr-xr-x 1 root root 19527 Jul 8 08:37 check_nagios<o:p></o:p> -rwxr-xr-x 1 root root 20291 Jul 8 08:37 check_nntp<o:p></o:p> -rwxr-xr-x 1 root root 7853 Jul 8 08:37 check_ntp<o:p></o:p> -rwxr-xr-x 1 root root 27386 Jul 8 08:37 check_nwstat<o:p></o:p> -rwxr-xr-x 1 root root 4324 Jul 8 08:37 check_oracle<o:p></o:p> -rwxr-xr-x 1 root root 21786 Jul 8 08:37 check_overcr<o:p></o:p> -rwxr-xr-x 1 root root 24254 Jul 8 08:37 check_ping<o:p></o:p> -rwxr-xr-x 1 root root 19296 Jul 8 08:37 check_pop<o:p></o:p> -rwxr-xr-x 1 root root 23856 Jul 8 08:37 check_procs<o:p></o:p> -rwxr-xr-x 1 root root 21050 Jul 8 08:37 check_real<o:p></o:p> -rwxr-xr-x 1 root root 9695 Jul 8 08:37 check_rpc<o:p></o:p> -rwxr-xr-x 1 root root 1180 Jul 8 08:37 check_sensors<o:p></o:p> -rwxr-xr-x 1 root root 19590 Jul 8 08:37 check_smtp<o:p></o:p> -rwxr-xr-x 1 root root 17952 Jul 8 08:37 check_ssh<o:p></o:p> -rwxr-xr-x 1 root root 19382 Jul 8 08:37 check_swap<o:p></o:p> -rwxr-xr-x 1 root root 24484 Jul 8 08:37 check_tcp<o:p></o:p> -rwxr-xr-x 1 root root 20547 Jul 8 08:37 check_time<o:p></o:p> -rwxr-xr-x 1 root root 19293 Jul 8 08:37 check_udp<o:p></o:p> -rwxr-xr-x 1 root root 24689 Jul 8 08:37 check_ups<o:p></o:p> -rwxr-xr-x 1 root root 17946 Jul 8 08:37 check_users<o:p></o:p> -rwxr-xr-x 1 root root 19259 Jul 8 08:37 check_vsz<o:p></o:p> -rwxr-xr-x 1 root root 3016 Jul 8 08:37 check_wave<o:p></o:p> -rwxr-xr-x 1 root root 16752 Jul 8 08:37 urlize<o:p></o:p> -rwxr-xr-x 1 root root 1974 Jul 8 08:37 utils.pm<o:p></o:p> -rwxr-xr-x 1 root root 739 Jul 8 08:37 utils.sh<o:p></o:p> [root@ps-sm-poly-00 /root]#<o:p></o:p> <o:p></o:p> <o:p></o:p> <o:p></o:p> Gerald Wichmann<o:p></o:p> Senior Systems Development Engineer<o:p></o:p> Zantaz, Inc.<o:p></o:p> 925.598.3099 (w)<o:p></o:p>  <o:p></o:p> <![if !supportEmptyParas]> <![endif]><o:p></o:p> This e-mail has been captured and archived by the ZANTAZ Digital Safe(tm) service. For more information, visit us at www.zantaz.com. <o:p></o:p> IMPORTANT: This electronic mail message is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential or exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by telephone or directly reply to the original message(s) sent. Thank you.<o:p></o:p> </div> </div> </body> </html> This e-mail has been captured and archived by the ZANTAZ Digital Safe(tm) service. For more information, visit us at www.zantaz.com. IMPORTANT: This electronic mail message is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential or exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by telephone or directly reply to the original message(s) sent. Thank you.