cannot stop notifications!!

[Marc Powell]

> -----Original Message-----
> From: nagios-users-bounces at lists.sourceforge.net [mailto:nagios-users-
> bounces at lists.sourceforge.net] On Behalf Of Carlos Mauricio Reyes
> Sanmiguel
> Sent: Friday, August 25, 2006 6:07 PM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] cannot stop notifications!!
> 
> 
> Hi,
> 
> I´ve been working with nagios for a while, I like it a lot, but now i´m
> having some major problems with notifications. I have a server that flaps
> a lot because of a poor channel, i configured nagios with the external
> commands options enable, and it seems to work, but now, this server is
> sending too many messages, almost 1000 a day, that is driving me crazy..,
> I try to disable notifications from the web page, and it appears to have
> taken the command, it appears in red in the bottom of the page, but when
> the page refresh is not disable anymore.... and it continues to send
> messages.. the last change i did, was to modify the configuration file
> directly, the notifications option from workhours to none... and it
> continues to send the messages..
> 
> Does anybody know how i can make it to take the changes?

It sounds to me that you have more than one nagios daemon running. Stop nagios then use ps/kill to kill any nagios processes that remain then retart nagios.

--
Marc

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
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