Hi again.<br>I have bad news(for me,at least). I remove the flap announcements and notifications are not working. Here's the debug log for nagios:<br><br>[1231835680.728809] [032.2] [pid=14526] ** Checking host notification viability for contact 'user'...<br>
[1231835680.728838] [032.2] [pid=14526] We shouldn't notify this contact about DOWN states.<br>[1231835680.728858] [032.0] [pid=14526] No contacts were notified. Next possible notification time: Thu Jan 1 02:00:00 1970<br>
[1231835680.728873] [032.0] [pid=14526] 0 contacts were notified.<br><br><br>So it seems that the contacts didn't inherited the template??? were found. Again, my configs read:<br><br>
# contactgroups admins<br>define contactgroup {<br> contactgroup_name admins<br> alias admins<br> members nagios,user<br>}<br>#contact template<br>
define contact {<br> name generic_contact<br> host_notification_period 24din24_7din7<br> service_notification_period 24din24_7din7<br> host_notification_options d,u,r,n,f<br>
service_notification_options u,c,w,r,n,f<br> host_notification_commands notify-host-by-email<br> service_notification_commands notify-service-by-email<br> register 0<br>
}<br>define contact {<br> contact_name user<br> use generic_contact<br> alias utilizator_generic<br> email &nbs
p; smo@localhost<br>
}<br><br>define host {<br> host_name host1<br> alias host1<br> address 192.168.1.1<br> use &n
bsp; generic_host_tpl<br>
}<br>define host {<br> name generic_host_tpl<br> process_perf_data 1<br> retain_status_information 1<br> retain_nonstatus_information 1<br> active_checks_enabled 1<br>
passive_checks_enabled 1<br> check_period 24din24_7din7<br> obsess_over_host 0<br> check_freshness 1<br> freshness_threshold 0<br>
check_command is_icmp_alive<br> max_check_attempts 1<br> event_handler_enabled 0<br> notifications_enabled 1<br> notification_interval 5<br>
notification_period 24din24_7din7<br> notification_options d,u,r,f<br> stalking_options d,o,u<br> register 0<br> action_url /nagios/pnp/index.php?host=$HOSTN
AME$<br>
}<br><br><br><br><br><br><br><br><br><div class="gmail_quote">On Mon, Jan 12, 2009 at 3:49 PM, Marc Powell <span dir="ltr"><<a href="mailto:marc@ena.com" target="_blank">marc@ena.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><br>
On Jan 12, 2009, at 5:44 AM, alex alex wrote:<br>
> Notification: FLAPPINGSTOP<br>
> Host: host1<br>
> State: UP<br>
</div>> Or for a service<br>
<div><br>
> Notification Type: FLAPPINGSTOP<br>
><br>
> Service: is_alive<br>
> Host: host1<br>
</div><div>> Is it the right behaviour (to put flapping instead up/down if the<br>
> flapping is enabled) ?<br>
<br>
</div>Yes, if the host or service were in a flapping state, which these<br>
were. flapping is different than a normal up/down and that<br>
notification type is provided should you want or need to make that<br>
distinction. If you'd rather just receive up/down notifications,<br>
disable notifications for flapping.<br>
<div><br>
> Anyhow, some notifications are sent and that's the main good news. I<br>
> think from now only some small changes must be done in my configs to<br>
> tune the uinstallation.<br>
<br>
</div>Good =)<br>
<div><div></div><div><br>
--<br>
Marc<br>
<br>
<br>
------------------------------------------------------------------------------<br>
Check out the new SourceForge.net Marketplace.<br>
It is the best place to buy or sell services for<br>
just about anything Open Source.<br>
<a href="http://p.sf.net/sfu/Xq1LFB" target="_blank">http://p.sf.net/sfu/Xq1LFB</a><br>
_______________________________________________<br>
Nagios-users mailing list<br>
<a href="mailto:Nagios-users@lists.sourceforge.net" target="_blank">Nagios-users@lists.sourceforge.net</a><br>
<a href="https://lists.sourceforge.net/lists/listinfo/nagios-users" target="_blank">https://lists.sourceforge.net/lists/listinfo/nagios-users</a><br>
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue.<br>
::: Messages without supporting info will risk being sent to /dev/null<br>
</div></div></blockquote></div><br>