Nagios Support Forum

i am stuck. the status show "CHECK_NRPE : Error - Could not complete SSH handshake."

Thanks @nozlaf! Let us know if that helps. Alternatively, here's the link to our exchange which has a few more results returned for 'client cert' - https://exchange.nagios.org/index.php?option=com_mtree&task=search&Itemid=74&searchword=client%20cert thanks nozlaf & rkennedy. i faile...

Hi,
Yes, you may close this ticket since the problem has resolved.

Image

http://tinypic.com/r/ivzp0p/9

Hi,

Has anyone try to monitor / have script to monitor base64 certificate ?
normally in .cer or .crt format.
I would like to monitor the certificate expiry date.

note: it is not SSL certificate. It is a end user certificate.

regards,

Can you show us the notification. Can you provide the host and service definitions. Thanks Box293. You just give me an idea. I found this in contacts.cfg and made necessary changes. define contact{ contact_name nagiosemail alias Nagios eMail service_notification_period 24x7 host_notification_period...

notification history xxxx D:\ Drive Space WARNING 03-14-2016 09:19:49 nagiosemail notify-host-by-email d:\ - total: 60.00 Gb - used: 55.32 Gb (92%) - free 4.68 Gb (8%) xxxx D:\ Drive Space WARNING 03-14-2016 09:19:49 nagiosadmin notify-host-by-email d:\ - total: 60.00 Gb - used: 55.32 Gb (92%) - fre...

Hi,

We've a scenario where nagios only send host alert notification instead of service alert.
one sample is when we monitor free space and suddenly it reached the threshold limit, it send the host problem notification.
but it is actually service related issue.

regards,

rkennedy wrote:It was most likely a permissions issue that had to do with SELinux.

Can you please clarify what you mean by no matching directoryindex is logged? Show us a screenshot?

please find below the screen shot for your review.
https://support.nagios.com/forum/downlo ... w&id=12704

surprisingly, the problem resolved without doing any changes but still the no matching directoryindex is still logged.

on top of that i did run setenforce 0 and stop iptables service, when the problem occurred.