Re: [Nagios-users] freshness checks not working
On 27 December 2011 13:32, JM jm+nagios-us...@roth.lu wrote: Jim Avery jim at jimavery.me.uk writes: Is the the relevant entry for that service check in your objects.cache file correct? I believe so. Do you see something out of the ordinary: host_name xxx service_description yyy check_period 24x7 check_command check_dummy!0 contact_groups cg_xx notification_period 24x7 initial_state o check_interval 1.00 retry_interval 1.00 max_check_attempts 1 is_volatile 1 parallelize_check 1 active_checks_enabled 0 passive_checks_enabled 1 obsess_over_service 1 event_handler_enabled 1 low_flap_threshold 0.00 high_flap_threshold 0.00 flap_detection_enabled 0 flap_detection_options o,w,u,c freshness_threshold 600 check_freshness 1 notification_options u,w,c notifications_enabled 1 notification_interval 240.00 first_notification_delay 0.00 stalking_options n process_perf_data 1 failure_prediction_enabled 1 retain_status_information 1 retain_nonstatus_information 1 Ok looking at my config where I do the same sort of thing to clear SNMP-Trap states after a period, it's pretty much the same as yours except I have .. obsess_over_service 0 event_handler_enabled 0 low_flap_threshold 60.00 high_flap_threshold 80.00 flap_detection_enabled 1 flap_detection_options o,w,u,c notification_optionsw,c,r stalking_optionsw,c process_perf_data 0 failure_prediction_enabled 0 I'll leave it to you to think about whether any of those are likely to have any effect. I don't think they should do, but it might be worth doing a bit of experimentation. Cheers, Jim -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ Nagios-users mailing list Nagios-users@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
Re: [Nagios-users] freshness checks not working
Jim Avery jim at jimavery.me.uk writes: your objects.cache file correct? I believe so. Do you see something out of the ordinary? I can't see anything wrong with that at all, no. The only difference I can think of between what you have and what I have is I don't use an event handler. I have tested that (event handlers are enabled globally, but only defined in a few rare places): for now the freshness check seems to work again. If it is really related to that, is there a special meaning to it, or can it be considered a bug? Other possible causes that have come to mind is: - template used by the service is nested at least 3 levels deep (not sure how many people do that) - obsess-over-service is also enabled although I can't remember why rightaway... Thanks for now. -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ Nagios-users mailing list Nagios-users@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
Re: [Nagios-users] freshness checks not working
Jim Avery jim at jimavery.me.uk writes: Is the the relevant entry for that service check in your objects.cache file correct? I believe so. Do you see something out of the ordinary: host_name xxx service_description yyy check_period24x7 check_command check_dummy!0 contact_groups cg_xx notification_period 24x7 initial_state o check_interval 1.00 retry_interval 1.00 max_check_attempts 1 is_volatile 1 parallelize_check 1 active_checks_enabled 0 passive_checks_enabled 1 obsess_over_service 1 event_handler_enabled 1 low_flap_threshold 0.00 high_flap_threshold 0.00 flap_detection_enabled 0 flap_detection_options o,w,u,c freshness_threshold 600 check_freshness 1 notification_optionsu,w,c notifications_enabled 1 notification_interval 240.00 first_notification_delay0.00 stalking_optionsn process_perf_data 1 failure_prediction_enabled 1 retain_status_information 1 retain_nonstatus_information1 -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ Nagios-users mailing list Nagios-users@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
Re: [Nagios-users] freshness checks not working
Jim Avery jim at jimavery.me.uk writes: Can someone tell me why some real services derived from the above template do not seem to do the freshness checks? Are you sure they don't do the freshness check? Definitely, once a trap was received, the state remains critical... -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ Nagios-users mailing list Nagios-users@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
Re: [Nagios-users] freshness checks not working
On 27 December 2011 13:32, JM jm+nagios-us...@roth.lu wrote: Jim Avery jim at jimavery.me.uk writes: Is the the relevant entry for that service check in your objects.cache file correct? I believe so. Do you see something out of the ordinary: I can't see anything wrong with that at all, no. The only difference I can think of between what you have and what I have is I don't use an event handler. I'll be back at work on Thursday so I'll take a closer look then. -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ Nagios-users mailing list Nagios-users@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
[Nagios-users] freshness checks not working
Hi there,
consider the following template:
define service {
name x_trap
register 0; DONT REGISTER - ITS NOT
REAL,JUST A TEMPLATE!
host_name host
active_checks_enabled 0
passive_checks_enabled 1
is_volatile1
max_check_attempts 1
normal_check_interval 1
retry_check_interval 1
flap_detection_enabled 0
contact_groups cg_x
notification_options w,u,c
notification_interval 240
notification_period24x7
check_freshness 1
freshness_threshold 600
check_command check_dummy!0
check_period 24x7
}
Can someone tell me why some real services derived from the above template
do not seem to do the freshness checks?
define service {
usex_trap
service_descriptionX-service
contact_groups x-team
}
We're running Nagios 3.2.1.
Thanks and happy holidays.
--
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create
new or port existing apps to sell to consumers worldwide. Explore the
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev
___
Nagios-users mailing list
Nagios-users@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
Re: [Nagios-users] freshness checks not working
On 23 December 2011 18:48, jm+nagios-us...@roth.lu wrote:
Hi there,
consider the following template:
define service {
name x_trap
register 0 ; DONT REGISTER - ITS NOT
REAL,JUST A TEMPLATE!
host_name host
active_checks_enabled 0
passive_checks_enabled 1
is_volatile 1
max_check_attempts 1
normal_check_interval 1
retry_check_interval 1
flap_detection_enabled 0
contact_groups cg_x
notification_options w,u,c
notification_interval 240
notification_period 24x7
check_freshness 1
freshness_threshold 600
check_command check_dummy!0
check_period 24x7
}
Can someone tell me why some real services derived from the above template
do not seem to do the freshness checks?
Are you sure they don't do the freshness check? Personally I would
have the following arguments (or similar) to check_dummy, using 3
rather than 0 to show an unknown rather than ok state.
check_command check_dummy!3 UNKNOWN: Nagios did not receive a
passive service check recently.
One thing that catches me out frequently is when I put an explanation
mark in there which stops it from working. For example, this will not
work.
check_command check_dummy!3 UNKNOWN: Nagios did not receive a
passive service check recently!
hth,
Jim
--
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create
new or port existing apps to sell to consumers worldwide. Explore the
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev
___
Nagios-users mailing list
Nagios-users@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
