Nagios Support Forum

Just to recap. You need to do 3 things: 1. Verify that service_check_timeout in the nagios.cfg on your nagios server is set high enough: grep service_check_timeout /usr/local/nagios/etc/nagios.cfg NOTE: Remember to restart nagios after any changes to nagios.cfg. 2. Add "-t" to the check_n...

Here's a snapshot:

Thanks, tried that but no luck.

Ok, so the service definition it is: define service{ use generic-service host_name cassandratest,cassandratest2 service_description Cassandra Monitoring check_command check_nrpe!check_cassandra } Perhaps I need to add the -t here? Also, the nrpe.cfg file on the remote client has the following settin...

Here's the check_nrpe definition:

define command{
command_name check_nrpe
command_line $USER1$/check_nrpe -H $HOSTADDRESS$ -c $ARG1$ -t 30
}


service definition:

command[check_cassandra]=HOME=~nagios /usr/local/nagios/libexec/check_cassandra_cluster.sh

I'm running 2.15, and when I run the command and add -t 20 at the end it does in fact run correctly without timing out. Just doesn't seem to want to do it when I add the -t value to the check_nrpe command definition in the commands.cfg

So I have a remote check that needs to be run, and it takes longer than 10 seconds to run, and as such I keep getting "Socket timeout after 10 seconds". That's fine, so I went and added "-t 30" to the commands.cfg file (for the NRPE command), and verified in the nrpe.cfg file on ...

WOOHOO got it working!!! :lol: path environment was not loaded BINGO! I had kinda abandoned/forgotten about this for a while, but this morning I was troubleshooting a cron job that wouldn't run on Cassandra when I realized the issue was that it didn't have the necessary environment set to successful...

ssax wrote:I haven't seen anyone ask if you have selinux enabled:

Code: Select all

getenforce

or

Code: Select all

sestatus

In this test instance I have selinux set to permissive and iptables is stopped and set to off.

I would double check that with your clean system that you compiled using --enable-command-args Yep this has been verified, I can run other plugins w/args just fine remotely via NRPE, such as "check_users" Now I know this is probably another typo but I'm going to point it out: Yep another ...