Nagios 3.99.95 contact_groups

[Supporto Tecnico - Crazy Network]

Thanks a lot :)

Just two questions:

1 - Where i can find the patch you menthioned?
2 - I will get latest (patched) version with git clone from repository?

Tomorrow i'll grep latest git repo and try to recompile and test

Thanks

Il 29/11/2012 18:59, Robin Sonefors ha scritto:
> 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{
>>>            name                            cn-contacts
>>>            service_notification_period     24x7
>>>            host_notification_period        24x7
>>>            service_notification_options    c,r
>>>            host_notification_options       d,u,r
>>>            service_notification_commands   notify-service-by-email
>>>            host_notification_commands      notify-host-by-email
>>>            register                        0
>>> }
>>>
>>> define contact{
>>>            contact_name                    andrea.iannucci
>>>            use                             cn-contacts
>>>            alias                           Andrea Iannucci
>>>            email                           support at 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
>>
>>
>
>


-- 

Andrea Iannucci
-------------------------------

-------------------------------
Crazy Network di Iannucci Andrea
Viale G.B. Lulli, 24
00050 Cerveteri - RM
(w) www.crazynetwork.it
(e) andrea.iannucci at crazynetwork.it
(t) +39 06 62279876
(f) +39 06 62298767
(m) +39 338 8552885
-------------------------------------------------------------------------------
Please consider our enviromental responsability before printing this 
E-Mail. Thank you.
-------------------------------------------------------------------------------
Questo messaggio di posta elettronica contiene informazioni di carattere 
confidenziale rivolte esclusivamente al destinatario sopra indicato.
E' vietato l'uso, la diffusione, distribuzione o riproduzione da parte 
di ogni altra persona. Nel caso aveste ricevuto questo messaggio di 
posta elettronica per errore, siete pregati di segnalarlo immediatamente 
al mittente e distruggere quanto ricevuto (compresi i file allegati) 
senza farne copia.
Qualsivoglia utilizzo non autorizzato del contenuto di questo messaggio 
costituisce violazione dell'obbligo di non prendere cognizione della 
corrispondenza tra altri soggetti, salvo più grave illecito, ed espone 
il responsabile alle relative conseguenze.
--------------------------------------------------------------------------------
This e-mail is confidential and may also contain privileged information. 
If you are not the intended recipient you are not authorised to read, 
print, save, process or disclose this message. If you have received this 
message by mistake, please inform the sender immediately and delete this 
e-mail, its attachments and any copies.
Any use, distribution, reproduction or disclosure by any person other 
than the intended recipient is strictly prohibited and the person 
responsible may incur penalties.
-------------------------------------------------------------------------------- 



------------------------------------------------------------------------------
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 at 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