On 08/05/2013 04:44 PM, Michael Friedrich wrote: > On 05.08.2013 16:27, Daniel Petersen wrote: >> so it look like when the icinga service is running, there were in this >> instance 3 icinga processes and 2 ido2db processes. >> >> I know with some servers, such as httpd for example, it's normal for >> many processes to launch, but is this expected behavior for icinga? > > icinga spawns child processes in order to execute checks. so that's > normal to see more than just one process in ps tree. that's the reason > why i was asking you to stop the service itsself to see whether there's > a wild horse running without any valid pid file. > > for ido2db, there will be one master process, forking a child for each > idomod client connection. so 2 processes is the normal operational case, > 1 is wrong (means no data flow between core and database). details on > that on the wiki in the testing space, articles referencing idoutils. > > either way, please attach # egrep -v "^$|^#" icinga.cfg > Thanks for the explanation. Below is the egrep output.
********** /etc/icinga# egrep -v "^$|^#" icinga.cfg log_file=/var/log/icinga/icinga.log cfg_file=/etc/icinga/commands.cfg cfg_dir=/etc/nagios-plugins/config cfg_dir=/etc/icinga/objects/ cfg_dir=/etc/icinga/modules object_cache_file=/var/cache/icinga/objects.cache precached_object_file=/var/cache/icinga/objects.precache resource_file=/etc/icinga/resource.cfg status_file=/var/lib/icinga/status.dat status_update_interval=10 icinga_user=nagios icinga_group=nagios check_external_commands=1 command_check_interval=-1 command_file=/var/lib/icinga/rw/icinga.cmd external_command_buffer_slots=4096 lock_file=/var/run/icinga/icinga.pid temp_file=/var/cache/icinga/icinga.tmp temp_path=/tmp event_broker_options=-1 log_rotation_method=d log_archive_path=/var/log/icinga/archives use_daemon_log=1 use_syslog=1 use_syslog_local_facility=0 syslog_local_facility=5 log_notifications=1 log_service_retries=1 log_host_retries=1 log_event_handlers=1 log_initial_states=0 log_current_states=1 log_external_commands=1 log_passive_checks=1 log_long_plugin_output=0 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=/var/lib/icinga/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=/var/cache/icinga/retention.dat retention_update_interval=60 use_retained_program_state=1 dump_retained_host_service_states_to_neb=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 use_aggressive_host_checking=0 execute_service_checks=1 accept_passive_service_checks=1 execute_host_checks=1 accept_passive_host_checks=1 enable_notifications=1 enable_event_handlers=1 process_performance_data=0 obsess_over_services=0 obsess_over_hosts=0 translate_passive_host_checks=0 passive_host_checks_are_soft=0 check_for_orphaned_services=1 check_for_orphaned_hosts=1 service_check_timeout_state=u check_service_freshness=1 service_freshness_check_interval=60 check_host_freshness=0 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=iso8601 p1_file=/usr/lib/icinga/p1.pl enable_embedded_perl=1 use_embedded_perl_implicitly=1 stalking_event_handlers_for_hosts=0 stalking_event_handlers_for_services=0 stalking_notifications_for_hosts=0 stalking_notifications_for_services=0 illegal_object_name_chars=`~!$%^&*|'"<>?,()= illegal_macro_output_chars=`~$&|'"<> keep_unknown_macros=0 use_regexp_matching=0 use_true_regexp_matching=0 admin_email=root@localhost admin_pager=pageroot@localhost daemon_dumps_core=0 use_large_installation_tweaks=0 enable_environment_macros=1 debug_level=0 debug_verbosity=2 debug_file=/var/log/icinga/icinga.debug max_debug_file_size=100000000 event_profiling_enabled=0 ------------------------------------------------------------------------------ Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ icinga-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/icinga-users
