where to get help with ext. cmd CHANGE_NORMAL_SVC_CHECK_INTERVAL ?

[John P. Rouillard]

In message <20060316223329.GA7653 at mini.alaya.net>,
prosolutions writes:

>I am using the CHANGE_NORMAL_SVC_CHECK_INTERVAL so
>that if a state of CRITICAL HARD exists longer than
>the time period covered by retry_check_interval and
>max_check_attempts nagios will still continue checking
>the service at an increased interval until it returns
>to OK.
> [mangled broken shell script removed]

What I saw as a shell script isn't a valid shell script. At
the very least it looks like a case statement got chopped
off at the top. Also you have a lot of redundant code there.

Also there is no standard for the arguments to event handler
scripts, including the command definition would have been
useful.
  
>I see after max_check_attempts that state to go
>CRITICAL HARD for the service and then it runs the
>event_handler which runs the external command:
>
>[1142543941] EXTERNAL COMMAND: CHANGE_NORMAL_SVC_CHECK_INTERVAL;test_host;test.html;15

I assume you mean it sends:

  [1142543941] CHANGE_NORMAL_SVC_CHECK_INTERVAL;test_host;test.html;15

the inclusion of "EXTERNAL COMMAND:" is a syntax error. If
that is actually the command sent, Nagios will ignore the
command. What you showed above is the log entry and not what
is sent to the command file right?

>this should set the check_interval to 15 seconds instead
>of the default 90 seconds.  However, watching the log I see
>that the checks on the service revert to 90 s.

What are you seeing in the log that makes you think it's
getting reset? If I use:

 echo "[`date +%s`] CHANGE_NORMAL_SVC_CHECK_INTERVAL;tigris;DiskBackupMountCheck;3"

to change the check interval to three minutes, and direct it
to the command pipe, I see it take effect and stay in
effect. Looking at the Event Log in the web interface shows:

[03-16-2006 22:54:25] EXTERNAL COMMAND: CHANGE_NORMAL_SVC_CHECK_INTERVAL;tigris;DiskBackupMountCheck;3

No other CHANGE_NORMAL_SVC_CHECK_INTERVAL commands occur. If
you are seeing another command reset it, maybe something is
wacky in the event handler.

After the command, /var/log/nagios/retention.dat and
/var/log/nagios/object.cache both show:

  normal_check_interval   3

for the service just as expected. It is normally set to 60
minutes in the configuration files.

When you change the check interval, it doesn't force a
reschedule of the service with the new interval. I
rescheduled from the web interface, but I suspect that a
"SCHEDULE_FORCED_HOST_CHECK" command would also do the
trick. Then I saw the 3 minute reschedule take effect and
stay in effect.

>I cannot find ANY documentation nor mention of this command,
>CHANGE_NORMAL_SVC_CHECK_INTERVAL, anywhere on the users or dev
>mailing lists, via google, or anywhere else except here:  
>
>http://www.nagios.org/developerinfo/externalcommands/commandinfo.php?command_id=110

That's the only place I have found it. The source is the
only other doc.

Also I am using nagios 2.0rc1, so YMMV.

				-- rouilj
John Rouillard
===========================================================================
My employers don't acknowledge my existence much less my opinions.


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&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