Installing NRPE agent on SLES 11 SP3+

[dlukinski]

Hello XI support

Please help with guidance in installing latest NRPE agent on SLES 11 SP3+ (makes 50% of our Linux servers we are yet to monitor).

Thank you

[dlukinski]

Clean install (./fullinstall) of NRPE agent on SLES11 SP3+ (also clean installed)
Doe snot work, producing (Return code of 255 is out of bounds) error for all checks

[hsmith]

While I don't have a SLES license I am able to use here, I did test this with openSUSE 13.2 as you asked about in your previous post. I got the fullinstall script to work, but it did take a little bit of "hacking together". I'll post my results here and hopefully they can lead you in the right direction as far as getting it working on your SLES machine.

steps:

I used our fullinstall script, documented in this pdf, and it failed immediately.

I had to make the following modification, since openSUSE leap identifies a bit differently:

You'll notice this line(mine shows line numbers, yours will not):

Code: Select all

 74 elif [ "$distro" == "openSUSE" ] || [ "$distro" == "SUSE LINUX" ]; then
 75         caninstall="yes"

Below it, add the following two lines for it to work on openSUSE 13.2:

Code: Select all

elif [ "$distro" == "openSUSE Leap" ] || [ "$distro" == "SUSE LINUX" ]; then
        caninstall="yes"

I ran the fullinstall script, and it failed once more. The error I got was:

Code: Select all

configure: error: no acceptable C compiler found in $PATH
See `config.log' for more details.

Normally, the fullinstall script will take care of that for you, it may be a little different on openSUSE 13.2 though.

Okay, so my prereqs for running the fullinstall script were not there, easy enough, with a little help from box293's article I got a list of prerequisites I will need.

I installed said dependencies in a somewhat messy fashion, because I wanted to watch each one to make sure it worked right. Here's my history file:

Code: Select all

16  2016-01-11 10:42:25 zypper install gcc
   17  2016-01-11 10:43:01 zypper install make
   18  2016-01-11 10:44:20 zypper install openssl-devel
   19  2016-01-11 10:44:31 zypper install glibc
   20  2016-01-11 10:44:41 zypper install libmcrypt-devel
   21  2016-01-11 10:44:52 zypper install xinetd
   22  2016-01-11 10:45:08 zypper install sysstat
   23  2016-01-11 10:45:21 zypper install bc

At the end, it asked me for my allowed IP addresses, which is a great sign.

Code: Select all

###############################################################################
###                                                                          ###
### NRPE is currently set to allow connections only from these IP addresses: ###
###                                                                          ###
### 127.0.0.1                                                                ###
###                                                                          ###
### If you would like to change this list, enter all IP addresses to allow,  ###
### separated by spaces only, and then press Enter.                          ###
### (Put the address(es) of your Nagios XI servers(s) here.)                 ###
###                                                                          ###
################################################################################

Allow from:  172.16.0.5

Subcomponents installed OK
RESULT=0

##########################################################
###                                                    ###
###    Nagios XI Linux Agent Installation Complete!    ###
###                                                    ###
##########################################################

Great, let's test it from my XI server!

Code: Select all

[root@XI5 tmp]# /usr/local/nagios/libexec/check_nrpe -H 172.16.0.56
NRPE v2.15

That's a successful test. So, you're right, at least pertaining to the version of openSUSE you posted about in the previous thread, the fullinstall script can probably use some openSUSE love. I hope this information can be useful for SLES. Let me know if you have questions.

[dlukinski]

While I don't have a SLES license I am able to use here, I did test this with openSUSE 13.2 as you asked about in your previous post. I got the fullinstall script to work, but it did take a little bit of "hacking together". I'll post my results here and hopefully they can lead you in the right direction as far as getting it working on your SLES machine.

steps:

I used our fullinstall script, documented in this pdf, and it failed immediately.

I had to make the following modification, since openSUSE leap identifies a bit differently:

You'll notice this line(mine shows line numbers, yours will not):

Code: Select all

 74 elif [ "$distro" == "openSUSE" ] || [ "$distro" == "SUSE LINUX" ]; then
 75         caninstall="yes"

Below it, add the following two lines for it to work on openSUSE 13.2:

Code: Select all

elif [ "$distro" == "openSUSE Leap" ] || [ "$distro" == "SUSE LINUX" ]; then
        caninstall="yes"

I ran the fullinstall script, and it failed once more. The error I got was:

Code: Select all

configure: error: no acceptable C compiler found in $PATH
See `config.log' for more details.

Normally, the fullinstall script will take care of that for you, it may be a little different on openSUSE 13.2 though.

Okay, so my prereqs for running the fullinstall script were not there, easy enough, with a little help from box293's article I got a list of prerequisites I will need.

I installed said dependencies in a somewhat messy fashion, because I wanted to watch each one to make sure it worked right. Here's my history file:

Code: Select all

16  2016-01-11 10:42:25 zypper install gcc
   17  2016-01-11 10:43:01 zypper install make
   18  2016-01-11 10:44:20 zypper install openssl-devel
   19  2016-01-11 10:44:31 zypper install glibc
   20  2016-01-11 10:44:41 zypper install libmcrypt-devel
   21  2016-01-11 10:44:52 zypper install xinetd
   22  2016-01-11 10:45:08 zypper install sysstat
   23  2016-01-11 10:45:21 zypper install bc

At the end, it asked me for my allowed IP addresses, which is a great sign.

Code: Select all

###############################################################################
###                                                                          ###
### NRPE is currently set to allow connections only from these IP addresses: ###
###                                                                          ###
### 127.0.0.1                                                                ###
###                                                                          ###
### If you would like to change this list, enter all IP addresses to allow,  ###
### separated by spaces only, and then press Enter.                          ###
### (Put the address(es) of your Nagios XI servers(s) here.)                 ###
###                                                                          ###
################################################################################

Allow from:  172.16.0.5

Subcomponents installed OK
RESULT=0

##########################################################
###                                                    ###
###    Nagios XI Linux Agent Installation Complete!    ###
###                                                    ###
##########################################################

Great, let's test it from my XI server!

Code: Select all

[root@XI5 tmp]# /usr/local/nagios/libexec/check_nrpe -H 172.16.0.56
NRPE v2.15

That's a successful test. So, you're right, at least pertaining to the version of openSUSE you posted about in the previous thread, the fullinstall script can probably use some openSUSE love. I hope this information can be useful for SLES. Let me know if you have questions.

In our case ./fullinstall ran on SLES right away fi5rst time, but produced that error anyways
After reading your post I attempted installing pre-reqs listed (most were already there except for gcc and sysstat; openssl-devel did not apply)

We made no changes to ./fullinstall script (wasn't OpenSuse we tested with)

This now works in one test case and I am to try to few more installs, including production, before asking to close this thread.
-----------------------------------------------------------------------------------------------------------------------------------
So In general, we should add all the prereqs and run ./fullinstall after that (when it comes to SLES 11 SP3+)?

P.S. I'll have separate thread opened for REDHAT EL 5.x / 6.x

Thank you once again

[hsmith]

I would recommend you run the dependencies first, yeah. If I had SLES available to me, I would test that out as well, I like trying new stuff out. I am not sure why none of the prereqs were installed from the script, but I would suggest you make sure that you have all of the packages that I zypper installed. I'm not sure why you wouldn't need openssl-devel, NRPE uses SSL for secure communication.

Are your checks still failing?

[dlukinski]

I would recommend you run the dependencies first, yeah. If I had SLES available to me, I would test that out as well, I like trying new stuff out. I am not sure why none of the prereqs were installed from the script, but I would suggest you make sure that you have all of the packages that I zypper installed. I'm not sure why you wouldn't need openssl-devel, NRPE uses SSL for secure communication.

Are your checks still failing?

all good now: 2 x SLES and 1 x OpenSuse installs now operational

Please keep this open until we try production installs (servers that are already in use)

[tmcdonald]

Please keep this open until we try production installs (servers that are already in use)

You got it.

[dlukinski]

Please keep this open until we try production installs (servers that are already in use)

You got it.

Please close this thread: opened new (appears us having same problems with NRPE 2.15)
- Some NRPE checks are in UNKNOWN state after fresh install Attachment(s) is a new thread name

[lmiltchev]

Please close this thread: opened new (appears us having same problems with NRPE 2.15)
- Some NRPE checks are in UNKNOWN state after fresh install Attachment(s) is a new thread name

Closing the thread.