[Nagios-users] Set Host Status from Distributed Monitoring Server
Hello! Pardon me if this is already covered somewhere in the documentation. I can't seem to find what I'm looking for. I have a working Nagios 3.2.0 environment in a distributed configuration. One of my environments lives behind a firewall that is blocking icmp traffic from the central server. In that same environment I have a remote Nagios node that is successfully sending service checks backs to the central server. All of the nodes behind this firewall are reporting DOWN on the central server nagios page, but their service checks are reporting OK. Is their a configuration setting available so that the central server will report these nodes as UP if it receives a successful check from the remote monitoring node? The translate_passive_host_checks options sounds like it should work, but it doesn't. I understand I can remove the check_command from the host.cfg, but the host status will be a Pending status. Any suggestions? Thank you in advance for your time and assistance. CS Configs log_file=/usr/local/nagios/var/nagios.log cfg_file=/usr/local/nagios/etc/objects/commands.cfg cfg_file=/usr/local/nagios/etc/objects/contacts.cfg cfg_file=/usr/local/nagios/etc/objects/timeperiods.cfg cfg_file=/usr/local/nagios/etc/objects/templates.cfg cfg_file=/usr/local/nagios/etc/objects/hostgroups.cfg cfg_dir=/usr/local/nagios/etc/hosts object_cache_file=/usr/local/nagios/var/objects.cache precached_object_file=/usr/local/nagios/var/objects.precache resource_file=/usr/local/nagios/etc/resource.cfg status_file=/usr/local/nagios/var/status.dat status_update_interval=10 nagios_user=nagios nagios_group=nagios check_external_commands=1 command_check_interval=-1 command_file=/usr/local/nagios/var/rw/nagios.cmd external_command_buffer_slots=4096 lock_file=/usr/local/nagios/var/nagios.lock temp_file=/usr/local/nagios/var/nagios.tmp temp_path=/tmp event_broker_options=-1 log_rotation_method=d log_archive_path=/usr/local/nagios/var/archives use_syslog=1 log_notifications=1 log_service_retries=1 log_host_retries=1 log_event_handlers=1 log_initial_states=0 log_external_commands=1 log_passive_checks=1 service_inter_check_delay_method=s max_service_check_spread=30 service_interleave_factor=s host_inter_check_delay_method=s max_host_check_spread=30 max_concurrent_checks=0 check_result_reaper_frequency=10 max_check_result_reaper_time=30 check_result_path=/usr/local/nagios/var/spool/checkresults max_check_result_file_age=3600 cached_host_check_horizon=15 cached_service_check_horizon=15 enable_predictive_host_dependency_checks=1 enable_predictive_service_dependency_checks=1 soft_state_dependencies=0 auto_reschedule_checks=0 auto_rescheduling_interval=30 auto_rescheduling_window=180 sleep_time=0.25 service_check_timeout=60 host_check_timeout=30 event_handler_timeout=30 notification_timeout=30 ocsp_timeout=5 perfdata_timeout=5 retain_state_information=1 state_retention_file=/usr/local/nagios/var/retention.dat retention_update_interval=60 use_retained_program_state=1 use_retained_scheduling_info=1 retained_host_attribute_mask=0 retained_service_attribute_mask=0 retained_process_host_attribute_mask=0 retained_process_service_attribute_mask=0 retained_contact_host_attribute_mask=0 retained_contact_service_attribute_mask=0 interval_length=60 check_for_updates=1 bare_update_check=0 use_aggressive_host_checking=0 execute_service_checks=0 accept_passive_service_checks=1 execute_host_checks=1 accept_passive_host_checks=1 enable_notifications=0 enable_event_handlers=1 process_performance_data=0 obsess_over_services=0 obsess_over_hosts=0 translate_passive_host_checks=1 passive_host_checks_are_soft=0 check_for_orphaned_services=1 check_for_orphaned_hosts=1 check_service_freshness=1 service_freshness_check_interval=60 check_host_freshness=1 host_freshness_check_interval=60 additional_freshness_latency=15 enable_flap_detection=1 low_service_flap_threshold=5.0 high_service_flap_threshold=20.0 low_host_flap_threshold=5.0 high_host_flap_threshold=20.0 date_format=us p1_file=/usr/local/nagios/bin/p1.pl enable_embedded_perl=1 use_embedded_perl_implicitly=1 illegal_object_name_chars=`~!$%^*|'?,()= illegal_macro_output_chars=`~$|' use_regexp_matching=0 use_true_regexp_matching=0 admin_email=nag...@localhost admin_pager=pagenag...@localhost daemon_dumps_core=0 use_large_installation_tweaks=0 enable_environment_macros=1 debug_level=16 debug_verbosity=2 debug_file=/usr/local/nagios/var/nagios.debug max_debug_file_size=100 Remote Monitoring Node log_file=/usr/local/nagios/var/nagios.log cfg_file=/usr/local/nagios/etc/objects/commands.cfg cfg_file=/usr/local/nagios/etc/objects/contacts.cfg cfg_file=/usr/local/nagios/etc/objects/timeperiods.cfg cfg_file=/usr/local/nagios/etc/objects/templates.cfg cfg_file=/usr/local/nagios/etc/objects/hostgroups.cfg cfg_dir=/usr/local/nagios/etc/hosts object_cache_file=/usr/local/nagios/var/objects.cache
Re: [Nagios-users] Set Host Status from Distributed Monitoring Server
tktuc...@gmail.com wrote: Hello! Pardon me if this is already covered somewhere in the documentation. I can't seem to find what I'm looking for. I have a working Nagios 3.2.0 environment in a distributed configuration. One of my environments lives behind a firewall that is blocking icmp traffic from the central server. In that same environment I have a remote Nagios node that is successfully sending service checks backs to the central server. All of the nodes behind this firewall are reporting DOWN on the central server nagios page, but their service checks are reporting OK. Is their a configuration setting available so that the central server will report these nodes as UP if it receives a successful check from the remote monitoring node? The translate_passive_host_checks options sounds like it should work, but it doesn't. I understand I can remove the check_command from the host.cfg, but the host status will be a Pending status. Any suggestions? Thank you in advance for your time and assistance. translate_passive_host_checks only works if you send them. Are you? I suspect whatever method you're using to send service check results upstream is only being used for service checks, and you may need to modify it to also send service check results. -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ 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
