Re: [Nagios-users] nagios 3.0.5 email notifications fail {Spam?}
Ok, my mistake. I can clearly see that I put all options in notification
template, including "n " from "none" so none of the notifications were sent.
Stupid me!
Thanks all,
Alex
On Tue, Jan 13, 2009 at 10:47 AM, alex alex wrote:
> Hi again.
> 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:
>
> [1231835680.728809] [032.2] [pid=14526] ** Checking host notification
> viability for contact 'user'...
> [1231835680.728838] [032.2] [pid=14526] We shouldn't notify this contact
> about DOWN states.
> [1231835680.728858] [032.0] [pid=14526] No contacts were notified. Next
> possible notification time: Thu Jan 1 02:00:00 1970
> [1231835680.728873] [032.0] [pid=14526] 0 contacts were notified.
>
>
> So it seems that the contacts didn't inherited the template??? were found.
> Again, my configs read:
>
> # contactgroups admins
> define contactgroup {
> contactgroup_name admins
> alias admins
> members nagios,user
> }
> #contact template
> define contact {
> namegeneric_contact
> host_notification_period24din24_7din7
> service_notification_period 24din24_7din7
> host_notification_options d,u,r,n,f
> service_notification_optionsu,c,w,r,n,f
> host_notification_commands notify-host-by-email
> service_notification_commands notify-service-by-email
> register0
> }
> define contact {
> contact_nameuser
> use generic_contact
> alias utilizator_generic
> email s...@localhost
> }
>
> define host {
> host_name host1
> alias host1
> address 192.168.1.1
> use generic_host_tpl
> }
> define host {
> namegeneric_host_tpl
> process_perf_data 1
> retain_status_information 1
> retain_nonstatus_information1
> active_checks_enabled 1
> passive_checks_enabled 1
> check_period24din24_7din7
> obsess_over_host0
> check_freshness 1
> freshness_threshold 0
> check_command is_icmp_alive
> max_check_attempts 1
> event_handler_enabled 0
> notifications_enabled 1
> notification_interval 5
> notification_period 24din24_7din7
> notification_optionsd,u,r,f
> stalking_optionsd,o,u
> register0
> action_url/nagios/pnp/index.php?host=$HOSTNAME$
>
> }
>
>
>
>
>
>
>
>
> On Mon, Jan 12, 2009 at 3:49 PM, Marc Powell wrote:
>
>>
>> On Jan 12, 2009, at 5:44 AM, alex alex wrote:
>> > Notification: FLAPPINGSTOP
>> > Host: host1
>> > State: UP
>> > Or for a service
>>
>> > Notification Type: FLAPPINGSTOP
>> >
>> > Service: is_alive
>> > Host: host1
>> > Is it the right behaviour (to put flapping instead up/down if the
>> > flapping is enabled) ?
>>
>> Yes, if the host or service were in a flapping state, which these
>> were. flapping is different than a normal up/down and that
>> notification type is provided should you want or need to make that
>> distinction. If you'd rather just receive up/down notifications,
>> disable notifications for flapping.
>>
>> > Anyhow, some notifications are sent and that's the main good news. I
>> > think from now only some small changes must be done in my configs to
>> > tune the uinstallation.
>>
>> Good =)
>>
>> --
>> Marc
>>
>>
>>
>> --
>> Check out the new SourceForge.net Marketplace.
>> It is the best place to buy or sell services for
>> just about anything Open Source.
>> http://p.sf.net/sfu/Xq1LFB
>> ___
>> Nagios-users mailing list
>> Nagios-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/nagios-users
>> ::: Please include Nagios version, plugin version (-v) and OS when
>> reporting any issue.
>> ::: Messages without supporting info will risk being sent to /dev/null
>>
>
>
--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version,
Re: [Nagios-users] nagios 3.0.5 email notifications fail {Spam?}
alex alex schrieb:
> Hi again.
> 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:
>
> [1231835680.728809] [032.2] [pid=14526] ** Checking host notification
> viability for contact 'user'...
> [1231835680.728838] [032.2] [pid=14526] We shouldn't notify this contact
> about DOWN states.
> [1231835680.728858] [032.0] [pid=14526] No contacts were notified. Next
> possible notification time: Thu Jan 1 02:00:00 1970
> [1231835680.728873] [032.0] [pid=14526] 0 contacts were notified.
>
>
> So it seems that the contacts didn't inherited the template??? were
> found. Again, my configs read:
>
> # contactgroups admins
> define contactgroup {
> contactgroup_name admins
> alias admins
> members nagios,user
> }
> #contact template
> define contact {
> namegeneric_contact
> host_notification_period24din24_7din7
> service_notification_period 24din24_7din7
> host_notification_options d,u,r,n,f
> service_notification_optionsu,c,w,r,n,f
> host_notification_commands notify-host-by-email
> service_notification_commands notify-service-by-email
> register0
> }
Do you realy want to use "service_notification_options n"?
http://nagios.sourceforge.net/docs/3_0/objectdefinitions.html#contact
If you specify n (none) as an option, the contact will not receive any type of
service notifications.
Cheers Joerg
--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null
Re: [Nagios-users] nagios 3.0.5 email notifications fail {Spam?}
Hi again.
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:
[1231835680.728809] [032.2] [pid=14526] ** Checking host notification
viability for contact 'user'...
[1231835680.728838] [032.2] [pid=14526] We shouldn't notify this contact
about DOWN states.
[1231835680.728858] [032.0] [pid=14526] No contacts were notified. Next
possible notification time: Thu Jan 1 02:00:00 1970
[1231835680.728873] [032.0] [pid=14526] 0 contacts were notified.
So it seems that the contacts didn't inherited the template??? were found.
Again, my configs read:
# contactgroups admins
define contactgroup {
contactgroup_name admins
alias admins
members nagios,user
}
#contact template
define contact {
namegeneric_contact
host_notification_period24din24_7din7
service_notification_period 24din24_7din7
host_notification_options d,u,r,n,f
service_notification_optionsu,c,w,r,n,f
host_notification_commands notify-host-by-email
service_notification_commands notify-service-by-email
register0
}
define contact {
contact_nameuser
use generic_contact
alias utilizator_generic
email s...@localhost
}
define host {
host_name host1
alias host1
address 192.168.1.1
use generic_host_tpl
}
define host {
namegeneric_host_tpl
process_perf_data 1
retain_status_information 1
retain_nonstatus_information1
active_checks_enabled 1
passive_checks_enabled 1
check_period24din24_7din7
obsess_over_host0
check_freshness 1
freshness_threshold 0
check_command is_icmp_alive
max_check_attempts 1
event_handler_enabled 0
notifications_enabled 1
notification_interval 5
notification_period 24din24_7din7
notification_optionsd,u,r,f
stalking_optionsd,o,u
register0
action_url/nagios/pnp/index.php?host=$HOSTNAME$
}
On Mon, Jan 12, 2009 at 3:49 PM, Marc Powell wrote:
>
> On Jan 12, 2009, at 5:44 AM, alex alex wrote:
> > Notification: FLAPPINGSTOP
> > Host: host1
> > State: UP
> > Or for a service
>
> > Notification Type: FLAPPINGSTOP
> >
> > Service: is_alive
> > Host: host1
> > Is it the right behaviour (to put flapping instead up/down if the
> > flapping is enabled) ?
>
> Yes, if the host or service were in a flapping state, which these
> were. flapping is different than a normal up/down and that
> notification type is provided should you want or need to make that
> distinction. If you'd rather just receive up/down notifications,
> disable notifications for flapping.
>
> > Anyhow, some notifications are sent and that's the main good news. I
> > think from now only some small changes must be done in my configs to
> > tune the uinstallation.
>
> Good =)
>
> --
> Marc
>
>
>
> --
> Check out the new SourceForge.net Marketplace.
> It is the best place to buy or sell services for
> just about anything Open Source.
> http://p.sf.net/sfu/Xq1LFB
> ___
> Nagios-users mailing list
> Nagios-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-users
> ::: Please include Nagios version, plugin version (-v) and OS when
> reporting any issue.
> ::: Messages without supporting info will risk being sent to /dev/null
>
--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null
Re: [Nagios-users] nagios 3.0.5 email notifications fail {Spam?}
On Jan 12, 2009, at 5:44 AM, alex alex wrote: > Notification: FLAPPINGSTOP > Host: host1 > State: UP > Or for a service > Notification Type: FLAPPINGSTOP > > Service: is_alive > Host: host1 > Is it the right behaviour (to put flapping instead up/down if the > flapping is enabled) ? Yes, if the host or service were in a flapping state, which these were. flapping is different than a normal up/down and that notification type is provided should you want or need to make that distinction. If you'd rather just receive up/down notifications, disable notifications for flapping. > Anyhow, some notifications are sent and that's the main good news. I > think from now only some small changes must be done in my configs to > tune the uinstallation. Good =) -- Marc -- Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB ___ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
Re: [Nagios-users] nagios 3.0.5 email notifications fail {Spam?}
Hi again,
Yes, there is another template named generic-contact but it's identical to
the generic (excepting the name).
But here's a good news: I have some notifications (finnaly, it seems that
the notification works). And the bad news is that I get only emails like:
"
Return-Path:
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
by localhost.localdomain (8.14.1/8.14.1) with ESMTP id n0CAArp4003801
for ; Mon, 12 Jan 2009 12:10:53 +0200
Received: (from nag...@localhost)
by localhost.localdomain (8.14.1/8.14.1/Submit) id n0CAArxq003799
for nag...@localhost; Mon, 12 Jan 2009 12:10:53 +0200
Date: Mon, 12 Jan 2009 12:10:53 +0200
From: nag...@localhost.localdomain
Message-Id: <200901121010.n0caarxq003...@localhost.localdomain>
To: nag...@localhost.localdomain
Subject: ** $ Host Alert: host1 is UP **
* Nagios *
Notification: FLAPPINGSTOP
Host: host1
State: UP
Address: 172.30.129.67
Info: PING OK - Packet loss = 0%, RTA = 11.74 ms
Date/Time: Sun Jan 11 15:10:11 EET 2009"
Or for a service
"
Subject: ** FLAPPINGSTOP Service Alert: host1/is_alive is OK **
* Nagios *
Notification Type: FLAPPINGSTOP
Service: is_alive
Host: host1
Address: 172.24.14.242
State: OK
Date/Time: Mon Jan 12 12:10:53 EET 2009
Additional Info:
PING OK - Packet loss = 0%, RTA = 131.99 ms
"
Is it the right behaviour (to put flapping instead up/down if the flapping
is enabled) ? The thresholds for flapp are set at 25% and 50%.
Anyhow, some notifications are sent and that's the main good news. I think
from now only some small changes must be done in my configs to tune the
uinstallation.
Thank you again,
Alex
On Sat, Jan 10, 2009 at 1:11 AM, Marc Powell wrote:
>
> On Jan 9, 2009, at 11:26 AM, alex alex wrote:
>
> > Hi again,
> > I've just disabled events handler. I think youwere right. The dead
> > emails were from events handler, not from notifications. No new
> > notifications failed in letter.dead It seems that in event handler,
> > the $CONTACTEMAIL$ is not set.
> > But now, even stranger, no notification is sent. I mean I enabled
> > debug in nagios.cfg and the result is:
> > [1231482452.131909] [032.0] [pid=16674] ** Host Notification Attempt
> > ** Host: 'h
> > ost1', Type: 0, Options: 0, Current State: 1, Last Notification: Thu
> > Jan 1
> > 02:00:00 1970
> > [1231482452.132086] [032.0] [pid=16674] Notification viability test
> > passed.
> > [1231482452.132104] [032.1] [pid=16674] Current notification number:
> > 1 (incremen
> > ted)
> > [1231482452.132127] [032.1] [pid=16674] Host notification will NOT
> > be escalated.
> > [1231482452.132241] [032.1] [pid=16674] Adding normal contacts for
> > host to notif
> > ication list.
> > [1231482452.132504] [032.0] [pid=16674] No contacts were notified.
> > Next possibl
> > e notification time: Thu Jan 1 02:00:00 1970
> > [1231482452.132524] [032.0] [pid=16674] 0 contacts were notified.
> > Now more than ever I don't understand why no contacts were notified!
> > It can mean that normal contacts doesn't exist?
> >
>
> From a previous e-mail --
>
> define contact {
> contact_namenagios
> use generic-contact
> alias nagios
> email nag...@localhost
> }
>
> define contact {
> namegeneric
> host_notification_period24din2_7din7
> service_notification_period 24din2_7din7
> host_notification_options d,u,r,n,f
> service_notification_optionsu,c,w,r,n,f
> host_notification_commands notify-host-by-email
> service_notification_commands notify-service-by-email
> register0
> }
>
> Your contact 'nagios' uses a template named 'generic-contact'. Do the
> host and service_notification_periods in that template include the
> time when the notification above was supposed to go out? The contact
> template you provided is named 'generic' not 'generic-contact' so
> there must be another template that needs to be looked at.
>
> --
> Marc
>
>
>
> --
> Check out the new SourceForge.net Marketplace.
> It is the best place to buy or sell services for
> just about anything Open Source.
> http://p.sf.net/sfu/Xq1LFB
> ___
> Nagios-users mailing list
> Nagios-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-users
> ::: Please include Nagios version, plugin version (-v) and OS when
> reporting any issue.
> ::: Messages without supporting info will risk being sent to /dev/null
>
--
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB_
Re: [Nagios-users] nagios 3.0.5 email notifications fail {Spam?}
On Jan 9, 2009, at 11:26 AM, alex alex wrote:
> Hi again,
> I've just disabled events handler. I think youwere right. The dead
> emails were from events handler, not from notifications. No new
> notifications failed in letter.dead It seems that in event handler,
> the $CONTACTEMAIL$ is not set.
> But now, even stranger, no notification is sent. I mean I enabled
> debug in nagios.cfg and the result is:
> [1231482452.131909] [032.0] [pid=16674] ** Host Notification Attempt
> ** Host: 'h
> ost1', Type: 0, Options: 0, Current State: 1, Last Notification: Thu
> Jan 1
> 02:00:00 1970
> [1231482452.132086] [032.0] [pid=16674] Notification viability test
> passed.
> [1231482452.132104] [032.1] [pid=16674] Current notification number:
> 1 (incremen
> ted)
> [1231482452.132127] [032.1] [pid=16674] Host notification will NOT
> be escalated.
> [1231482452.132241] [032.1] [pid=16674] Adding normal contacts for
> host to notif
> ication list.
> [1231482452.132504] [032.0] [pid=16674] No contacts were notified.
> Next possibl
> e notification time: Thu Jan 1 02:00:00 1970
> [1231482452.132524] [032.0] [pid=16674] 0 contacts were notified.
> Now more than ever I don't understand why no contacts were notified!
> It can mean that normal contacts doesn't exist?
>
From a previous e-mail --
define contact {
contact_namenagios
use generic-contact
alias nagios
email nag...@localhost
}
define contact {
namegeneric
host_notification_period24din2_7din7
service_notification_period 24din2_7din7
host_notification_options d,u,r,n,f
service_notification_optionsu,c,w,r,n,f
host_notification_commands notify-host-by-email
service_notification_commands notify-service-by-email
register0
}
Your contact 'nagios' uses a template named 'generic-contact'. Do the
host and service_notification_periods in that template include the
time when the notification above was supposed to go out? The contact
template you provided is named 'generic' not 'generic-contact' so
there must be another template that needs to be looked at.
--
Marc
--
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null
