Nagios Support Forum

nunezric,

We'll review your .cfg files for erros. In the meantime, please review the following if you haven't already:

http://assets.nagios.com/downloads/nagi ... ations.pdf


Thanks,

-Yancy

Hi,

Any update?


Thank you,

Ricardo

has the fs_/usr service returned to an OK state since you setup the escalations? or has it been CRITICAL the whole time?

If it has not returned to an OK state this could be the problem

The pararameter "notification_interval 1440" means that there should be a service escalation every 24 hours (even if the service has stayed critical), right?

I do receive service escalation for problems which don't have the character "/" in the middle. Did you find some mistake of mine if the attachments I've put in this incident? If not, are you taking into account the possibility that perhaps Nagios has a source code bug?

I'm receiving every 24 hours e-mails like the following. This means that Nagios is sending alerts every 24 hours even if the service has stayed critical. The problem is that the service escalation is not working for services like "fs_/usr":

From: Nagios XI MTL [mailto:[email protected]]
Sent: Sunday, February 17, 2013 3:38 PM
To: Ricardo Nunez
Subject: PROBLEM Service Alert - mtl1log02/fs_/usr is CRITICAL

***** Nagios XI Alert *****

Nagios has detected a problem with this service.

Notification Type: PROBLEM

Service: fs_/usr
Host: mtl1log02
Address: 134.87.177.115
State: CRITICAL
Info:
CRIT - 97.0% used (8.25 of 8.5 GB), (levels at 80.0/90.0%), trend: -0.00B / 24 hours
Date/Time: 2013-02-17 20:37:54
Location: Montreal

Respond: http://nagiosxi-mtl.pmc-sierra.bc.ca/na ... 668af3fb09
Nagios URL: http://nagiosxi-mtl.pmc-sierra.bc.ca/nagiosxi/

The escalation chains are setup when a service goes into a non-OK state, if it has been in a CRITICAL state and not returned to an OK state since the escalation were setup it would not trigger the escalation since it is already past the *First Notification of 1 set in the escalation

nunezric wrote:If not, are you taking into account the possibility that perhaps Nagios has a source code bug?

I have considered this and performed a test which had expected results

You were absolutely right.

I just set the parameter last_notification to "0" (no limit) in order to escalate the issue and it worked.

I just set it back to "last_notification 1" in that service escalation.

You can close this incident.


Thank you very much,

Ricardo