Service Notifications Stopped

[Marc Powell]

> -----Original Message-----
> From: nagios-users-bounces at lists.sourceforge.net [mailto:nagios-users-
> bounces at lists.sourceforge.net] On Behalf Of Ben James
> Sent: Tuesday, March 13, 2007 9:07 PM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] Service Notifications Stopped
> 
> Hi all,
> 
> I'm hoping you may be able to give me some insight into a problem I'm
> having with my Nagios configuration.
> 
> I have approximately 20 hosts with 35 services set up, with
> notifications only set to send for service alerts. This was all
working
> fine up until a couple of weeks ago, when notifications for services
> seem to have stopped. Something may have changed in the configuration
at
> this point, but I have gone back over it all and have not been able to
> find the problem.


> 
> Is there anyway I can get some information on what nagios is doing
when
> I get a HARD service alert, and where it is deciding it doesn't need
to
> send a notification?

Recompiling nagios with DEBUG will output more in-depth information
which may be helpful --

[nagios-2.7]$ ./configure --help

[chop]
--enable-DEBUG0 shows function entry and exit
--enable-DEBUG1 shows general info messages
--enable-DEBUG2 shows warning messages
--enable-DEBUG3 shows scheduled events (service and host checks... etc)
--enable-DEBUG4 shows service and host notifications
--enable-DEBUG5 shows SQL queries

--
Marc


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
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