Page 2 of 2

Re: Monitoring Linux SUSE from Nagios

Posted: Fri Oct 31, 2014 10:56 am
by jkinning
glibc and syslog-ng are installed. I tried using different version and still nada.

Re: Monitoring Linux SUSE from Nagios

Posted: Fri Oct 31, 2014 1:12 pm
by lmiltchev
Have you tried using the following links?

http://assets.nagios.com/downloads/ncpa/download.php

I haven't tested the OpenSUSE ones, but they should work. Let me know if you get stuck on something.

Re: Monitoring Linux SUSE from Nagios

Posted: Fri Oct 31, 2014 1:27 pm
by jkinning
From my earlier post:

I tried install both ncpa-1.7.2.os12.x86_64.rpm and ncpa-1.7.2.os13.x86_64.rpm both give me the same errors.

Retrieving package ncpa-1.7.2-1.x86_64 (1/1), 7.4 MiB (27.1 MiB unpacked)
Retrieving package ncpa-1.7.2-1.x86_64 (1/1), 7.4 MiB (27.1 MiB unpacked)
Installing: ncpa-1.7.2-1 [done]
Additional rpm output:
uid=1000(nagios) gid=1000(nagcmd) groups=16(dialout),33(video),1000(nagcmd)
insserv: Service syslog is missed in the runlevels 4 to use service ncpa_listener
ncpa_listener 0:off 1:off 2:on 3:on 4:on 5:on 6:off
insserv: Service syslog is missed in the runlevels 4 to use service ncpa_listener
ncpa_passive 0:off 1:off 2:on 3:on 4:on 5:on 6:off
./ncpa_posix_listener: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by ./ncpa_posix_listener)
./ncpa_posix_listener: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /usr/local/ncpa/libpython2.7.so.1.0)
Started listener...
/usr/local/ncpa/ncpa_posix_passive: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /usr/local/ncpa/ncpa_posix_passive)
/usr/local/ncpa/ncpa_posix_passive: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /usr/local/ncpa/libpython2.7.so.1.0)
Started passive agent...

The links above are for openSUSE not SLES. Is it possible to install the NCPA on the Enterprise version of SUSE? I noticed a thread about getting security hits using the nrpe agent and I don't want to install that agent just to change later on.

Re: Monitoring Linux SUSE from Nagios

Posted: Fri Oct 31, 2014 1:43 pm
by lmiltchev
I will test installing NCPA on OpenSUSE and will get back to you with the results. It will take some time though.
Is it possible to install the NCPA on the Enterprise version of SUSE?
It hasn't been tested/documented. They are somewhat similar, so I think you should be able to install NCPA on SLES but I could be wrong.

Re: Monitoring Linux SUSE from Nagios

Posted: Fri Oct 31, 2014 2:27 pm
by jkinning
You need to try and install it on the Enterprise version SLES. I'm sure openSUSE would work as that is what the package says but with SLES I encountered those issues.

Re: Monitoring Linux SUSE from Nagios

Posted: Mon Nov 03, 2014 11:54 am
by abrist
It may be best to open a github issue for this problem as it will get much better exposure to Nick and the nagiso devs. You can post the issue at the following link: https://github.com/NagiosEnterprises/ncpa
If you like, I can post your issue there myself instead.

Re: Monitoring Linux SUSE from Nagios

Posted: Tue Nov 11, 2014 8:24 am
by jkinning
Thanks. I've submitted a new issue on the github page.

Re: Monitoring Linux SUSE from Nagios

Posted: Tue Nov 11, 2014 11:46 am
by slansing
Thank you very much jkinning, the team will take a look at it as soon as possible.

Re: Monitoring Linux SUSE from Nagios

Posted: Thu Sep 03, 2015 12:12 pm
by minnow
I have successfully installed the prm package ncpa-1.8.1-1.os12.x86_64.rpm on a SUSE 12 server and deplyed the NCPA agent. Most of our Linux server are SSUE 11 R2 or R3 as well, so as ofnwo that's still the challange for the NCPA.

Re: Monitoring Linux SUSE from Nagios

Posted: Thu Sep 03, 2015 1:45 pm
by tmcdonald
This thread is quite old, and it sounds like the issue has been at least partially resolved. For the sake of organization, I am going to ask that we start with a clean slate and you open a new thread for the issue with NCPA on other servers. Please describe the issue as if we hadn't heard about it before - indeed many of the technicians you worked with in this thread are no longer with the company, and others have come onboard in that time.