Page 1 of 2

Nagios Core: Mass Update of Host .cfg files

Posted: Wed Jan 20, 2016 4:43 pm
by grantdoug
Mass Update of Host .cfg files
We are attempting to mass-update the hundreds of hosts we monitor by editing them offline, then uploading them back to Nagios Core.
The directory that we load the changed files to is: /usr/local/nagios/etc/hosts
Unfortunately when the changed files are uploaded, they do not show the change in the web interface, even after Nagios is restarted.
I have looked through the Nagios Core configuration, and am concerned that it will accept uploaded files (though XI does have a utility to perform import operations).
Help appreciated,
Doug @ Jackson Hole Mountain Resort

Re: Mass Update of Host .cfg files

Posted: Wed Jan 20, 2016 5:11 pm
by tmcdonald
I guess my first question is: Is this for Core or XI? You mention both in your post, so I want to make sure we are clear on our end.

Re: Mass Update of Host .cfg files

Posted: Wed Jan 20, 2016 5:29 pm
by grantdoug
I wrote in the post, " then uploading them back to Nagios core." I also mentioned "though XI does have a utility to perform import operations." But I updated the subject to make the post more clearly refer to Nagios Core.

Re: Nagios Core: Mass Update of Host .cfg files

Posted: Wed Jan 20, 2016 5:39 pm
by tmcdonald
The reason I ask is because XI runs Core underneath, and we get a lot of people asking questions about XI in the Core forum, or vice-versa. And while XI does include Core, there are differences in how the configs are handled that can lead to exactly the problem you are describing.

Are there other hosts in the /usr/local/nagios/etc/hosts directory that are working, and it's just these new ones that do not? Where do you have your working configs stored? Likely your nagios.cfg is missing a directive to cinluce the /usr/local/nagios/etc/hosts files.

Re: Nagios Core: Mass Update of Host .cfg files

Posted: Wed Jan 20, 2016 5:55 pm
by grantdoug
Note that our Nagios hosts we have manually configured in the web interface are working perfectly.

Our question is specifically when we attempt to manually alter a host .cfg file, and upload it with SFTP, that we cannot see the change go into effect in the web interface.

Re: Nagios Core: Mass Update of Host .cfg files

Posted: Wed Jan 20, 2016 6:14 pm
by Box293
Please post your /usr/local/nagios/etc/nagios.cfg file.

After uploading and restarting nagios, are the changes reflected in /usr/local/nagios/var/objects.cache ?

Re: Nagios Core: Mass Update of Host .cfg files

Posted: Thu Jan 21, 2016 9:49 am
by grantdoug
I do see the changed values in the objects.cache file.

Here is the Nagios .cfg file.

# MODIFIED
admin_email=root@localhost
admin_pager=root@localhost
translate_passive_host_checks=1
log_event_handlers=0
use_large_installation_tweaks=1
enable_environment_macros=0


# NDOUtils module
#broker_module=/usr/local/nagios/bin/ndomod.o config_file=/usr/local/nagios/etc/ndomod.cfg


# PNP settings - bulk mode with NCPD
process_performance_data=1
# service performance data
service_perfdata_file=/usr/local/nagios/var/service-perfdata
service_perfdata_file_template=DATATYPE::SERVICEPERFDATA\tTIMET::$TIMET$\tHOSTNAME::$HOSTNAME$\tSERVICEDESC::$SERVICEDESC$\tSERVICEPERFDATA::$SERVICEPERFDATA$\tSERVICECHECKCOMMAND::$SERVICECHECKCOMMAND$\tHOSTSTATE::$HOSTSTATE$\tHOSTSTATETYPE::$HOSTSTATETYPE$\tSERVICESTATE::$SERVICESTATE$\tSERVICESTATETYPE::$SERVICESTATETYPE$\tSERVICEOUTPUT::$SERVICEOUTPUT$
service_perfdata_file_mode=a
service_perfdata_file_processing_interval=15
service_perfdata_file_processing_command=process-service-perfdata-file-pnp-bulk
# host performance data
host_perfdata_file=/usr/local/nagios/var/host-perfdata
host_perfdata_file_template=DATATYPE::HOSTPERFDATA\tTIMET::$TIMET$\tHOSTNAME::$HOSTNAME$\tHOSTPERFDATA::$HOSTPERFDATA$\tHOSTCHECKCOMMAND::$HOSTCHECKCOMMAND$\tHOSTSTATE::$HOSTSTATE$\tHOSTSTATETYPE::$HOSTSTATETYPE$\tHOSTOUTPUT::$HOSTOUTPUT$
host_perfdata_file_mode=a
host_perfdata_file_processing_interval=15
host_perfdata_file_processing_command=process-host-perfdata-file-pnp-bulk


# OBJECTS - UNMODIFIED
#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/localhost.cfg
#cfg_file=/usr/local/nagios/etc/objects/templates.cfg
#cfg_file=/usr/local/nagios/etc/objects/timeperiods.cfg


# STATIC OBJECT DEFINITIONS (THESE DON'T GET EXPORTED/IMPORTED BY NAGIOSQL)
cfg_dir=/usr/local/nagios/etc/static

# OBJECTS EXPORTED FROM NAGIOSQL
cfg_file=/usr/local/nagios/etc/contacttemplates.cfg
cfg_file=/usr/local/nagios/etc/contactgroups.cfg
cfg_file=/usr/local/nagios/etc/contacts.cfg
cfg_file=/usr/local/nagios/etc/timeperiods.cfg
cfg_file=/usr/local/nagios/etc/commands.cfg
cfg_file=/usr/local/nagios/etc/hostgroups.cfg
cfg_file=/usr/local/nagios/etc/servicegroups.cfg
cfg_file=/usr/local/nagios/etc/hosttemplates.cfg
cfg_file=/usr/local/nagios/etc/servicetemplates.cfg
cfg_file=/usr/local/nagios/etc/servicedependencies.cfg
cfg_file=/usr/local/nagios/etc/serviceescalations.cfg
cfg_file=/usr/local/nagios/etc/hostdependencies.cfg
cfg_file=/usr/local/nagios/etc/hostescalations.cfg
cfg_file=/usr/local/nagios/etc/hostextinfo.cfg
cfg_file=/usr/local/nagios/etc/serviceextinfo.cfg
cfg_dir=/usr/local/nagios/etc/hosts
cfg_dir=/usr/local/nagios/etc/services

# GLOBAL EVENT HANDLERS
#global_host_event_handler=xi_host_event_handler
#vi global_service_event_handler=xi_service_event_handler



# UNMODIFIED
accept_passive_host_checks=1
accept_passive_service_checks=1
additional_freshness_latency=15
auto_reschedule_checks=0
auto_rescheduling_interval=30
auto_rescheduling_window=180
bare_update_check=0
cached_host_check_horizon=15
cached_service_check_horizon=15
check_external_commands=1
check_for_orphaned_hosts=1
check_for_orphaned_services=1
check_for_updates=1
check_host_freshness=0
check_result_path=/usr/local/nagios/var/spool/checkresults
check_result_reaper_frequency=10
check_service_freshness=1
command_check_interval=-1
command_file=/usr/local/nagios/var/rw/nagios.cmd
daemon_dumps_core=0
date_format=us
debug_file=/usr/local/nagios/var/nagios.debug
debug_level=0
debug_verbosity=1
enable_embedded_perl=1
enable_event_handlers=1
enable_flap_detection=1
enable_notifications=1
enable_predictive_host_dependency_checks=1
enable_predictive_service_dependency_checks=1
event_broker_options=-1
event_handler_timeout=30
execute_host_checks=1
execute_service_checks=1
external_command_buffer_slots=4096
high_host_flap_threshold=20.0
high_service_flap_threshold=20.0
host_check_timeout=30
host_freshness_check_interval=60
host_inter_check_delay_method=s
illegal_macro_output_chars=`~$&|'"<>
illegal_object_name_chars=`~!$%^&*|'"<>?,()=
interval_length=60
lock_file=/usr/local/nagios/var/nagios.lock
log_archive_path=/usr/local/nagios/var/archives
log_external_commands=0
log_file=/usr/local/nagios/var/nagios.log
log_host_retries=1
log_initial_states=0
log_notifications=1
log_passive_checks=0
log_rotation_method=d
log_service_retries=1
low_host_flap_threshold=5.0
low_service_flap_threshold=5.0
max_check_result_file_age=3600
max_check_result_reaper_time=30
max_concurrent_checks=0
max_debug_file_size=1000000
max_host_check_spread=30
max_service_check_spread=30
nagios_group=nagios
nagios_user=nagios
notification_timeout=30
object_cache_file=/usr/local/nagios/var/objects.cache
obsess_over_hosts=0
obsess_over_services=0
ocsp_timeout=5
p1_file=/usr/local/nagios/bin/p1.pl
passive_host_checks_are_soft=0
perfdata_timeout=5
precached_object_file=/usr/local/nagios/var/objects.precache
resource_file=/usr/local/nagios/etc/resource.cfg
retained_contact_host_attribute_mask=0
retained_contact_service_attribute_mask=0
retained_host_attribute_mask=0
retained_process_host_attribute_mask=0
retained_process_service_attribute_mask=0
retained_service_attribute_mask=0
retain_state_information=1
retention_update_interval=60
service_check_timeout=60
service_freshness_check_interval=60
service_inter_check_delay_method=s
service_interleave_factor=s
sleep_time=0.25
soft_state_dependencies=0
state_retention_file=/usr/local/nagios/var/retention.dat
status_file=/usr/local/nagios/var/status.dat
status_update_interval=10
temp_file=/usr/local/nagios/var/nagios.tmp
temp_path=/tmp
use_aggressive_host_checking=0
use_embedded_perl_implicitly=1
use_regexp_matching=0
use_retained_program_state=1
use_retained_scheduling_info=1
use_syslog=1
use_true_regexp_matching=0
broker_module=/usr/local/lib/mk-livestatus/livestatus.o /usr/local/nagios/var/rw/live pnp_path=/usr/local/nagios/share/perfdata
event_broker_options=-1

Re: Nagios Core: Mass Update of Host .cfg files

Posted: Thu Jan 21, 2016 3:05 pm
by rkennedy
grantdoug wrote:Note that our Nagios hosts we have manually configured in the web interface are working perfectly.
Can you please attach a screen shot showing where you manually configured these hosts?

Re: Nagios Core: Mass Update of Host .cfg files

Posted: Thu Jan 21, 2016 3:38 pm
by grantdoug
We maintain them in the CCM web interface at the url:
http://nagios/ccm/index.php
Screenshot attached.

Re: Nagios Core: Mass Update of Host .cfg files

Posted: Thu Jan 21, 2016 5:13 pm
by Box293
grantdoug wrote:Note that our Nagios hosts we have manually configured in the web interface are working perfectly.

Our question is specifically when we attempt to manually alter a host .cfg file, and upload it with SFTP, that we cannot see the change go into effect in the web interface.
grantdoug wrote:We maintain them in the CCM web interface at the url:
http://nagios/ccm/index.php
Screenshot attached.
Image
Because you are using Core Configuration Manager, all of the settings are stored in a database and then PUSHED down to the flat config files. CCM will have no idea that you've updated the flat config files and will overwrite them the next time you apply configuration.