Page 1 of 1

Nagios 3.4.1 - problem service notification

Posted: Mon Jul 23, 2012 2:31 am
by dolecek
Hello
I use Nagios 3.4.1 and I have a problem with a notice from certain services. For example, the SSH service (check_ssh) everything is fine. Services have set up so that it sends a notification if the error persists up to 4 controls (max_check_attempts = 4).

The problem I have but HTTP and PING (PING_PO_KLENOVCE).
The HTTP service is unavailable to verify only 2/4. That's will remain "stuck". So will not send notification.
The PING service (PING_PO_KLENOVCE) is verified by the unavailability of only 1/4. That's will remain "stuck". So will not send notification.

Annex "data.zip" send screenshots and config.
http://www.klenovka.cz/data.zip

If Nagios restarted, so the service is 4/4. Notification is not sent but still.
Notifications are sent from the Host without any problems.

Thank you for your help.
Sincerely, Michael Dolecek

Re: Nagios 3.4.1 - problem service notification

Posted: Wed Jul 25, 2012 10:17 am
by dolecek
no one knows?

Re: Nagios 3.4.1 - problem service notification

Posted: Wed Jul 25, 2012 12:55 pm
by agriffin
dolecek wrote:The problem I have but HTTP and PING (PING_PO_KLENOVCE).
The HTTP service is unavailable to verify only 2/4. That's will remain "stuck". So will not send notification.
The PING service (PING_PO_KLENOVCE) is verified by the unavailability of only 1/4. That's will remain "stuck". So will not send notification.
I'm a little unclear about the problem you described. Can you elaborate or rephrase this?

Re: Nagios 3.4.1 - problem service notification

Posted: Fri Jul 27, 2012 12:23 pm
by dolecek
If I set to the nagios service check only 1 and immediately sent a notification and sends it. However, if you set up to check for error as a service 4x and then doesnt sent the notification, so I will not send it. The web interface is seen to remain sown on 2/4. If you restart nagios daemon, so there starts 4/4

Re: Nagios 3.4.1 - problem service notification

Posted: Fri Jul 27, 2012 2:31 pm
by agriffin
I'm still not quite sure what the problem is, but I did notice a few odd things about your service definition. You have passive checks and freshness checking enabled on your service which appears to be a active check. Is there some reason for this? If not, try disabling passive_checks_enabled and check_freshness to see if that helps.

Re: Nagios 3.4.1 - problem service notification

Posted: Sat Jul 28, 2012 9:45 am
by dolecek
Hi, I disabled passive_checks_enabled and check_freshness but it is the same :(
I have set max_check_attempts = 4 If I set max_check_attempts = 1 So everything is OK. But if I set to 4, so nagios check only the 2x in The web interface will remain sown 2/4.
any ideas? :( you understand me now?
I apologize for my English