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.
It's probably best to start a new thread if the alert did not work properly. However, I think the alert did work, you only got connection refused, which didn't seem appropriate to you. Is that correct?
If the server/application did go down, connection refused doesn't sound odd at all to me, but maybe I am misunderstanding the situation. Maybe you could explain a bit more about the actual alert in the other thread, if you feel it is warranted.
A couple of other things to check on for the intermittent issue for your checks is is network outages, if you have any firewalls that are blocking the Nagios system temporarily.
Do you see any errors in the logs of the web site you are checking?
Be sure to check out our Knowledgebase for helpful articles and solutions!
So it registers the hit on the apache log on the box being checked, but nagios says 'connection refused' and fires an alert.
I have no idea why as this is checked every ten minutes, all day every day.
It could be that the check is on the edge of the timeout setting that the check_http plugin has and it is causing the connection / timeout intermittent issues.
Try increasing the timeout to 59 seconds for your check_http command by adding the following option to it.
Is it possible to send a passive check? I know it's not an ideal solution, but it seems like if other people were getting false positive notifications we'd know about it.
Of course, waiting to hear back about the -t 59 too!