Upgrade from 5.2.7 to 5.5.0 failed

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
blueagle
Posts: 26
Joined: Mon Feb 17, 2014 4:16 am

Re: Upgrade from 5.2.7 to 5.5.0 failed

Post by blueagle »

Here's the full output as requested:


[root@nagios ~]# /usr/local/nagiosxi/scripts/reconfigure_nagios.sh

--- reset_config_perms.sh ------------
> Setting CCM script permissions
> Setting script permissions
> Setting special component script permissions
> Setting configuration file/directory permissions
> Setting perfdata directory and RRD permissions
> Setting NOM checkpoint user:group permissions
> + Setting Nagios Core corelog.newobjects user:group permissions
> + Setting CCM configuration file user:group permissions
> + Setting Recurring Downtime file user:group permissions
> + Setting BPI configuration file user:group permissions
--------------------------------------

--- ccm_import.php -------------------
> Setting import directory: /usr/local/nagios/etc/import/
> Importing config files into the CCM
No files to import
--------------------------------------

--- ccm_export.php -------------------
> Writing CCM configuration to Nagios files
PHP Warning: Invalid argument supplied for foreach() in /usr/local/nagiosxi/html/includes/components/nagiosim/nagiosim.inc.php on line 491
Write host configurations ...<br /><span class="verify-ok">Host configuration files successfully written!</span><br /><br />Write service configurations ...<br>Configuration file: <strong>check_mysql_slavestatus.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_httpd.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_cpu_stats.cfg</strong> successfully written!<br>Configuration file: <strong>devops_url_status_qaportal_picasso.cfg</strong> successfully written!<br>Configuration file: <strong>devops_url_content_qaportal_picasso.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_disk_usage_root.cfg</strong> successfully written!<br>Configuration file: <strong>devops_ping.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_disk_usage_home.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_check_swap.cfg</strong> successfully written!<br>Configuration file: <strong>devops_ldap.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_crond.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_memory.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_sshd.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_tftp.cfg</strong> successfully written!<br>Configuration file: <strong>devops_dmz_jira.cfg</strong> successfully written!<br>Configuration file: <strong>devops_dmz_confluence.cfg</strong> successfully written!<br>Configuration file: <strong>devops_linux_diskspace.cfg</strong> successfully written!<br>Configuration file: <strong>devops_linux_http.cfg</strong> successfully written!<br>Configuration file: <strong>devops_win7_cpu_usage.cfg</strong> successfully written!<br>Configuration file: <strong>devops_win7_mem_usage.cfg</strong> successfully written!<br>Configuration file: <strong>devops_win7_uptime.cfg</strong> successfully written!<br>Configuration file: <strong>devops_win7_disk_usage.cfg</strong> successfully written!<br>Configuration file: <strong>devops_dmz_qaportal.cfg</strong> successfully written!<br>Configuration file: <strong>devops_dmz_gosa.cfg</strong> successfully written!<br>Configuration file: <strong>devops_dmz_self_service.cfg</strong> successfully written!<br>Configuration file: <strong>devops_certgen_logfile_age.cfg</strong> successfully written!<br>Configuration file: <strong>CTECH Jira.cfg</strong> successfully written!<br>Configuration file: <strong>www.stb.bskyb.com.cfg</strong> successfully written!<br>Configuration file: <strong>devops_dmz_qastaging.cfg</strong> successfully written!<br>Configuration file: <strong>qastaging.picasso.bskyb.com.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_redis_service.cfg</strong> successfully written!<br>Configuration file: <strong>devops_redis_port.cfg</strong> successfully written!<br>Configuration file: <strong>devops_redis_email_queue.cfg</strong> successfully written!<br>Configuration file: <strong>devops_redis_db_usage.cfg</strong> successfully written!<br>Configuration file: <strong>check_sanswitch_systeminfo.cfg</strong> successfully written!<br>Configuration file: <strong>check_sanswitch_port1-TEST.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_disk_usage_var.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_disk_usage_usr.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_disk_usage_opt.cfg</strong> successfully written!<br>Configuration file: <strong>Synology Status.cfg</strong> successfully written!<br>Configuration file: <strong>devops_dmz_ldap.cfg</strong> successfully written!<br>Configuration file: <strong>certgen_log_errors.cfg</strong> successfully written!<br>Configuration file: <strong>devops_ReadOnly_Synology_ISO_Store_datastore.cfg</strong> successfully written!<br>Configuration file: <strong>devops_3par7008_vsphere_1_datastore.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_bacula_dir.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_bacula_fd.cfg</strong> successfully written!<br>Configuration file: <strong>devops_VM_PicassoAthena_cpu_usage.cfg</strong> successfully written!<br>Configuration file: <strong>devops_VM_PicassoAthena_memory_usage.cfg</strong> successfully written!<br>Configuration file: <strong>devops_tomcat_port.cfg</strong> successfully written!<br>Configuration file: <strong>prd_mysql_connection_time.cfg</strong> successfully written!<br>Configuration file: <strong>prd_mysql_connection_time_raw.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_dmz_usage_apps_ldap.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_disk_usage_bacula_backup-store2-lff.cfg</strong> successfully written!<br>Configuration file: <strong>devops_DMZ_nrpe_memory.cfg</strong> successfully written!<br>Configuration file: <strong>certgen_mnt_backup_mount.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_disk_usage_bacula_backup-store3-lff.cfg</strong> successfully written!<br>Configuration file: <strong>devops_VM_CTA402_Cluster_cpu_usage.cfg</strong> successfully written!<br>Configuration file: <strong>devops_VM_CTA402_Cluster_memory_usage.cfg</strong> successfully written!<br>Configuration file: <strong>devops_3par6977_vsphere_1_datastore.cfg</strong> successfully written!<br>Configuration file: <strong>devops_3par6977_vsphere_2_datastore.cfg</strong> successfully written!<br>Configuration file: <strong>devops_dmz_crowd.cfg</strong> successfully written!<br>Configuration file: <strong>Admin Console.cfg</strong> successfully written!<br>Configuration file: <strong>C Drive Space.cfg</strong> successfully written!<br>Configuration file: <strong>Config Server.cfg</strong> successfully written!<br>Configuration file: <strong>FTP for Daemon Logs.cfg</strong> successfully written!<br>Configuration file: <strong>Uptime.cfg</strong> successfully written!<br>Configuration file: <strong>CPU Load.cfg</strong> successfully written!<br>Configuration file: <strong>Memory Usage.cfg</strong> successfully written!<br>Configuration file: <strong>D Drive Space.cfg</strong> successfully written!<br>Configuration file: <strong>Host Service.cfg</strong> successfully written!<br>Configuration file: <strong>IRNetBox Availability.cfg</strong> successfully written!<br>Configuration file: <strong>StormTest Servers Process.cfg</strong> successfully written!<br>Configuration file: <strong>StormTest HD Video Server One.cfg</strong> successfully written!<br>Configuration file: <strong>StormTest HD Video Server Two.cfg</strong> successfully written!<br>Configuration file: <strong>StormTest HD Video Server Three.cfg</strong> successfully written!<br>Configuration file: <strong>StormTest HD Video Server Four.cfg</strong> successfully written!<br>Configuration file: <strong>devops_3par7008_vsphere_2_datastore.cfg</strong> successfully written!<br>Configuration file: <strong>Confluence DB Connection.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_disk_usage_apps_crowd.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_disk_usage_apps_splunk.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_disk_usage_zorkstore.cfg</strong> successfully written!<br>Configuration file: <strong>devops_d12_web_content_ethan.cfg</strong> successfully written!<br>Configuration file: <strong>devops_d12_web_content_picasso.cfg</strong> successfully written!<br>Configuration file: <strong>devops_fisheye_port.cfg</strong> successfully written!<br>Configuration file: <strong>devops_http_content.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_disk_usage_protexip.cfg</strong> successfully written!<br>Configuration file: <strong>devops_blackduck_postgres.cfg</strong> successfully written!<br>Configuration file: <strong>devops_blackduck_tomcat.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_disk_usage_opt_blackduck.cfg</strong> successfully written!<br>Configuration file: <strong>devops_url_content_qaportal_php.cfg</strong> successfully written!<br>Configuration file: <strong>devops_http_content_jenkins.cfg</strong> successfully written!<br>Configuration file: <strong>devops_dmz_qaportal_brentwood_php.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_disk_usage_zorkstore_picasso.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_disk_usage_protexip_data.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_bucky_service.cfg</strong> successfully written!<br>Configuration file: <strong>devops_http_content_jenkins_8081.cfg</strong> successfully written!<br>Configuration file: <strong>check_hp_ilo.cfg</strong> successfully written!<br>Configuration file: <strong>check_hardware_MSA.cfg</strong> successfully written!<br>Configuration file: <strong>check_rabbitmq_aliveness.cfg</strong> successfully written!<br>Configuration file: <strong>check_rabbitmq_server.cfg</strong> successfully written!<br>Configuration file: <strong>check_rabbitmq_aliveness_vhost.cfg</strong> successfully written!<br>Configuration file: <strong>check_rabbitmq_connections.cfg</strong> successfully written!<br>Configuration file: <strong>check_rabbitmq_objects.cfg</strong> successfully written!<br>Configuration file: <strong>check_rabbitmq_overview.cfg</strong> successfully written!<br>Configuration file: <strong>P2040 Athena Court Storage picasso-store2-vol1.cfg</strong> successfully written!<br>Configuration file: <strong>P2040 AthenaCourt storage picasso-store1-vol1.cfg</strong> successfully written!<br>Configuration file: <strong>devops_dmz_splunk.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_disk_usage_apps_splunkdata.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_disk_usage_apps_logs.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_splunk_process.cfg</strong> successfully written!<br>Configuration file: <strong>devops_meshdata_web_content.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_disk_usage_apps.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_nginx_process.cfg</strong> successfully written!<br>Configuration file: <strong>devops_http_content_skyq_mesh_diag_url_check.cfg</strong> successfully written!<br>Configuration file: <strong>devops_http_content_mesh-diagnostics-chrome_stb_app.cfg</strong> successfully written!<br>Configuration file: <strong>devops_http_content_jenkins_8080.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_picasso_process.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_ethan_process.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_php_process.cfg</strong> successfully written!<br>Configuration file: <strong>devops_url_content_qaportal_ethan.cfg</strong> successfully written!<br>Configuration file: <strong>devops_url_status_qaportal_ethan.cfg</strong> successfully written!<br>Configuration file: <strong>devops_url_status_qaportal_php.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_check_time.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_jenkins_slave_process.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_disk_usage_apps_sftp.cfg</strong> successfully written!<br>Configuration file: <strong>devops_http_content_mesh-diagnostics_analysis.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_disk_usage_apps_mysql.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_vsftpd.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_disk_usage_apps_luna.cfg</strong> successfully written!<br>Configuration file: <strong>devops_meshdata_download_url.cfg</strong> successfully written!<br>Configuration file: <strong>devops_meshdata_upload_url.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_bacula_sd.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nfs_server.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_disk_usage_apps_tftpboot.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_disk_usage_apps_nfsshare.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_disk_usage_apps_jira_attach_bkup.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_splunkd_process.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_disk_usage_apps_streamstore.cfg</strong> successfully written!<br>Configuration file: <strong>P2040 Athena Court Storage picasso-store1-vol2.cfg</strong> successfully written!<br>Configuration file: <strong>devops_3par7008_vsphere_AO.1_datastore.cfg</strong> successfully written!<br>Configuration file: <strong>devops_3par7008_vsphere_AO.7_datastore.cfg</strong> successfully written!<br>Configuration file: <strong>devops_3par7008_vsphere_AO.0_datastore.cfg</strong> successfully written!<br>Configuration file: <strong>devops_3par7008_vsphere_AO.2_datastore.cfg</strong> successfully written!<br>Configuration file: <strong>devops_3par7008_vsphere_AO.3_datastore.cfg</strong> successfully written!<br>Configuration file: <strong>devops_3par7008_vsphere_AO.4_datastore.cfg</strong> successfully written!<br>Configuration file: <strong>devops_3par7008_vsphere_AO.5_datastore.cfg</strong> successfully written!<br>Configuration file: <strong>devops_3par7008_vsphere_AO.6_datastore.cfg</strong> successfully written!<br>Configuration file: <strong>devops_3par7008_vsphere_AO.8_datastore.cfg</strong> successfully written!<br>Configuration file: <strong>devops_3par7008_vsphere_AO.9_datastore.cfg</strong> successfully written!<br>Configuration file: <strong>devops_3par7008_vsphere_AO.10_datastore.cfg</strong> successfully written!<br>Configuration file: <strong>devops_3par7008_vsphere_AO.11_datastore.cfg</strong> successfully written!<br>Configuration file: <strong>devops_3par7008_vsphere_AO.12_datastore.cfg</strong> successfully written!<br>Configuration file: <strong>devops_3par7008_vsphere_AO.13_datastore.cfg</strong> successfully written!<br>Configuration file: <strong>devops_3par7008_vsphere_AO.15_datastore.cfg</strong> successfully written!<br>Configuration file: <strong>devops_3par7008_vsphere_AO.14_datastore.cfg</strong> successfully written!<br>Configuration file: <strong>devops_3par6977_vsphere_AO.0_datastore.cfg</strong> successfully written!<br>Configuration file: <strong>devops_3par6977_vsphere_AO.1_datastore.cfg</strong> successfully written!<br>Configuration file: <strong>devops_3par6977_vsphere_AO.2_datastore.cfg</strong> successfully written!<br>Configuration file: <strong>devops_3par6977_vsphere_AO.3_datastore.cfg</strong> successfully written!<br>Configuration file: <strong>devops_3par6977_vsphere_AO.4_datastore.cfg</strong> successfully written!<br>Configuration file: <strong>devops_3par6977_vsphere_AO.5_datastore.cfg</strong> successfully written!<br>Configuration file: <strong>devops_3par6977_vsphere_AO.6_datastore.cfg</strong> successfully written!<br>Configuration file: <strong>devops_3par6977_vsphere_AO.7_datastore.cfg</strong> successfully written!<br>Configuration file: <strong>devops_3par6977_vsphere_AO.8_datastore.cfg</strong> successfully written!<br>Configuration file: <strong>devops_3par6977_vsphere_AO.9_datastore.cfg</strong> successfully written!<br>Configuration file: <strong>devops_3par6977_vsphere_AO.10_datastore.cfg</strong> successfully written!<br>Configuration file: <strong>devops_3par6977_vsphere_AO.11_datastore.cfg</strong> successfully written!<br>Configuration file: <strong>devops_3par6977_vsphere_AO.12_datastore.cfg</strong> successfully written!<br>Configuration file: <strong>devops_3par6977_vsphere_AO.13_datastore.cfg</strong> successfully written!<br>Configuration file: <strong>devops_3par6977_vsphere_AO.14_datastore.cfg</strong> successfully written!<br>Configuration file: <strong>devops_3par6977_vsphere_AO.15_datastore.cfg</strong> successfully written!<br>Configuration file: <strong>devops_hiabStore_datastore.cfg</strong> successfully written!<br>Configuration file: <strong>devops_jaguarStore_datastore.cfg</strong> successfully written!<br>Configuration file: <strong>devops_vm-store1-vol1_datastore.cfg</strong> successfully written!<br>Configuration file: <strong>devops_vm-store1-vol2_datastore.cfg</strong> successfully written!<br>Configuration file: <strong>devops_vm-store2-vol1_datastore.cfg</strong> successfully written!<br>Configuration file: <strong>devops_vm-store2-vol2_datastore.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_disk_usage_var_lib_mysql.cfg</strong> successfully written!<br>Configuration file: <strong>devops_mysql_connection_time_ssr_db.cfg</strong> successfully written!<br>Configuration file: <strong>devops_mysql_uptime_ssr_db.cfg</strong> successfully written!<br>Configuration file: <strong>devops_mysql_open_connections_ssr_db.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_disk_usage_storage_core.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_disk_usage_storage_db.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_disk_usage_storage_log.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_disk_usage_boot.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_disk_usage_storage_dblog.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_disk_usage_storage_seat.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_disk_usage_storage_netdump.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_disk_usage_storage_autodeploy.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_disk_usage_storage_invsvc.cfg</strong> successfully written!<br>Configuration file: <strong>devops_rce_http_check.cfg</strong> successfully written!<br>Configuration file: <strong>P2040 Athena Court Storage picasso-store2-vol2.cfg</strong> successfully written!<br>Configuration file: <strong>mesh_mysql_long_running_processes.cfg</strong> successfully written!<br>Configuration file: <strong>yard_mysql_long_running_processes.cfg</strong> successfully written!<br>Configuration file: <strong>Mesh celery queue.cfg</strong> successfully written!<br>Configuration file: <strong>Mesh snapshot jobs.cfg</strong> successfully written!<br>Configuration file: <strong>Mesh Viewing Card Lag.cfg</strong> successfully written!<br>Configuration file: <strong>Mesh Reboot Lag.cfg</strong> successfully written!<br>Configuration file: <strong>Mesh Stream Lag.cfg</strong> successfully written!<br>Configuration file: <strong>Mesh AS_SYSTEM_INFO job.cfg</strong> successfully written!<br>Configuration file: <strong>Mesh Data Lag.cfg</strong> successfully written!<br>Configuration file: <strong>devops_http_content_mesh-diagnostics_analysis-background.cfg</strong> successfully written!<br>Configuration file: <strong>Check HTTP URL Generic Content.cfg</strong> successfully written!<br>Configuration file: <strong>devops_http_content_dashq.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_disk_usage_apps_data.cfg</strong> successfully written!<br>Configuration file: <strong>devops_url_content_qaportal_internal_italy.cfg</strong> successfully written!<br>Configuration file: <strong>devops_url_status_qaportal_internal_it.cfg</strong> successfully written!<br>Configuration file: <strong>meshdiag_nrpe_disk_usage_apps_mysql.cfg</strong> successfully written!<br>Configuration file: <strong>meshdiag_nrpe_disk_usage_apps_mysql_backup.cfg</strong> successfully written!<br>Configuration file: <strong>meshdiag_nrpe_disk_usage_apps_mysql_binlog.cfg</strong> successfully written!<br>Configuration file: <strong>SSL certificate validation - 30 day warning.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_mysqld_process.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_disk_usage_owncloud.cfg</strong> successfully written!<br>Configuration file: <strong>devops_mesh_redis_port.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_disk_usage_apps_gitlab.cfg</strong> successfully written!<br>Configuration file: <strong>devops_url_content_qaportal_internal_germany.cfg</strong> successfully written!<br>Configuration file: <strong>devops_dmz_qaportal_staines.cfg</strong> successfully written!<br>Configuration file: <strong>devops_dmz_qaportal_staines_test_results.cfg</strong> successfully written!<br>Configuration file: <strong>devops_http_content_splunk_8000.cfg</strong> successfully written!<br>Configuration file: <strong>devops_http_content_splunk_8089.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_disk_usage_apps_httpd.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_redis_process.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_disk_usage_apps_jenkins.cfg</strong> successfully written!<br>Configuration file: <strong>meshdiag_nrpe_disk_usage_meshd1p_mysql.cfg</strong> successfully written!<br>Configuration file: <strong>meshdiag_nrpe_disk_usage_meshd1p_mysql_backup_copy_1.cfg</strong> successfully written!<br>Configuration file: <strong>meshdiag_nrpe_disk_usage_meshd1p_mysql_binlog.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_skunk_process.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_disk_usage_apps_cttest.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_disk_usage_apps_clash-cache.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_disk_usage_apps_tomcat.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_disk_usage_apps_trials_site.cfg</strong> successfully written!<br>Configuration file: <strong>devops_nrpe_disk_usage_apps_signing-application.cfg</strong> successfully written!<br><span class='urgent'>Cannot open/overwrite service configuration files (check the permissions)!</span><br><span class='successMessage'>Configuration file: <strong>hostgroups.cfg</strong> successfully written!</span><br><span class='successMessage'>Configuration file: <strong>servicegroups.cfg</strong> successfully written!</span><br><span class='successMessage'>Configuration file: <strong>hosttemplates.cfg</strong> successfully written!</span><br><span class='successMessage'>Configuration file: <strong>servicetemplates.cfg</strong> successfully written!</span><br><span class='successMessage'>Configuration file: <strong>timeperiods.cfg</strong> successfully written!</span><br><span class='successMessage'>Configuration file: <strong>commands.cfg</strong> successfully written!</span><br><span class='successMessage'>Configuration file: <strong>contacts.cfg</strong> successfully written!</span><br><span class='successMessage'>Configuration file: <strong>contactgroups.cfg</strong> successfully written!</span><br><span class='successMessage'>Configuration file: <strong>contacttemplates.cfg</strong> successfully written!</span><br><span class='successMessage'>Configuration file: <strong>servicedependencies.cfg</strong> successfully written!</span><br><span class='successMessage'>Configuration file: <strong>hostdependencies.cfg</strong> successfully written!</span><br><span class='successMessage'>Configuration file: <strong>serviceescalations.cfg</strong> successfully written!</span><br><span class='successMessage'>Configuration file: <strong>hostescalations.cfg</strong> successfully written!</span><br><span class='successMessage'>Configuration file: <strong>serviceextinfo.cfg</strong> successfully written!</span><br><span class='successMessage'>Configuration file: <strong>hostextinfo.cfg</strong> successfully written!</span><br>
Writing CCM configuration failed!\n

[root@nagios ~]# ls -al /usr/local/nagios/
total 9260
drwxr-xr-x 9 root root 4096 Jul 27 2016 .
drwxr-xr-x. 20 root root 4096 Jul 10 13:44 ..
-rw-r--r-- 1 root root 9436442 Jul 29 2015 2015-07-290955.tgz
drwxr-xr-x 2 nagios nagios 4096 Jul 20 15:00 bin
drwxrwxr-x 8 apache nagios 4096 Jul 23 10:08 etc
drwxr-xr-x 2 nagios nagcmd 4096 Jun 11 2014 include
drwxrwsr-x 7 nagios nagios 12288 Jul 20 15:00 libexec
drwxrwxr-x 2 nagios nagios 4096 Jul 19 11:13 sbin
drwxrwxr-x 19 nagios nagios 4096 Jul 19 11:13 share
drwxrwxr-x 6 nagios nagios 4096 Jul 30 10:08 var

[root@nagios ~]# ls -al /usr/local/nagios/hosts
ls: cannot access /usr/local/nagios/hosts: No such file or directory

[root@nagios ~]# ls -al /usr/local/nagios/services
ls: cannot access /usr/local/nagios/services: No such file or directory
scottwilkerson
DevOps Engineer
Posts: 19396
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises
Contact:

Re: Upgrade from 5.2.7 to 5.5.0 failed

Post by scottwilkerson »

sorry, I misstyped, but this is where it is erroring

Code: Select all

ls -al /usr/local/nagios/etc/services
Former Nagios employee
Creator:
ahumandesign.com
enneagrams.com
blueagle
Posts: 26
Joined: Mon Feb 17, 2014 4:16 am

Re: Upgrade from 5.2.7 to 5.5.0 failed

Post by blueagle »

Output from the correct directory paths:

[root@nagios ~]# ls -al /usr/local/nagios/etc/hosts/ | wc -l
438
[root@nagios ~]# ls -al /usr/local/nagios/etc/services
total 32
drwxrwxr-x 2 apache nagios 20480 Jul 30 10:58 .
drwxrwxr-x 8 apache nagios 4096 Jul 23 10:08 ..
-rw-rw-r-- 1 root root 1109 Jul 30 10:58 check_mysql_slavestatus.cfg
-rw-rw-r-- 1 apache nagios 1453 Jul 24 09:41 devops_nrpe_check_load.cfg

[root@nagios services]# cat check_mysql_slavestatus.cfg
###############################################################################
#
# Services configuration file
#
# Created by: Nagios CCM 2.7.0
# Date: 2018-07-30 10:58:01
# Version: Nagios Core 4.x
#
# --- DO NOT EDIT THIS FILE BY HAND ---
# Nagios CCM will overwrite all manual settings during the next update if you
# would like to edit files manually, place them in the 'static' directory or
# import your configs into the CCM by placing them in the 'import' directory.
#
###############################################################################

define service {
service_description check_mysql_slavestatus
check_command check_mysql_slavestatus.sh!!nagios!12naggioss!!!!!
max_check_attempts 5
check_interval 5
retry_interval 1
check_period 24x7
notification_period 24x7
register 1
}

###############################################################################
#
# Services configuration file
#
# END OF FILE
#
###############################################################################

[root@nagios services]# cat devops_nrpe_check_load.cfg
###############################################################################
#
# Services configuration file
#
# Created by: Nagios CCM 2.7.0
# Date: 2018-07-24 09:41:11
# Version: Nagios Core 4.x
#
# --- DO NOT EDIT THIS FILE BY HAND ---
# Nagios CCM will overwrite all manual settings during the next update if you
# would like to edit files manually, place them in the 'static' directory or
# import your configs into the CCM by placing them in the 'import' directory.
#
###############################################################################

define service {
service_description Load check
use xiwizard_nrpe_service
check_command check_nrpe!check_load!-a $_HOSTLOAD_CHECK$!!!!!!
max_check_attempts 5
check_interval 5
retry_interval 1
check_period 24x7
notification_interval 1440
first_notification_delay 5
notification_period nagiosadmin_notification_times
notification_options w,c,u,r,f,s,
notifications_enabled 1
contacts nagiosadmin
_xiwizard linux-server
register 1
}

###############################################################################
#
# Services configuration file
#
# END OF FILE
#
###############################################################################

The same checks are working in Nagios 5.2.7.
Is there anything obvious you can see what we need to change before upgrading to 5.5.x?
scottwilkerson
DevOps Engineer
Posts: 19396
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises
Contact:

Re: Upgrade from 5.2.7 to 5.5.0 failed

Post by scottwilkerson »

please change the following owner

Code: Select all

chown apache.nagios /usr/local/nagios/etc/services/check_mysql_slavestatus.cfg
Then go to CCM -. Tools -> Config File Management
Write Configs
Verify Files

If all looks good with out Errors

Apply Configuration
Former Nagios employee
Creator:
ahumandesign.com
enneagrams.com
blueagle
Posts: 26
Joined: Mon Feb 17, 2014 4:16 am

Re: Upgrade from 5.2.7 to 5.5.0 failed

Post by blueagle »

OK did that and its got the right ownership now.
Wrote files and when I verified them got this error.

Error: Service has no hosts and/or service_description (config file '/usr/local/nagios/etc/services/devops_nrpe_check_load.cfg', starting on line 16)
Error: Service escalation host name or description is NULL
Error: Could not register service escalation (config file '/usr/local/nagios/etc/serviceescalations.cfg', starting on line 16)

[nagios@nagios ~]$ ll /usr/local/nagios/etc/services
total 12
-rw-rw-r-- 1 apache nagios 1109 Jul 30 10:58 check_mysql_slavestatus.cfg
-rw-rw-r-- 1 apache nagios 1453 Jul 24 09:41 devops_nrpe_check_load.cfg
-rw-rw-r-- 1 apache apache 1481 Aug 1 09:28 devops_nrpe_httpd.cfg

Contents of the service its complaining about:

[nagios@nagios ~]$ cat /usr/local/nagios/etc/services/devops_nrpe_check_load.cfg
###############################################################################
#
# Services configuration file
#
# Created by: Nagios CCM 2.7.0
# Date: 2018-07-24 09:41:11
# Version: Nagios Core 4.x
#
# --- DO NOT EDIT THIS FILE BY HAND ---
# Nagios CCM will overwrite all manual settings during the next update if you
# would like to edit files manually, place them in the 'static' directory or
# import your configs into the CCM by placing them in the 'import' directory.
#
###############################################################################

define service {
service_description Load check
use xiwizard_nrpe_service
check_command check_nrpe!check_load!-a $_HOSTLOAD_CHECK$!!!!!!
max_check_attempts 5
check_interval 5
retry_interval 1
check_period 24x7
notification_interval 1440
first_notification_delay 5
notification_period nagiosadmin_notification_times
notification_options w,c,u,r,f,s,
notifications_enabled 1
contacts nagiosadmin
_xiwizard linux-server
register 1
}

###############################################################################
#
# Services configuration file
#
# END OF FILE
#
###############################################################################
scottwilkerson
DevOps Engineer
Posts: 19396
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises
Contact:

Re: Upgrade from 5.2.7 to 5.5.0 failed

Post by scottwilkerson »

Go to CCM -> Services -> Select Template Edit devops_nrpe_check_load
Edit Load check
You need to add a host or disable this service

Also look at your service escalations in the CCM, there is an escalation that has something misconfigured.
Former Nagios employee
Creator:
ahumandesign.com
enneagrams.com
blueagle
Posts: 26
Joined: Mon Feb 17, 2014 4:16 am

Re: Upgrade from 5.2.7 to 5.5.0 failed

Post by blueagle »

I have had a look at this service, its got 2 hosts and 4 host groups assigned to it.

There's only one service in service escalations so I disabled it.
Tried to apply configuration and I got this:

Reset config permissions failed.
An error occurred while attempting to apply your configuration to Nagios Core. Monitoring engine configuration files have been rolled back to their last known good checkpoint.

Error: Service description missing from list '' (config file '/usr/local/nagios/etc/servicegroups.cfg', starting at line 37)
Error: Could not expand members specified in servicegroup 'Splunk Servers' (config file '/usr/local/nagios/etc/servicegroups.cfg', starting at line 37)
Error: Service escalation host name or description is NULL
Error: Could not register service escalation (config file '/usr/local/nagios/etc/serviceescalations.cfg', starting on line 16)

Do you know why we're seeing all these errors in 5.5 but don't see them in 5.2.7?
scottwilkerson
DevOps Engineer
Posts: 19396
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises
Contact:

Re: Upgrade from 5.2.7 to 5.5.0 failed

Post by scottwilkerson »

go to Admin -> Security Credentials
Click Update Credentials

Then run the following and return output

Code: Select all

/usr/local/nagiosxi/scripts/reconfigure_nagios.sh
the above may resolve the issue, if it does we will not need to see the output, but if I fails, send the output of the above command in your response
Former Nagios employee
Creator:
ahumandesign.com
enneagrams.com
pdd-devops
Posts: 7
Joined: Tue Jul 24, 2018 2:37 am

Re: Upgrade from 5.2.7 to 5.5.0 failed

Post by pdd-devops »

I tried this on Friday and tried it again but when I run the script this is what I'm getting:

/usr/local/nagiosxi/scripts/reconfigure_nagios.sh

--- reset_config_perms.sh ------------
> Setting CCM script permissions
> Setting script permissions
> Setting special component script permissions
> Setting configuration file/directory permissions
> Setting perfdata directory and RRD permissions
> Setting NOM checkpoint user:group permissions
> + Setting Nagios Core corelog.newobjects user:group permissions
> + Setting CCM configuration file user:group permissions
> + Setting Recurring Downtime file user:group permissions
> + Setting BPI configuration file user:group permissions
--------------------------------------

--- ccm_import.php -------------------
> Setting import directory: /usr/local/nagios/etc/import/
> Importing config files into the CCM
No files to import
--------------------------------------
Another reconfigure process is still running, sleeping...
Another reconfigure process is still running, sleeping...

I've even rebooted the VM but no luck. I'm not sure which process is blocking it?
scottwilkerson
DevOps Engineer
Posts: 19396
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises
Contact:

Re: Upgrade from 5.2.7 to 5.5.0 failed

Post by scottwilkerson »

please run the following

Code: Select all

rm -f /usr/local/nagiosxi/scripts/reconfigure_nagios.lock
then try again
Former Nagios employee
Creator:
ahumandesign.com
enneagrams.com
Locked