Page 4 of 4
Re: CHECK_NRPE: Error - Could not connect to . Check system
Posted: Thu Apr 11, 2019 9:36 am
by anilgupta
however, it is breaking from Nagios Server.
When I pass command without parameter as below, it works.
Code: Select all
[guptaa@cacbigdcapmdw51 ~]$ /usr/local/nagios/libexec/check_nrpe -H 10.92.34.66 -t 30 -c check_cpu_stats
CPU STATISTICS OK : user=0% system=0%, iowait=0%, idle=100%, nice=0.00%, steal=0.00% | CpuUser=0%;70;90;0; CpuSystem=0%;40;60;0; CpuIowait=0%;30;40;0; CpuIdle=100%;0;0;0; CpuNice=0.0%;0;0;0; CpuSteal=0.0%;0;0;0;
Please suggest
Re: CHECK_NRPE: Error - Could not connect to . Check system
Posted: Thu Apr 11, 2019 1:45 pm
by lmiltchev
I would recommend that you upgrade your NRPE agent to v3. Here's our KB article on installing NRPE v3 from source:
https://support.nagios.com/kb/article/n ... e-515.html
Re: CHECK_NRPE: Error - Could not connect to . Check system
Posted: Thu Apr 11, 2019 2:34 pm
by anilgupta
I would recommend that you upgrade your NRPE agent to v3. Here's our KB article on installing NRPE v3 from source:
NRPE upgrade will be done in different phase of this project. In this phase we have planned to use the existing agent.
Please suggest if we can achieve it with the given version.
Secondly, I am getting
Code: Select all
"CRITICAL - 10.92.34.66: rta nan, lost 100%"
for my host status.
How does "Host Status" work, meaning does it use specific port to get the status?
Re: CHECK_NRPE: Error - Could not connect to . Check system
Posted: Thu Apr 11, 2019 3:38 pm
by npolovenko
@anilgupta , In this case, I'd recommend hardcoding arguments in the nrpe.cfg file itself. Your nrpe agent version is old and was likely compiled without the functionality of accepting arguments. In the future, you should consider upgrading the agent as
@lmiltchev recommended.
Re: CHECK_NRPE: Error - Could not connect to . Check system
Posted: Thu Apr 11, 2019 3:41 pm
by anilgupta
@anilgupta , In this case, I'd recommend hardcoding arguments in the nrpe.cfg file itself. Your nrpe agent version is old and was likely compiled without the functionality of accepting arguments. In the future, you should consider upgrading the agent as @lmiltchev recommended.
I will do. Thanks
Secondly, I am getting
CODE: SELECT ALL
"CRITICAL - 10.92.34.66: rta nan, lost 100%"
for my host status.
How does "Host Status" work, meaning does it use specific port to get the status?
Can you please comment on below host status?
Re: CHECK_NRPE: Error - Could not connect to . Check system
Posted: Thu Apr 11, 2019 3:46 pm
by npolovenko
@anilgupta, Host status check is using ping(icmp). Are you able to ping the Solaris server(10.92.34.66) from the Nagios XI server? It says there's 100% packet loss. Make sure that the monitored host is ICMP(ping) discoverable and that there are no network issues.