Nagios Support Forum

I'm looking at migrating some of my AWS EC2 instances to use Graviton (arm64) instance types. Since NCPA is only available via RPM repo in x86-64, I'm trying to build from scratch. This is specifically on Amazon Linux 2023. I've installed all of the prerequisites manually: $ sudo yum install python3...

You can see above that it is already set to 60:

> ./nagios.cfg:service_check_timeout=60

Whoops, I just realized that you might have meant the server being monitored -- seeing as how you suggested looking at nrpe.cfg. I only have /etc/nagios/nrpe.cfg -- no other configuration files on the server. $ grep _timeout nrpe.cfg command_timeout=60 connection_timeout=300 So the 10-second timeout...

This is all I have: $ grep _timeout `find . -type f` ./conf.d/my_vpn_host.cfg: command_name check_nrpe_with_timeout ./conf.d/my_vpn_host.cfg: check_command check_nrpe_with_timeout!check_VPN_client_name!30 ./nagios.cfg:service_check_timeout=60 ./nagios.cfg:host_check_timeout=30 ./nagios.cfg:event_han...

It /was/ working for a while. I have tried increasing the timeout, but I may be doing it incorrectly: define command { command_name check_nrpe_with_timeout command_line $USER1$/check_nrpe -H $HOSTADDRESS$ -c $ARG1$ -t $ARG2$ } define service { use local-service host_name hostname service_description...

Yes, I'm using check_ping from the remote host because I have to check to see whether a VPN tunnel is available from that host. I can't check it from anywhere else.

Today I saw that one of my services was giving an error with the message: "CHECK_NRPE: Socket timeout after 10 seconds." I figured the service was down so I started checking. The service was up, so Nagios was making a mistake. So I went to the command line on the Nagios server (the one mak...