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.
mbellerue
Posts: 1403 Joined: Fri Jul 12, 2019 11:10 am
Post
by mbellerue » Tue Jan 07, 2020 11:22 am
If you don't already have a check_ncpa command defined in commands.cfg, that will be pretty easy to take care of. I would recommend something like this.
Code: Select all
define command {
command_name check_ncpa
command_line $USER1$/check_ncpa.py -H $HOSTADDRESS$ -t $ARG1$ -M $ARG2$ -a $ARG3$
}
For your service definition, your check_command will look something like this,
Code: Select all
check_command check_ncpa!ASecretToken!plugins/check_ping!'-H <internal_IP> -w 70,2% -c 80,5%'
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new
Privacy Policy .
Be sure to check out our
Knowledgebase for helpful articles and solutions!
mbellerue
Posts: 1403 Joined: Fri Jul 12, 2019 11:10 am
Post
by mbellerue » Tue Jan 07, 2020 2:33 pm
Can you post your check_ncpa command definition from commands.cfg? I think the issue may be there.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new
Privacy Policy .
Be sure to check out our
Knowledgebase for helpful articles and solutions!
epixelitsupport
Posts: 85 Joined: Fri Nov 08, 2019 2:40 am
Post
by epixelitsupport » Tue Jan 07, 2020 2:38 pm
here it is
define command {
command_name check_ncpa
command_line $USER1$/check_ncpa.py -H $HOSTADDRESS$ $ARG1$
}
mbellerue
Posts: 1403 Joined: Fri Jul 12, 2019 11:10 am
Post
by mbellerue » Tue Jan 07, 2020 2:47 pm
Ah, there it is. It's only expecting 1 argument, and we're passing 3. Change it to this, and we should be good to go.
Code: Select all
command_line $USER1$/check_ncpa.py -H $HOSTADDRESS$ -t $ARG1$ -M $ARG2$ -a $ARG3$
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new
Privacy Policy .
Be sure to check out our
Knowledgebase for helpful articles and solutions!
mbellerue
Posts: 1403 Joined: Fri Jul 12, 2019 11:10 am
Post
by mbellerue » Tue Jan 07, 2020 2:57 pm
That's progress though. That error message 'Incorrect credentials given' means that Nagios actually reached out to NCPA on the remote machine. So now go into your service definition and verify that your token is correct.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new
Privacy Policy .
Be sure to check out our
Knowledgebase for helpful articles and solutions!
mbellerue
Posts: 1403 Joined: Fri Jul 12, 2019 11:10 am
Post
by mbellerue » Tue Jan 07, 2020 3:14 pm
It will work, once you verify that your token is correct. Because right now, NCPA is saying that it doesn't recognize the token that you gave it.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new
Privacy Policy .
Be sure to check out our
Knowledgebase for helpful articles and solutions!