FOSS upgrade fails

[buraglio]

--Edit: The topic should be Open Source Version Upgrade, OS makes it sound like the operating system. There was no operating system upgrade. Sorry for the confusion.

I've done a little searching and really not found a good answer as to how to remedy my issue, so here is my first post.
Please bear in mind that I've been a router jockey for the last 8 years and don't really have any current mail admin experience.
That said, I have a machine (Debian 4.0 2.6.18-5-486) that had been running a pilot of ZCS that I moved to a new subnet and also tried to upgrade (yeah, I know, I tried to make too many changes at once). Anyway, I'm now seeing this error:
<snip>

Restoring existing configuration file from /opt/zimbra/.saveconfig/config.save...done
Operations logged to /tmp/zmsetup.02122008-071935.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
Tue Feb 12 07:21:01 2008: SELECT value FROM config WHERE name = 'db.version'
ERROR 1045 (28000): Access denied for user 'zimbra'@'localhost' (using password: YES)
I can't upgrade version 
UPGRADE FAILED - exiting

</snip>

The versions are as such:
from version zcs-5.0.0_RC2_1745.DEBIAN4.0.20071120152822
to version zcs-5.0.2_GA_1975.DEBIAN4.0.20080130234700

All upgrade aspects appear to be fine until this one fails.
I can start zimbra (after adjusting the postfix version using "zmlocalconfig -f -e postfix_version='2.4.3.4z'") but can't seem to do anything frm the web interface (authentication fails) and the admin page shows nothing at al (i.e. no login area).
I'm not afraid to get my hands dirty working on this if someone can point me in the right direction.
Any help apreciated, Thanks in advance.

nb

[buraglio]

Has anyone else seen this issue? Even an acknowledgement that I'm not just doing something stupid would be mildly helpful. I stepped away from it for most of yesterday since it was just a pilot system but we are very likely purchasing the Network Edition as a replacement for our current system (pricing has already been worked out) and I would really like to think that the upgrades go a little smoother than this. At this point I'm *really* hoping that it's just me, that I've missed reading something, not searched enough or just plain done something incorrectly.

nb

[jholder]

Looks like youre mysql password got out of sync. This can happen if an installation fails or is restarted multiple times.

Take a look here for more help:
Resetting LDAP & MySQL Passwords - Zimbra :: Wiki

[buraglio]

Good lead. I ran:

zmmylogpasswd --root newpassword
zmmypasswd newpasswd
and
zmmypasswd --root newpassword

All were successful. Running the install.sh and choosing yes to upgrade yielded the same results:

Restoring existing configuration file from /opt/zimbra/.saveconfig/config.save...done
Operations logged to /tmp/zmsetup.02132008-043152.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
Wed Feb 13 04:33:10 2008: SELECT value FROM config WHERE name = 'db.version'
ERROR 1045 (28000): Access denied for user 'zimbra'@'localhost' (using password: YES)
I can't upgrade version 

UPGRADE FAILED - exiting

It looks like the versions that would currently run are the newer versions but this error is apparently killing any chance of the service actually working.

[buraglio]

I also tried:
zmmylogpasswd newpasswd
which was successful, then ran the install.sh script again and got a slightly different error:

Restoring existing configuration file from /opt/zimbra/.saveconfig/config.save...done
Operations logged to /tmp/zmsetup.02132008-051021.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
Wed Feb 13 05:11:40 2008: SELECT value FROM config WHERE name = 'db.version'
I can't upgrade version 

UPGRADE FAILED - exiting

So, the db access error seems to have resolved but the underlying problem is still there in that it doesn't like or can't find the the db.version.
Can this be changed or reset manually?

[buraglio]

Some more potentially helpful info:

"zmcontrol -v" yields:
Release 5.0.2_GA_1975.DEBIAN4.0 DEBIAN4.0

su - zimbra
mysql.server start
cd /opt/zimbra/libexec/scripts
./migrate20070703-ScheduledTaskIndex.pl
Wed Feb 13 05:32:42 2008: Schema version mismatch. Expected version 42. Version in the database is 48.

[buraglio]

I'm clearly operating beyond my knowledge level here but it *looks* like in /opt/zimbra/libexec/scripts/Migrate.pm it is looking for certain db versions for various databases and that maybe the db that I have is either
1. Already upgraded to the newer version, therefore it errors out and doesn't need to upgrade.
2. has some random version number outside the threshold of what the scripts are looking for
3. I have no idea what I'm talking about and the versions numbers are a crazy variable that I don't comprehend.

At this point it's really just a personal mission to understand it.

Any insight? Anyone? Bueller?

[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)

[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;

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).

[jholder]

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;

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).

Bobby's right! I didn't realize it was the logger. I assumed it was your db for the mailstore.
Great catch!