interval setup wont work
Arno Lehmann
al at its-lehmann.de
Tue Jan 16 12:31:21 CET 2007
Hi,
On 1/16/2007 12:09 PM, Daniel wrote:
> Hi there,
>
> i setup a host to check every 30secs btw every 60secs.
>
> The last check command was sheduled:
>
> Last Check Time: 01-16-2007 11:54:11
>
> Now 10 minutes are over and nothink happends:
>
> Here my config for this host:
Your config shows an interval of 60.
The normal interval length is 1 minute.
You'll have to change your configuration accordingly.
This is all in the Manual, by the way.
Arno
> define host{
> name ipv6 ; The name of this host template - referenced in other host definitions, used for template recurs$
> notifications_enabled 1 ; Host notifications are enabled
> event_handler_enabled 1 ; Host event handler is enabled
> flap_detection_enabled 0 ; Flap detection is enabled
> process_perf_data 1 ; Process performance data
> retain_status_information 1 ; Retain status information across program restarts
> retain_nonstatus_information 1 ; Retain non-status information across program restarts
> parents ipv6
> register 0 ; DONT REGISTER THIS DEFINITION - ITS NOT A REAL HOST, JUST A TEMPLATE!
> }
>
> define service{
> ; The 'name' of this service template, referenced in other service definitions
> name ipv6
> active_checks_enabled 1 ; Active service checks are enabled
> passive_checks_enabled 0 ; Passive service checks are enabled/disabled
> parallelize_check 1 ; Active service checks should be parallelized
> ; (disabling this can lead to major performance problems)
> obsess_over_service 1 ; We should obsess over this service (if necessary)
> check_freshness 0 ; Default is to NOT check service 'freshness'
> notifications_enabled 1 ; Service notifications are disabled
> event_handler_enabled 1 ; Service event handler is disabled
> flap_detection_enabled 0 ; Flap detection is disabled
> process_perf_data 1 ; Process performance data
> retain_status_information 1 ; Retain status information across program restarts
> retain_nonstatus_information 1 ; Retain non-status information across program restarts
>
> register 0 ; DONT REGISTER THIS DEFINITION - ITS NOT A REAL SERVICE, JUST A TEMPLATE!
> normal_check_interval 30
> retry_check_interval 30
>
> }
>
>
>
> define host{
> use ipv6
> host_name vs-uptime
> alias vs-uptime
> address 89.106.71.100
> check_command check-host-alive
> max_check_attempts 5
> process_perf_data 0
> retain_nonstatus_information 0
> contact_groups IPv6
> notification_interval 10
> notification_period 24x7
> notification_options d,u,r
> }
>
> define service{
> use ipv6
> host_name vs-uptime
> service_description PING
> is_volatile 0
> check_period 24x7
> max_check_attempts 1
> normal_check_interval 1
> retry_check_interval 1
> contact_groups IPv6
> notification_options w,u,c,r
> notification_interval 10
> notification_period 24x7
> check_command check_ping!100.0,40%!500.0,60%
> }
>
>
> In the nagios.cfg the normal check interval is set to 60secs.
>
> Nothink seems to be work... :(
>
>
--
IT-Service Lehmann al at its-lehmann.de
Arno Lehmann http://www.its-lehmann.de
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
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
More information about the Users
mailing list