Trying some more things, and going through the suggestions from this thread,
it was verified that we can send custom service, and host alerts.  We also
get host alerts, but no service alerts.


On Tue, Jan 13, 2009 at 5:10 PM, Marc Powell <m...@ena.com> wrote:

>
> On Jan 13, 2009, at 5:15 PM, jmose...@corp.xanadoo.com wrote:
>
> > That certainly seems to be a valid configuration.  Have you included
> > all
> > your configs in the main nagios.cfg file so that they are all being
> > read?
> > Barring that, do you have any service/host depencies setup?  What
> > about
> > escalations?
> >
> > If you have any dependency or escalation configs, I would disable them
> > first before doing any more troubleshooting.
>
>
> ... also verify that you don't have notifications disabled program-
> wide in nagios.cfg, via the web interface (Process Info) or
> specifically for this host or service via the web interface (click on
> the service and/or host name).
>
> --
> Marc
>
>
>
> ------------------------------------------------------------------------------
> 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
>
------------------------------------------------------------------------------
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

Reply via email to