Upgrade to 4.5rc2 failed miserably

[mcevoys]

Running 4.04 on FC5 happily for a few months.

Decided to try the upgrade to 4.5rc2 to see how it goes....It doesn't. See error below.

I tried the zmsetup.pl -c config.xxxx trick, but it didn't get any further
Reboot of the system doesn't help.

Tried running install.sh multiple times with no change.

After zmsetup.pl, I can start the servers, and zmcontrol status shows all running, but the client gets nothing but SOAP errors.

Rolling back to 4.04 for now, but any ideas?

__________________________________________________ _______________________________________

Setting defaults...Setting defaults from existing config...Done
Upgrading from 4.0.4_GA_457 to 4.5.0_RC2_566
Sun Jan 14 17:27:27 2007: Stopping zimbra services
Sun Jan 14 17:27:37 2007: Starting mysql
Sun Jan 14 17:27:54 2007: Starting logger mysql
Sun Jan 14 17:28:09 2007: SELECT value FROM config WHERE name = 'db.version'
This appears to be 4.0.4_GA
Exception in thread "main" java.lang.NoClassDefFoundError: com/zimbra/cs/backup/util/GetVersion
Sun Jan 14 17:28:15 2007: Backup Version: New Backup Version:
Sun Jan 14 17:28:15 2007: Redolog Version: New Redolog Version: 1.11
Schema upgrade required
Sun Jan 14 17:28:15 2007: Running /opt/zimbra/libexec/scripts/migrate20060911-MailboxGroup.pl
Sun Jan 14 17:28:19 2007: Verified schema version 27.
Executing SQL statements in /tmp/migrate-MailboxGroup.sql
--------------
ALTER TABLE zimbra.mailbox
ADD COLUMN group_id INTEGER UNSIGNED NOT NULL AFTER id
--------------

ERROR 1060 (42S21) at line 2: Duplicate column name 'group_id'
mysql invication failed, exit code = 1: at /opt/zimbra/libexec/scripts/migrate20060911-MailboxGroup.pl line 84,

line 38.
Sun Jan 14 17:28:22 2007: Script failed with code 1 - exiting
UPGRADE FAILED - exiting

[mcevoys]

I rolled back to 4.04, checked that all was well, then tried a quick upgrade to 4.05GA.

4.05GA upgrade went fine, so the server currently lives at that level until I can figure out what went wrong and how to (safely) get to 4.5.

[mcevoys]

Can someone please take a quick look at this before I attempt 4.5GA?

I'd be disappointed if I had to roll back a second time.

[mcevoys]

Couldn't wait for a forum response, since none seems forthcoming, so I tried the 4.05 to 4.50GA upgrade.

Failed miserably again with the same errors as above.

Can *anyone* please point me in the direction of a solution? There are 4.5 features that are fairly important to me and my user base.

I said please this time!!

_________________________________

zmsetup.log is uninformative:

Setting defaults...
Setting local config zimbra_java_home to /opt/zimbra/java

*** Running as zimbra user: /opt/zimbra/bin/zmlocalconfig -f -e zimbra_java_home=/opt/zimbra/java

Setting defaults from existing config...
Getting local config zimbra_server_hostname

Getting local config ldap_master_url

Getting local config ldap_port

Getting local config ldap_root_password

Getting local config mysql_root_password

Getting local config mysql_logger_root_password

Getting local config zimbra_mysql_password

Getting local config zimbra_logger_mysql_password

Done

Upgrading from 4.0.5_GA_518 to 4.5.0_GA_612

UPGRADE FAILED - exiting

___________________________________________

.install_history is equally unimpressive:

1169080419: INSTALL SESSION START
1169080449: UPGRADED zimbra-core-4.5.0_GA_612.FC5-20070115195533.i386.rpm
1169080453: UPGRADED zimbra-ldap-4.5.0_GA_612.FC5-20070115195533.i386.rpm
1169080462: UPGRADED zimbra-logger-4.5.0_GA_612.FC5-20070115195533.i386.rpm
1169080478: UPGRADED zimbra-mta-4.5.0_GA_612.FC5-20070115195533.i386.rpm
1169080482: UPGRADED zimbra-snmp-4.5.0_GA_612.FC5-20070115195533.i386.rpm
1169080501: UPGRADED zimbra-store-4.5.0_GA_612.FC5-20070115195533.i386.rpm
1169080507: UPGRADED zimbra-apache-4.5.0_GA_612.FC5-20070115195533.i386.rpm
1169080516: UPGRADED zimbra-spell-4.5.0_GA_612.FC5-20070115195533.i386.rpm
1169080516: INSTALL SESSION COMPLETE

(CONFIG SESSION never logs)

[brian]

When upgrading to the GA version did you get the same duplicate group_id that you got when upgrading to RC2? Unfortunately that error is only logged to stdout.

[mcevoys]

Yes..same error.

[brian]

Typically these types of failures occur when a schema migration is interrupted mid-upgrade and the best way to recover is to revert to the previous version and rerun the upgrade.

After you revert to 4.0.5, we'd like to see a description of the schema for the mailbox table before proceeding.

su - zimbra
mysql -Dzimbra -e 'describe mailbox'

[mcevoys]

Back on 4.05:

mysql -Dzimbra -e 'describe mailbox'

+--------------------+---------------------+------+-----+---------+-------+
| Field | Type | Null | Key | Default | Extra |
+--------------------+---------------------+------+-----+---------+-------+
| id | int(10) unsigned | | PRI | 0 | |
| account_id | varchar(36) | | UNI | | |
| index_volume_id | tinyint(3) unsigned | | MUL | 0 | |
| item_id_checkpoint | int(10) unsigned | | | 0 | |
| contact_count | int(10) unsigned | YES | | 0 | |
| size_checkpoint | bigint(20) unsigned | | | 0 | |
| change_checkpoint | int(10) unsigned | | | 0 | |
| tracking_sync | int(10) unsigned | | | 0 | |
| tracking_imap | tinyint(1) | | | 0 | |
| comment | varchar(255) | YES | | NULL | |
+--------------------+---------------------+------+-----+---------+-------+

[mcevoys]

Rerunning the upgrade results the same

Definition of crazy...doing the same thing again and expecting a different outcome ;-)

[jholder]

Have you tried running the 4.0.5 setup as an upgrade?