Errors on Upgrage to XI 1.4

[chrisp]

We saw several errors on upgrade from 1.3 to 1.4 and I just wanted to post them here to make sure that they're "OK"...

Should we worry about this lot?

Code: Select all

Applying NDOUtils patch level 103
        ALTER TABLE `nagios_logentries` DROP INDEX `logentry_time_2` ;
        SQL:    SQL Error [ndoutils] :</b> Can't DROP 'logentry_time_2'; check that column/key exists   ALTER TABLE `nagios_logentries` DROP INDEX `logentry_data_2` ;
        SQL:    SQL Error [ndoutils] :</b> Can't DROP 'logentry_data_2'; check that column/key exists   ALTER TABLE `nagios_logentries` DROP INDEX `instance_id_2` ;
        SQL:    SQL Error [ndoutils] :</b> Can't DROP 'instance_id_2'; check that column/key exists     ALTER TABLE `nagios_statehistory` DROP INDEX `state_time_2`  ;
        SQL:    SQL Error [ndoutils] :</b> Can't DROP 'state_time_2'; check that column/key exists      ALTER TABLE `nagios_statehistory` DROP INDEX `object_id_2`  ;
        SQL:    SQL Error [ndoutils] :</b> Can't DROP 'object_id_2'; check that column/key exists       ALTER TABLE `nagios_notifications` DROP INDEX `start_time_2` ;
        SQL:    SQL Error [ndoutils] :</b> Can't DROP 'start_time_2'; check that column/key exists      ALTER TABLE `nagios_notifications` DROP INDEX `object_id_2`  ;
        SQL:    SQL Error [ndoutils] :</b> Can't DROP 'object_id_2'; check that column/key exists       ALTER TABLE `nagios_notifications` DROP INDEX `instance_id_2`  ;
        ALTER TABLE `nagios_contactnotifications` DROP INDEX `notification_id_2`  ;
        SQL:    SQL Error [ndoutils] :</b> Can't DROP 'notification_id_2'; check that column/key exists ALTER TABLE `nagios_contactnotifications` DROP INDEX `contact_object_id_2`  ;
        SQL:    SQL Error [ndoutils] :</b> Can't DROP 'contact_object_id_2'; check that column/key exists       ALTER TABLE `nagios_contactnotificationmethods` DROP INDEX `contactnotification_id_2`  ;
        SQL:    SQL Error [ndoutils] :</b> Can't DROP 'contactnotification_id_2'; check that column/key exists  ALTER TABLE `nagios_objects` DROP INDEX `objecttype_id_2` ;
        SQL:    SQL Error [ndoutils] :</b> Can't DROP 'objecttype_id_2'; check that column/key exists   ALTER TABLE `nagios_objects` DROP INDEX `name1_2` ;
        SQL:    SQL Error [ndoutils] :</b> Can't DROP 'name1_2'; check that column/key exists   ALTER TABLE `nagios_objects` DROP INDEX `name2_2` ;
        SQL:    SQL Error [ndoutils] :</b> Can't DROP 'name2_2'; check that column/key exists   ALTER TABLE `nagios_objects` DROP INDEX `is_active_2` ;
        SQL:    SQL Error [ndoutils] :</b> Can't DROP 'is_active_2'; check that column/key exists       ALTER TABLE `nagios_timedeventqueue` DROP INDEX `queued_time_2` ;
        SQL:    SQL Error [ndoutils] :</b> Can't DROP 'queued_time_2'; check that column/key exists     ALTER TABLE `nagios_timedevents` DROP INDEX `queued_time_2` ;
        SQL:    SQL Error [ndoutils] :</b> Can't DROP 'queued_time_2'; check that column/key existsNDOUtils patched to level 103 successfully.

Linux Distro: CentOS release 6.3 (Final)
Architechure: x86_64
Nagios Core 3.4.1
Installation: Manual
SSL Enabled: Yes

###################################
# Nagios XI version information
###################################
full=2012R1.4
major=2012
minor=R1.4
releasedate=2013-01-16
release=304

[abrist]

These actually aren't "errors" as this portion of the script runs through to find and delete duplicate indexes in the database. If you are worried, you can always run a database repair:

Code: Select all

/usr/local/nagiosxi/scripts/repairmysql.sh

[chrisp]

Thanks,

I just ran the database repair, so hopefully there's no real problem.

Part of my worries were that I also noticed that soon after the upgrade, while trying to use the Core Config Manager to add new services, I was regularly seeing a "Cannot connect to database" error, when submitting my changes. I've never seen this message before.

I was not sure if this was due to a problem introduced by the upgrade or the excessively high load average (6-27) we're seeing (even before the upgrade)...

[lmiltchev]

Actually, you need to specify the database, so run the following command instead:

Code: Select all

/usr/local/nagiosxi/scripts/repairmysql.sh nagios

[chrisp]

Yep, I ran it with no arguments, then followed the usage instructions, as you mentioned.

[scottwilkerson]

you should be good. As abrist had mentioned these aren't "errors", and are a natural output of the upgrade script.