Hi 00_kl250,
The -t option is the timeout, i.e. the number of seconds to wait before the connection times out.
I set mine to 30, I'm not entirely sure why I chose that number (I think I was having some latency issues in my network), but the default value is 10.
Kind Regards,
Gary Shergill
Nagios/NRPE Return code 127 error
-
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Nagios/NRPE Return code 127 error
spot on gshergill!
Re: Nagios/NRPE Return code 127 error
Here's another question for you.
It seems like it's not actively monitoring. I stopped the apache service on the client and the nagios server did not detect that no apache services were running until I did a force check. Is there a way to make sure it's monitoring(or checking in) every minute?
Thanks for all your help!
It seems like it's not actively monitoring. I stopped the apache service on the client and the nagios server did not detect that no apache services were running until I did a force check. Is there a way to make sure it's monitoring(or checking in) every minute?
Thanks for all your help!
Re: Nagios/NRPE Return code 127 error
Hi 00_kl250,
By default I think Nagios checks a service every 10 minutes.
In the service.cfg you can add the following to the service;
Kind Regards,
Gary Shergill
By default I think Nagios checks a service every 10 minutes.
In the service.cfg you can add the following to the service;
Code: Select all
check_interval 1
Gary Shergill
Re: Nagios/NRPE Return code 127 error
Thanks, got it all working. Appreciate your help gshergill and SLANSING.
-
- Posts: 7698
- Joined: Mon Apr 23, 2012 4:28 pm
- Location: Travelling through time and space...
Re: Nagios/NRPE Return code 127 error
Let us know if you need additional help!