[SPAM] Re: Issue with distributed Host checks

[Assaf Flatto]

You can try and remove the

active_checks_enabled    1

from the host config , the fact that it is enabled make nagios see the 
change and then trigger the active check which will be the 2nd status 
update ( from up to down) and hence make it a hard state .

if you do not trigger the active check , the master nagios will log the 
status change and then wait for the worker's next update.


Assaf

Mike Lindsey wrote:
> I'm seeing oddities with my host checks.  These are all on 3.2.1, and I 
> do not have Host dependencies for the hosts in question.
>
> A worker node will detect a host as being down and send back a soft 
> passive result.
>
> In many cases, the master will then immediately perform an active host 
> check which is NOT logged.  That host check will result in a hard state 
> change, even though host checks are set for 2 retries at 1 minute intervals.
>
> Anyone know what's going on, or do I need to go read the source?
>
> Here's the relevant entries from the master node's nagios.cfg:
> $ grep host nagios.cfg
> accept_passive_host_checks=1
> cached_host_check_horizon=15
> check_for_orphaned_hosts=0
> check_host_freshness=0
> enable_predictive_host_dependency_checks=1
> execute_host_checks=0
> global_host_event_handler=event_handler
> high_host_flap_threshold=20.0
> host_check_timeout=30
> host_freshness_check_interval=60
> host_inter_check_delay_method=s
> host_perfdata_file=/usr/local/nagios/var/host-perfdata.dat
> host_perfdata_file_mode=a
> log_host_retries=1
> low_host_flap_threshold=5.0
> max_host_check_spread=30
> obsess_over_hosts=0
> passive_host_checks_are_soft=1
> retained_contact_host_attribute_mask=0
> retained_host_attribute_mask=0
> retained_process_host_attribute_mask=0
> translate_passive_host_checks=0
> use_aggressive_host_checking=0
>
> And here's an example host object:
> define host {
>      host_name           xxxx
>      address             xxxx
>      hostgroups          
> All,cres,cres-dbss,cres-prod-dbss,cres-prod-dbss.soma,dbss,linux2,soma
>      check_command       check-host-alive
>      max_check_attempts  2
>      check_interval      3
>      retry_interval      1
>      active_checks_enabled    1
>      passive_checks_enabled   1
>      check_period        24x7
>      obsess_over_host    1
>      check_freshness     1
>      flap_detection_enabled   1
>      process_perf_data   0
>      retain_status_information     1
>      retain_nonstatus_information  0
>      contact_groups      sysops
>      notifications_enabled         1
>      notification_interval         60
>      notification_period           24x7
>      notification_options          d,u,r,f
>      notes_url           
> https://xxxx/cacti/graph_view.php?action=preview&host_id=0&graph_template_id=0&filter=xxxx
>      action_url          /nagios/cgi-bin/extui.py?host=xxxx.com
>      _ENVIRONMENT        prod
>      _HARDWARE           R710
>      _LOCATION           soma
>      _OS                 Linux 2.6.18-164.el5 #1 SMP Tue Aug 18 15:51:48 
> EDT 2009 x86_64
>      _PORTFOLIO          Encryption
>      _PRODUCT            cres
>      _PURPOSE            dbss
>      _RACK               07--11
>      _SERIAL             536QNM1
>      _SOURCE             ASDB/Servers
>      _SOURCE_URL         https://xxxx/servers/admin/servers/server/3363/
>      __SNMP_COMMUNITY    xxxx
> }
>
>   


------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
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