Page 3 of 12
Re: Where to start!?
Posted: Thu Feb 11, 2016 1:51 pm
by trafalgargirl
I assume even though this doc refers to nagios x it is still ok for nagios core?
Thanks
Sherri
Re: Where to start!?
Posted: Thu Feb 11, 2016 2:05 pm
by trafalgargirl
So following the instructions - I ended up with an error: Checking for SSL headers... configure: error: Cannot find ssl headers
there were a few others that came back as no during the ./configure command - not if that information would help?
Re: Where to start!?
Posted: Thu Feb 11, 2016 2:25 pm
by bwallace
Although the doc is for XI, installing the NRPE daemon and plugins on the remote host is the same whether you are using Core or XI.
You can also refer to this doc
https://assets.nagios.com/downloads/nag ... e/NRPE.pdf
As for the error "cannot find ssl headers" run this command to install the corresponding dependencies and (re) ./configure afterwards.
If any further problems please let us know what Linux distro + version your are installing NRPE on so we can better assist.
Re: Where to start!?
Posted: Thu Feb 11, 2016 4:00 pm
by trafalgargirl
Oh sorry about that - it was earlier in my posts. I am using Ubuntu 12.04.5 LTS (GNU/Linux 3.2.0-98-virtual x86_64)
I tried both apt-get and yum install openssl-devel and got the following error:
root@nagios:/tmp/nrpe-2.15# yum install openssl-devel
Setting up Install Process
No package openssl-devel available.
Nothing to do
Re: Where to start!?
Posted: Thu Feb 11, 2016 4:20 pm
by bwallace
My bad for missing that info in your earlier post - I assumed you were running Cent Os. The Ubuntu equivalent to 'openssl-devel' is 'libssl-dev' so you'll want to run:
Re: Where to start!?
Posted: Thu Feb 11, 2016 4:32 pm
by trafalgargirl
No - though I am wondering if it would have been easier...
So now I am getting the following error (which may or may not matter)
checking for SSL headers... SSL headers found in /usr
checking for SSL libraries... configure: error: Cannot find ssl libraries
Re: Where to start!?
Posted: Thu Feb 11, 2016 4:39 pm
by trafalgargirl
add to that - I did do a apt-get install gcc
since it said it was missing.
Re: Where to start!?
Posted: Thu Feb 11, 2016 5:32 pm
by bwallace
Alright, the condensed version of the following instructions are here
http://askubuntu.com/questions/133184/n ... -libraries
You'll have to use 'apt-file' to search for where these SSL headers reside and I don't think this is installed on Ubuntu by default. So, run the following:
then run
Now you should be ready to actually use apt-file, like so:
Code: Select all
apt-file search libssl |grep libssl-dev
You should see something similar to this:
Code: Select all
libssl-dev: /usr/lib/i386-linux-gnu/libssl.a
libssl-dev: /usr/lib/i386-linux-gnu/libssl.so
libssl-dev: /usr/lib/i386-linux-gnu/pkgconfig/libssl.pc
libssl-dev: /usr/share/doc/libssl-dev/changelog.Debian.gz
libssl-dev: /usr/share/doc/libssl-dev/changelog.gz
libssl-dev: /usr/share/doc/libssl-dev/copyright
Now you can reconfigure using the '--with-ssl-lib' option (run from the nrpe-* directory)
Code: Select all
./configure --with-ssl-lib=/usr/lib/i386-linux-gnu/
Thanks for your patience, let us know of the outcome.
Re: Where to start!?
Posted: Fri Feb 12, 2016 1:34 pm
by trafalgargirl
So I think I made progress
Everything went as described. I tried to do the following and it failed:
root@nagios:/usr/local/nagios/libexec# ./check_nrpe -H localhost
connect to address 127.0.0.1 port 5666: Connection refused
connect to host localhost port 5666: Connection refusedroot@nagios:/usr/local/nagios/libexec#
I did make sure that I had added the IP of our nagios server as described....
I also assume I need to do the same process on our nagios server?
Re: Where to start!?
Posted: Fri Feb 12, 2016 2:08 pm
by rkennedy
root@nagios:/usr/local/nagios/libexec# ./check_nrpe -H localhost
connect to address 127.0.0.1 port 5666: Connection refused
connect to host localhost port 5666: Connection refusedroot@nagios:/usr/local/nagios/libexec#
Is this from the Nagios server? You'll want to change 'localhost' to the remote client machine's IP address.