Notifications problem

[Antoine Rocher]

Hi again,

My problem seems to be an acknowledgment stickyness problem :


in nagios doc :
"If the "sticky" option is set to one (1), the acknowledgement will remain until the service returns to an OK state. Otherwise the acknowledgement will automatically be removed when the service changes state" 


but in my logs :
[1186627415] EXTERNAL COMMAND: ACKNOWLEDGE_SVC_PROBLEM;serveur;Check
Services;2;0;0;burton;ack

So it seems that the (2) puts stickyness on, and not (1).
Is this an error in the nagios documentation ?


Thanks.

Antoine
 

-----Message d'origine-----
De : nagios-users-bounces at lists.sourceforge.net [mailto:nagios-users-bounces at lists.sourceforge.net] De la part de Antoine Rocher
Envoyé : jeudi 9 août 2007 17:01
À : nagios-users at lists.sourceforge.net
Objet : [Nagios-users] Notifications problem

Hi all,


I got a problem with nagios last night. I don't get notifications after
the state type (SOFT or HARD) changed on one check.

Here are these options'check :

max_check_attempts 2
normal_check_interval 1
retry_check_interval 1
notification_options w,u,c,r 
notification_interval 15

In my logs I got :
[1186626921] SERVICE ALERT: serveur;Check
Services;CRITICAL;SOFT;1;Status : 2 - service problem 1
[1186626981] SERVICE ALERT: serveur;Check
Services;CRITICAL;HARD;2;Status : 2 - service problem 1

[1186626981] SERVICE NOTIFICATION: Pager;serveur;Check
Services;CRITICAL;notify-by-epager;Status : 2 - service problem 1
[1186626981] SERVICE NOTIFICATION: AlertesNagios;serveur;Check
Services;CRITICAL;notify-by-email;Status : 2 - service problem 1

[1186627041] SERVICE ALERT: serveur;Check Services;WARNING;HARD;2;Status
: 1 - service problem 1

[1186627041] SERVICE NOTIFICATION: Pager;serveur;Check
Services;WARNING;notify-by-epager;Status : 1 - service problem 1
[1186627041] SERVICE NOTIFICATION: AlertesNagios;serveur;Check
Services;WARNING;notify-by-email;Status : 1 - service problem 1

[1186627415] EXTERNAL COMMAND: ACKNOWLEDGE_SVC_PROBLEM;serveur;Check
Services;2;0;0;burton;ack

[1186628915] SERVICE ALERT: serveur;Check
Services;CRITICAL;HARD;2;Status : 2 - service problem 1,2
[1186628975] SERVICE ALERT: serveur;Check Services;WARNING;HARD;2;Status
: 1 - service problem 1
[1186629345] SERVICE ALERT: serveur;Check
Services;CRITICAL;HARD;2;Status : 2 - service problem 1,3
[1186629470] SERVICE ALERT: serveur;Check Services;WARNING;HARD;2;Status
: 1 - service problem 1,3
[1186636253] SERVICE ALERT: serveur;Check Services;OK;HARD;2;Status : 0
- 



Where "Statut" is the exit value of the script (0,1 or 2 = OK,WARNING or
CRIT). This check should reflect the change of what the script checks. I
mean, the two first checks in error should put the alert in CRIT state
(SOFT then HARD), and the third one in WARNING state (HARD). If the
thing checked changes one more time, the alert should be back in CRIT
state (HARD)before going back to WARNING state (HARD)
.
Let's go with an example as I have difficulties to explain what my
script do :

1rst check : the script check a page, which should be empty, but which
has things on it, then the script exits with 2 (and in body of alert I
have "service problem 1") => nagios CRIT (SOFT) and no notify
2nd check : the script exits with 2 (service problem 1) => nagios CRIT
(HARD) and notify
3rd check : the scripts exits with 1 (service problem 1)=> nagios WARN
(HARD) and notify
4th check : the scripts exits with 2 (service problem 1,2) => nagios
CRIT (HARD) and notify ...

But as you can see in my logs, at the 4th check nagios didn't notify,
nor the next HARD changes of state.
An other problem is that I acknowledged a WARNING state (HARD) but when
the alert changed to CRITICAL state (HARD) the acknowledgment was in
place. The same for the next changes of state. Acknowledgment was
effective only 4 changes of state after.

Hope I am clear enough. Anybody has an idea ?

Thanks for your help.
(and sorry for my poor english)


Antoine

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
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

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
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