From: Rahul Nabar [mailto:rpna...@gmail.com] Sent: Monday, January 26, 2009 3:09 PM To: Andy Shellam Cc: Nagios-Users Mailinglist Subject: Re: [Nagios-users] NRPE installation fails since check_nrpe pluginis not found in the libexec directory
On Mon, Jan 26, 2009 at 1:38 PM, Andy Shellam <andy-li...@networkmail.eu> wrote: Hi Rahul, The error it's returning suggests that "check_nrpe" is not in the "src" subdirectory of the current directory (/usr/local/src/nagios_nodes/downloads/nrpe-2.8/src.) It looks as if the plugin has not been built. Do you in fact have "check_nrpe" in the above mentioned directory? What was the final output from "make" ? I'm guessing it threw an error. Thanks again Andy! I don't seem to have the "check_nrpe". Neither here nor in /usr/local/nagios/libexec. All the other scripts seem to be present there though! But not this one. You are right. make did throw errors (I got carried away by my previous successful installs and did not notice!) Snippet attached below but it seems to be a bunch of SSL errors that prevent it from compiling check_nrpe. I traced back further and checked config.log for the nagios-plugins-1.4.13 and it shows: configure:24258: WARNING: OpenSSL or GnuTLS libs could not be found or were disabled I'm not sure why though! "yum info openssl.i686 openssl-devel.i386" show those both packages as "installed" ANy other sugesstions? -- Rahul ----------- Yes, check to ensure gnutls is also installed (rpm -q | grep tls) , and also run "ldconfig -v | grep ssl" and just be sure it can see the openssl-related *.so file(s).... ;) Regards, Jamie ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Nagios-users mailing list Nagios-users@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
