Re: [Nagios-devel] several host notifications for 1 host
Posted: Thu May 24, 2007 3:03 am
Hi guys,
after spending some ours in the code I have to tell: "It works as designed".
The Host Notification we are all seeing are _not_ from the scheduled
neither of the on-demand host checks.
Initiated by the service checks for a host nagios takes per default the
last known host state to determine to send a host or a service notification.
The last known Host check result after service check of your "DB server
egal" was the "soft down" from the last host-check.
If you want Nagios to execute a real host check after a non-OK service
check you should use the config option:
use_aggressive_host_checking=1
Kind regards,
Hendrik
Markus Blum schrieb:
> Hello,
>
> i get several notifications after a host went down even notification_interval is defined as 0. It seems to be related to service checks on these host because other hosts, without service checks, work fine. I know service checks will cause a host check but even then there shouldn't be a notification before the host check returns a hard state, right ?
>
> Here are the important parts of a log.
>
> [22-05-2007 15:02:35] HOST NOTIFICATION: mblum;server;DOWN;host-notify-by-email;(Host Check Timed Out)
> [22-05-2007 15:02:35] HOST ALERT: server;DOWN;HARD;10;(Host Check Timed Out)
> [22-05-2007 15:01:50] HOST ALERT: server;DOWN;SOFT;9;(Host Check Timed Out)
> [22-05-2007 15:01:35] HOST NOTIFICATION: mblum;server;DOWN;host-notify-by-email;(Host Check Timed Out)
> [22-05-2007 15:01:10] HOST ALERT: server;DOWN;SOFT;8;(Host Check Timed Out)
> [22-05-2007 15:00:25] HOST ALERT: server;DOWN;SOFT;7;(Host Check Timed Out)
> 22-05-2007 14:59:40] HOST ALERT: server;DOWN;SOFT;6;(Host Check Timed Out)
> [22-05-2007 14:59:35] HOST NOTIFICATION: mblum;server;DOWN;host-notify-by-email;(Host Check Timed Out)
> [22-05-2007 14:58:55] HOST ALERT: server;DOWN;SOFT;5;(Host Check Timed Out)
> [22-05-2007 14:58:15] HOST ALERT: server;DOWN;SOFT;4;(Host Check Timed Out)
> [22-05-2007 14:57:35] SERVICE ALERT: server;DB server test egal;CRITICAL;HARD;1;(Service Check Timed Out)
> [22-05-2007 14:57:35] SERVICE ALERT: server; DB server egal;CRITICAL;HARD;1;(Service Check Timed Out)
> [22-05-2007 14:57:35] HOST NOTIFICATION: mblum;server;DOWN;host-notify-by-email;(Host Check Timed Out)
> [22-05-2007 14:57:30] HOST ALERT: server;DOWN;SOFT;3;(Host Check Timed Out)
> [22-05-2007 14:56:50] HOST ALERT: server;DOWN;SOFT;2;(Host Check Timed Out)
> [22-05-2007 14:56:10] HOST ALERT: server;DOWN;SOFT;1;(Host Check Timed Out)
>
>
> The notification at [22-05-2007 15:02:35] is right because after 10 checks the host check went into a hard state. But the ones before are a mystery for me. If its just a problem of misconfiguration i am sorry for posting here and thanks for a hint to fix this problem.
>
>
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]
after spending some ours in the code I have to tell: "It works as designed".
The Host Notification we are all seeing are _not_ from the scheduled
neither of the on-demand host checks.
Initiated by the service checks for a host nagios takes per default the
last known host state to determine to send a host or a service notification.
The last known Host check result after service check of your "DB server
egal" was the "soft down" from the last host-check.
If you want Nagios to execute a real host check after a non-OK service
check you should use the config option:
use_aggressive_host_checking=1
Kind regards,
Hendrik
Markus Blum schrieb:
> Hello,
>
> i get several notifications after a host went down even notification_interval is defined as 0. It seems to be related to service checks on these host because other hosts, without service checks, work fine. I know service checks will cause a host check but even then there shouldn't be a notification before the host check returns a hard state, right ?
>
> Here are the important parts of a log.
>
> [22-05-2007 15:02:35] HOST NOTIFICATION: mblum;server;DOWN;host-notify-by-email;(Host Check Timed Out)
> [22-05-2007 15:02:35] HOST ALERT: server;DOWN;HARD;10;(Host Check Timed Out)
> [22-05-2007 15:01:50] HOST ALERT: server;DOWN;SOFT;9;(Host Check Timed Out)
> [22-05-2007 15:01:35] HOST NOTIFICATION: mblum;server;DOWN;host-notify-by-email;(Host Check Timed Out)
> [22-05-2007 15:01:10] HOST ALERT: server;DOWN;SOFT;8;(Host Check Timed Out)
> [22-05-2007 15:00:25] HOST ALERT: server;DOWN;SOFT;7;(Host Check Timed Out)
> 22-05-2007 14:59:40] HOST ALERT: server;DOWN;SOFT;6;(Host Check Timed Out)
> [22-05-2007 14:59:35] HOST NOTIFICATION: mblum;server;DOWN;host-notify-by-email;(Host Check Timed Out)
> [22-05-2007 14:58:55] HOST ALERT: server;DOWN;SOFT;5;(Host Check Timed Out)
> [22-05-2007 14:58:15] HOST ALERT: server;DOWN;SOFT;4;(Host Check Timed Out)
> [22-05-2007 14:57:35] SERVICE ALERT: server;DB server test egal;CRITICAL;HARD;1;(Service Check Timed Out)
> [22-05-2007 14:57:35] SERVICE ALERT: server; DB server egal;CRITICAL;HARD;1;(Service Check Timed Out)
> [22-05-2007 14:57:35] HOST NOTIFICATION: mblum;server;DOWN;host-notify-by-email;(Host Check Timed Out)
> [22-05-2007 14:57:30] HOST ALERT: server;DOWN;SOFT;3;(Host Check Timed Out)
> [22-05-2007 14:56:50] HOST ALERT: server;DOWN;SOFT;2;(Host Check Timed Out)
> [22-05-2007 14:56:10] HOST ALERT: server;DOWN;SOFT;1;(Host Check Timed Out)
>
>
> The notification at [22-05-2007 15:02:35] is right because after 10 checks the host check went into a hard state. But the ones before are a mystery for me. If its just a problem of misconfiguration i am sorry for posting here and thanks for a hint to fix this problem.
>
>
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]