FOSS upgrade fails

[buraglio]

Originally Posted by jholder

man o man

can you do a (as root)
rpm -qa | grep zimbra
and paste the output?

Also, do you have a backup? (please say yes)

It is a debian system so I don't use rpm, but I think the equiv command would be this:

# dpkg -l | grep zimbra
ii zimbra-apache 5.0.2_GA_1975.DEBIAN4.0 Best email money can buy
ii zimbra-core 5.0.2_GA_1975.DEBIAN4.0 Best email money can buy
ii zimbra-ldap 5.0.2_GA_1975.DEBIAN4.0 Best email money can buy
ii zimbra-logger 5.0.2_GA_1975.DEBIAN4.0 Best email money can buy
ii zimbra-mta 5.0.2_GA_1975.DEBIAN4.0 Best email money can buy
ii zimbra-snmp 5.0.2_GA_1975.DEBIAN4.0 Best email money can buy
ii zimbra-spell 5.0.2_GA_1975.DEBIAN4.0 Best email money can buy
ii zimbra-store 5.0.2_GA_1975.DEBIAN4.0 Best email money can buy



To answer your other question, Yes, I have both a snapshot (it's a VM) and a backup. I also have a fresh VM ready that has the GA version installed that I could dump the DB to if it isn't corrupt and I could learn how (this was the plan to learn backup/restore). This machine, however, is not production so I am more interested in just cutting my teeth on the internals and learning how everything is tied together.
I figure it can't hurt to try and debug a PITA problem now and that way I can learn how the guts work a little better, maybe help someone with the same problem in the future and exercise my brain a little on something I don't normally work on.

Your help is greatly appreciated.

[buraglio]

Originally Posted by bobby

It looks like the problem was always with the logger mysql password. I think the mailbox mysql migration is done. Let's check the database:

# su - zimbra
$ mysql zimbra
> select * from config;
> describe scheduled_task;

As requested:

mysql> select * from config;
+-----------------+-------+-------------------+---------------------+
| name | value | description | modified |
+-----------------+-------+-------------------+---------------------+
| db.version | 48 | db schema version | 2007-11-26 09:02:47 |
| index.version | 2 | index version | 2007-11-26 09:02:47 |
| redolog.version | 1.21 | redolog version | 2007-11-26 09:02:47 |
+-----------------+-------+-------------------+---------------------+
3 rows in set (0.01 sec)

mysql> describe scheduled_task;
+-----------------+------------------+------+-----+---------+-------+
| Field | Type | Null | Key | Default | Extra |
+-----------------+------------------+------+-----+---------+-------+
| class_name | varchar(255) | NO | PRI | | |
| name | varchar(255) | NO | PRI | | |
| mailbox_id | int(10) unsigned | NO | PRI | | |
| exec_time | datetime | YES | | NULL | |
| interval_millis | int(10) unsigned | YES | | NULL | |
| metadata | mediumtext | YES | | NULL | |
+-----------------+------------------+------+-----+---------+-------+
6 rows in set (0.03 sec)

I think you could make a copy of zmsetup.pl, comment out everything in the applyConfig subroutine up to "configInitLogger();", and then run that (Brian, please correct me if I'm wrong).

I made the edits and ran the script and got this result:

Operations logged to /tmp/zmsetup.02142008-064153.log
Starting ldap...done.
Setting defaults...done.
Upgrading from to 5.0.2_GA_1975
Stopping zimbra services
Verifying /opt/zimbra/conf/my.cnf
Starting mysql
Starting logger mysql
Thu Feb 14 06:43:33 2008: SELECT value FROM config WHERE name = 'db.version'
I can't upgrade version

UPGRADE FAILED - exiting

[buraglio]

I went ahead and reverted to my snapshot but I did copy the VM so that I can continue working on it. At some point I'd really like to upgrade to the newer version so that I can go through the upgrade process.

In general, is the Network Edition a smoother upgrade since it is commercially supported and not an RC?

[wdimmit]

I've got a similar problem to the initial poster. I've got a 4.5.6 FOSS install running on CentOS 5 that presents the same error on upgrade

Upgrading from  to 4.5.6_GA_1044
Stopping zimbra services
Verifying /opt/zimbra/conf/my.cnf
Starting mysql
Starting logger mysql
I can't upgrade version

UPGRADE FAILED - exiting

The above is from an attempt to upgrade over the top of my install, but I've tried 4.5.8, 4.5.10 and 5.0.2 all with the same result. When watching the console I also see "SELECT value FROM config WHERE name = 'db.version'" every time. I've reset both mysql passwords and the ldap password.

I've been unable to find a resolution in the forums here, so I'd appreciate any advice I can get.

--Will