notification problem help

[Aaron Segura]

That is a SOFT state change.  You won't be notified until there is a
HARD state change.  I would guess your nagios instance is functioning as
configured...however, without some relevant configuration information
from you, it's just a guess.

 

________________________________

From: Anirudh Srinivasan [mailto:srianirudh at gmail.com] 
Sent: Wednesday, February 11, 2009 11:26 AM
To: nagios-users at lists.sourceforge.net
Subject: [Nagios-users] notification problem help

 

Hey Folks,

 

We have a nagios monitoring tool in our office. 

 

 Service
Critical<https://tsweb.auxis-its.com/nagios/images/critical.png>
[02-11-2009 09:18:13] SERVICE ALERT: app-miafps01;Windows
Print;CRITICAL;SOFT;1;LPDSVC: Stopped


As we can see this perticular service failed at around 09:18 but we were
notified at around 09:45 . I browsed through the logs but couldnt find
anything useful. Can you people suggest me what could be the reason .

What is the reason nagios notified us only at 0945 and why not at 0918.
Any help would be appreciated.

-- 
Anirudh Srinivasan

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20090211/ab4d7fb1/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
-------------- next part --------------
_______________________________________________
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