CHECK_NRPE: Error - Could not complete SSL handshake
Posted: Fri Mar 23, 2012 11:55 am
I am using NRPE_NT client on a windows server machine to monitor all windows hosts in my enviornment. I am using CHECK_NRPE on nagios XI to monitor windows hosts using the NRPE_NT on this server.
The setup works fine. I have around 320 hosts monitored using this this way with 3 service check each host (total 950) with 10 min frequency.
Monitor used to fail once in a while with following errors. After bouncing the nrpe_nt service, and restarting nagios process on nagios XI server, the errors used to go away.
Mostly these errors appear for many monitors together and do not stick to specific monitors. For example, you would see 10 monitors failed with the same error at exact same time (e.g. 5:06 AM) and in next run after 10 min they will return to OK state. Then after some time another bunch of monitors would fail with same pattern and will clear in next run.
It gives a feeling that some sort of bottlenect happens every time we see those failures, which releases eventually and monitor returns to good state.
Thanks
Ashish
The setup works fine. I have around 320 hosts monitored using this this way with 3 service check each host (total 950) with 10 min frequency.
Monitor used to fail once in a while with following errors. After bouncing the nrpe_nt service, and restarting nagios process on nagios XI server, the errors used to go away.
CHECK_NRPE: Error - Could not complete SSL handshake.
Now these errors has become very frequent and do not go away even after bounce. Please let me know what additional details you need to further look into it.Connection refused or timed out
Mostly these errors appear for many monitors together and do not stick to specific monitors. For example, you would see 10 monitors failed with the same error at exact same time (e.g. 5:06 AM) and in next run after 10 min they will return to OK state. Then after some time another bunch of monitors would fail with same pattern and will clear in next run.
It gives a feeling that some sort of bottlenect happens every time we see those failures, which releases eventually and monitor returns to good state.
Thanks
Ashish