Re: [Nagios-users] Nagios 3.99.95 contact_groups
So, I think I just found the issue you're experiencing (though I failed
to mention you in the commit message, sorry) - see the patches I sent
out to nagios-devel the other minute.
On 2012-11-28 23:56, Supporto Tecnico - Crazy Network wrote:
no one have any hint on my issue?
Il 20/11/2012 15:01, Supporto Tecnico - Crazy Network ha scritto:
Hi,
i did update Nagios to this alpha release for test purpose using working
configurations (on Nagios 3.4.1).
The only big trouble im having is that i dont receive any notification.
Here contacts.cfg
define contact{
namecn-contacts
service_notification_period 24x7
host_notification_period24x7
service_notification_optionsc,r
host_notification_options d,u,r
service_notification_commands notify-service-by-email
host_notification_commands notify-host-by-email
register0
}
define contact{
contact_nameandrea.iannucci
use cn-contacts
alias Andrea Iannucci
email supp...@crazynetwork.it
contact_groups crazynetwork.it
service_notification_commands
notify-service-by-email,notify-service-by-sms
host_notification_commands
notify-host-by-email,notify-host-by-sms
pager *
}
define contactgroup{
contactgroup_name crazynetwork.it
alias CrazyNetwork.it Staff
}
I did try to use contactgroups and contact_groups in contact definition
I did try to add members andrea.iannucci in contactgroup definition
The error on debug_level=32 i can see is that for group crazynetwork.it
he cant fine any member (in any case).
Setting contacts instead of contact_groups to services definition make
notification work.
Here debug output:
[1353420007.497082] [032.0] [pid=14604] ** Service Notification Attempt
** Host: 'Test.CrazyNetwork.it', Service: 'MySQL', Type: 0, Options: 0,
Current State: 0, Last Notification: Thu Jan 1 01:00:00 1970
[1353420007.497154] [032.0] [pid=14604] Notification viability test passed.
[1353420007.497181] [032.1] [pid=14604] Current notification number: 2
(incremented)
[1353420007.497195] [032.2] [pid=14604] Creating list of contacts to be
notified.
[1353420007.497206] [032.1] [pid=14604] Service notification will NOT be
escalated.
[1353420007.497217] [032.1] [pid=14604] Adding normal contacts for
service to notification list.
[1353420007.497233] [032.2] [pid=14604] Adding members of contact group
'crazynetwork.it' for service to notification list.
[1353420007.497245] [032.0] [pid=14604] No contacts were found for
notification purposes. No notification was sent out.
Hope someone can help me fix this cause on older version was working at
actually it look like a bug to me.
Thanks
--
Keep yourself connected to Go Parallel:
VERIFY Test and improve your parallel project with help from experts
and peers. http://goparallel.sourceforge.net
___
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.99.95 contact_groups
Hi Crazy Network,
Using bleeding edge code, I've tried copying your contacts.cfg (with my
own email instead), put crazynetwork.it as the contact_group for a
service, and I do receive notifications for it. So there must be
something else at play here that affects you.
What does your services/hosts look like?
On 2012-11-20 15:01, Supporto Tecnico - Crazy Network wrote:
Hi,
i did update Nagios to this alpha release for test purpose using working
configurations (on Nagios 3.4.1).
The only big trouble im having is that i dont receive any notification.
Here contacts.cfg
define contact{
namecn-contacts
service_notification_period 24x7
host_notification_period24x7
service_notification_optionsc,r
host_notification_options d,u,r
service_notification_commands notify-service-by-email
host_notification_commands notify-host-by-email
register0
}
define contact{
contact_nameandrea.iannucci
use cn-contacts
alias Andrea Iannucci
email supp...@crazynetwork.it
contact_groups crazynetwork.it
service_notification_commands
notify-service-by-email,notify-service-by-sms
host_notification_commands
notify-host-by-email,notify-host-by-sms
pager *
}
define contactgroup{
contactgroup_name crazynetwork.it
alias CrazyNetwork.it Staff
}
I did try to use contactgroups and contact_groups in contact definition
I did try to add members andrea.iannucci in contactgroup definition
The error on debug_level=32 i can see is that for group crazynetwork.it
he cant fine any member (in any case).
Setting contacts instead of contact_groups to services definition make
notification work.
Here debug output:
[1353420007.497082] [032.0] [pid=14604] ** Service Notification Attempt
** Host: 'Test.CrazyNetwork.it', Service: 'MySQL', Type: 0, Options: 0,
Current State: 0, Last Notification: Thu Jan 1 01:00:00 1970
[1353420007.497154] [032.0] [pid=14604] Notification viability test passed.
[1353420007.497181] [032.1] [pid=14604] Current notification number: 2
(incremented)
[1353420007.497195] [032.2] [pid=14604] Creating list of contacts to be
notified.
[1353420007.497206] [032.1] [pid=14604] Service notification will NOT be
escalated.
[1353420007.497217] [032.1] [pid=14604] Adding normal contacts for
service to notification list.
[1353420007.497233] [032.2] [pid=14604] Adding members of contact group
'crazynetwork.it' for service to notification list.
[1353420007.497245] [032.0] [pid=14604] No contacts were found for
notification purposes. No notification was sent out.
Hope someone can help me fix this cause on older version was working at
actually it look like a bug to me.
Thanks
--
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
___
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
