Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
/usr/local/nagios/libexec/check_nrpe -V
NRPE Plugin for Nagios
Copyright (c) 1999-2008 Ethan Galstad (nagios@nagios.org)
Version: 3.0.1
Last Modified: 09-08-2016
License: GPL v2 with exemptions (-l for more info)
SSL/TLS Available: OpenSSL 0.9.6 or higher required
I have looked into this more and it seems to be an issue with AWS Linux AMI. This instance has an old Linux and kernel, which is not compatible with NRPE version 3.x. The installation failed and nrpe config files weren't working. It didn't recognize nrpe as a and installed service on the system.
So, I installed NRPE v2.15 and I forced version 2 packet only. Now it works and doesn't generate any errors.
I'm not sure if there is any other workaround or fix for the NRPE version 3.x on Amazon Linux but this seems to work for now...
When you compiled the version 3 of the NRPE Agent on the remote host, did you receive any errors?
How old is that system, what OS and release is it running?
Be sure to check out our Knowledgebase for helpful articles and solutions!
tgriep wrote:When you compiled the version 3 of the NRPE Agent on the remote host, did you receive any errors?
How old is that system, what OS and release is it running?
No, I didn't get any errors. I wasn't able to start nrpe at all.
1)NRPE [b]wasn't [/b]listening on TCP port 5666
2)NRPE [b]wasn't [/b]able to run or start
3)If you run: sudo service -status-all ---> NRPE is not registered as a service
4)If you run service nrpe start, you get---> nrpe: unrecognized service
5)nrpe.conf exists under /etc/init/nrpe.conf, but unable to start nrpe
1)Amazon LInux uses an old version of upstart that, for some reason, doesn’t like the nrpe.conf file
2)The log files complain about:
-[i]/etc/init.conf: unable to load configuration: No such file or directory[/i]
-[i]/etc/init/nrpe.conf:10 Illegal oom adjustment, expected -16 to 15 or never[/i]
Type sudo make install-daemon-config
make: *** No rule to make target `install-daemon-config'. Stop.
sudo make install-xinetd
make: *** No rule to make target `install-xinetd'. Stop.
sudo make
Please enter make [option] where [option] is one of:
all builds nrpe and check_nrpe
nrpe builds nrpe only
check_nrpe builds check_nrpe only
install-groups-users add the users and groups if they do not exist
install install nrpe and check_nrpe
install-plugin install the check_nrpe plugin
install-daemon install the nrpe daemon
install-config install the nrpe configuration file
install-inetd install the startup files for inetd, launchd, etc.
install-init install the startup files for init, systemd, etc.
step by step and still the service is not registered. I manually added the service to /etc/services and when I run
sudo cat /etc/*lease
NAME="Amazon Linux AMI"
VERSION="2015.03"
ID="amzn"
ID_LIKE="rhel fedora"
VERSION_ID="2015.03"
PRETTY_NAME="Amazon Linux AMI 2015.03"
ANSI_COLOR="0;33"
CPE_NAME="cpe:/o:amazon:linux:2015.03:ga"
HOME_URL="http://aws.amazon.com/amazon-linux-ami/"
Amazon Linux AMI release 2015.03
Is there any limitation with nrpe V3 on this Linux? Should I just go with the old backage for Amazon Linux provided here: https://gist.github.com/cbschuld/7476829 ?
[ec2-user@ip-xx-xx-xx-xx init]$ sudo chkconfig nrpe on
error reading information on service nrpe: No such file or directory
[ec2-user@ip-xx-xx-xx-xx init]$ sudo service nrpe start
nrpe: unrecognized service
Instead of it running under xinetd, it will run as a daemon.
Let us know what you find.