failing to upgrade

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Locked
gornm565
Posts: 72
Joined: Tue Nov 15, 2016 6:11 pm

failing to upgrade

Post by gornm565 »

Trying to upgrade to the latest version from the previous version and it fails:


sh ./upgrade.sh
Removing the old /tmp/nagiosxi directory, and xi-* tarball
Downloading latest Nagios XI release
--2019-08-23 22:26:32-- https://assets.nagios.com/downloads/nag ... est.tar.gz
Resolving assets.nagios.com... 72.14.181.71, 2600:3c00::f03c:91ff:fedf:b821
Connecting to assets.nagios.com|72.14.181.71|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 58145699 (55M) [application/x-gzip]
Saving to: “/tmp/xi-latest.tar.gz”

100%[=========================================================================================================>] 58,145,699 33.5M/s in 1.7s

2019-08-23 22:26:34 (33.5 MB/s) - “/tmp/xi-latest.tar.gz” saved [58145699/58145699]

Running upgrade
Nagios XI Upgrade Log
==========================
DATE: Fri Aug 23 22:26:37 EDT 2019

DISTRO INFO:
CentOS
6.10
x86_64


Archive: sourceguardian/ixed4.lin.x86-64.zip
inflating: /usr/lib64/php/modules/ixed.5.3.lin
Sourceguardian extension found for PHP version 5.3
Sourceguardian extension already in php.ini
Stopping httpd: [ OK ]
Starting httpd: [ OK ]
Checking required prereqs...
Please wait...

OLD VERSION: 5605
Loaded plugins: fastestmirror
Setting up Update Process
Determining fastest mirrors
* base: mirror.cc.columbia.edu
* epel: epel.mirror.constant.com
* extras: mirror.cc.columbia.edu
* updates: mirror.cc.columbia.edu
https://epel.mirror.constant.com/6/x86_ ... repomd.xml: [Errno 14] Peer cert cannot be verified or peer cert invalid
Trying other mirror.
It was impossible to connect to the CentOS servers.
This could mean a connectivity issue in your environment, such as the requirement to configure a proxy,
or a transparent proxy that tampers with TLS security, or an incorrect system clock.
You can try to solve this issue by using the instructions on https://wiki.centos.org/yum-errors
If above article doesn't help to resolve this issue please use https://bugs.centos.org/.

No Packages marked for Update
Loaded plugins: fastestmirror
Setting up Install Process
Loading mirror speeds from cached hostfile
* base: mirror.cc.columbia.edu
* epel: epel.mirror.constant.com
* extras: mirror.cc.columbia.edu
* updates: mirror.cc.columbia.edu
Package php-imap-5.3.3-49.el6.x86_64 already installed and latest version
Nothing to do
no crontab for nagios
no crontab for root
Copying over new XI directory...
Patching NDOUtils...
NDOUtils already patched at level 103
Updating sequences...
Nagios XI Postgres Database Sequence Information

OLD VALUES
--------------
xi_commands_command_id_seq = 14532
xi_events_event_id_seq = 1398037
xi_meta_meta_id_seq = 1398368
xi_options_option_id_seq = 177
xi_sysstat_sysstat_id_seq = 101
xi_usermeta_usermeta_id_seq = 1972
xi_users_user_id_seq = 85

NEW VALUES
--------------
xi_commands_command_id_seq = 14532
xi_events_event_id_seq = 1398037
xi_meta_meta_id_seq = 1398368
xi_options_option_id_seq = 177
xi_sysstat_sysstat_id_seq = 101
xi_usermeta_usermeta_id_seq = 1972
xi_users_user_id_seq = 85

Installing new PNP templates...
Enabling large install tweaks...
Fixing config file permissions...
Fixing htpasswd permissions...
Checking group memberships...
Installing new XI templates...

--- reset_config_perms.sh ------------
> Setting script permissions
> Setting CCM script permissions
> Setting special script permissions
> Setting special component script permissions
> Setting configuration file/directory permissions
> Setting perfdata directory and RRD permissions
> Setting libexec directory permissions
> Setting Nagios XI config 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
- Importing: /usr/local/nagios/etc/import/xi_timeperiod_24x7.cfg .. SUCCESS
--------------------------------------

--- ccm_export.php -------------------
> Writing CCM configuration to Nagios files
Finished writing out configuraton
--------------------------------------

--------------------------------------
> Verifying configuration with Nagios Core
> Output:
Nagios Core 4.4.3
Copyright (c) 2009-present Nagios Core Development Team and Community Contributors
Copyright (c) 1999-2009 Ethan Galstad
Last Modified: 2019-01-15
License: GPL

Website: https://www.nagios.org
Reading configuration data...
Read main config file okay...
Error: Contact 'xi_default_contact' is not defined anywhere!
Error: Could not add contact 'xi_default_contact' to host (config file '/usr/local/nagios/etc/hosts/172.16.24.1.cfg', starting on line 16)
Error processing object config files!


***> One or more problems was encountered while processing the config files...

Check your configuration file(s) to ensure that they contain valid
directives and data definitions. If you are upgrading from a previous
version of Nagios, you should be aware that some variables/definitions
may have been removed or modified in this version. Make sure to read
the HTML documentation regarding the config files, as well as the
'Whats New' section to find out what has changed.
> Return Code: 1
--------------------------------------
/usr/local/nagiosxi/nom/checkpoints/nagioscore/errors /usr/local/nagiosxi/scripts
tar: Removing leading `/' from member names
/usr/local/nagiosxi/scripts
LATEST NOM SNAPSHOT: /usr/local/nagiosxi/nom/checkpoints/nagioscore/1566607922.tar.gz
/ /usr/local/nagiosxi/scripts
RESTORING NOM SNAPSHOT : /usr/local/nagiosxi/nom/checkpoints/nagioscore/1566607922.tar.gz
/usr/local/nagiosxi/scripts

--- reset_config_perms.sh ------------
> Setting script permissions
> Setting CCM script permissions
> Setting special script permissions
> Setting special component script permissions
> Setting configuration file/directory permissions
> Setting perfdata directory and RRD permissions
> Setting libexec directory permissions
> Setting Nagios XI config 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
User avatar
cdienger
Support Tech
Posts: 5045
Joined: Tue Feb 07, 2017 11:26 am

Re: failing to upgrade

Post by cdienger »

Edit the 172.16.24.1 host(Configure > Core Config Manager > Monitoring > Hosts) and remove xi_default_contact from the contacts list or add a contact called xi_default_contact(Configure > Core Config Manager > Alerting > Contacts), and the try running the upgrade script again.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Locked