Global escalation service problem

Yohann DESQUERRE (DSI NOISIEL) yohann.desquerre at anpe.fr
Wed Mar 31 17:53:08 CEST 2004


Thanks,



In fact I would like to known the best practice to have the less escalation definition as possible



Regards,







-----Message d'origine-----
De : Spencer L Horn [mailto:shorn at lssi.net] 
Envoyé : mercredi 31 mars 2004 16:01
À : Yohann DESQUERRE (DSI NOISIEL)
Cc : nagios-users at lists.sourceforge.net
Objet : Re: [Nagios-users] Global escalation service problem

My setup is the following..


define serviceescalation{
        name                            production-escalation0
        first_notification              4
        last_notification               5
        notification_interval           15
        register                        0
        }

Then it varies on group ie networks, sysadmin, devel, etc defined like
this,

define serviceescalation{
        name                            servers_production-escalation0
        use                             production-escalation0
        contact_groups                  sysadmins
        register                        0
        }

this would change slightly for networks devel etc.

Make sense?

Spencer
On Wed, 2004-03-31 at 07:13, Yohann DESQUERRE (DSI NOISIEL) wrote:
> Hi all,
> 
> I'd like to declare a global service definition as that:
> 
> 
> define serviceescalation{
>        host_name                      wings
>        service_description           *
>        first_notification                3
>        last_notification                4
>        contact_groups                redcon-0
>        notification_interval           0
>        }
> 
> Or that :
> 
> 
> define serviceescalation{
>        host_name                       * 
>        service_description           *
>        first_notification               3
>        last_notification               4
>        contact_groups               redcon-0
>        notification_interval          0
>        }
> 
> Running configuration check.../etc/init.d/nagios: line 167: 17741
> Segmentation fault      $NagiosBin -v $NagiosCfg >/dev/null 2>&1
> 
> Nagios 1.1
> Copyright (c) 1999-2003 Ethan Galstad (nagios at nagios.org)
> Last Modified: 06-02-2003
> License: GPL
> 
> Reading configuration data...
> 
> /etc/init.d/nagios: line 167: 17742 Segmentation fault      $NagiosBin
> -v $NagiosCfg
> Failed - aborting restart.
> ...and I've got this message :
> "
> 
> 
> Any ideas????
> 
> 
> Thanks for help!!!
> 
> -----------------------------------------------
> Yohann Desquerre
> "Plateforme ANPE.FR"
> S/Direction de la production
> Gestion des Ressources
> -----------------------------------------------
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id70&alloc_id638&opk
> _______________________________________________
> 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



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click
_______________________________________________
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





More information about the Users mailing list