Upgrade from 4.5.11 -> 5.0.8 FAILED

[RaNd]

Original version was FOSS 4.5.5, upgrade to 5.x.x failed . .
Successfully upgraded to 4.5.11....

I've been trying for more than 1 week . . .


Setting defaults from saved config in /opt/zimbra/.saveconfig/config.save
HOSTNAME=hermes.domain.gr
LDAPHOST=hermes.domain.gr
LDAPPORT=389
SNMPTRAPHOST=hermes.domain.gr
SMTPSOURCE=admin@hermes.domain.gr
SMTPDEST=admin@hermes.domain.gr
SNMPNOTIFY=yes
SMTPNOTIFY=yes
LDAPROOTPW=password
LDAPZIMBRAPW=password
LDAPPOSTPW= <- Should it be blank ???
LDAPREPPW= <- Should it be blank ???
LDAPAMAVISPW= <- Should it be blank ???
Restoring existing configuration file from /opt/zimbra/.saveconfig/config.save...done
Operations logged to /tmp/zmsetup.01001900-0000139079552.log
Starting ldap...done.
ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.AuthenticationException [LDAP: error code 49 - Invalid Credentials])
ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.AuthenticationException [LDAP: error code 49 - Invalid Credentials])
Setting defaults...ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.AuthenticationException [LDAP: error code 49 - Invalid Credentials])
done.
Upgrading from 4.5.11_GA_1751 to 5.0.8_GA_2462
Stopping zimbra services
Verifying /opt/zimbra/conf/my.cnf
Starting mysql
Starting logger mysql
Thu Jul 31 12:32:21 2008: SELECT value FROM config WHERE name = 'db.version'
This appears to be 4.5.11_GA
Redolog Version: 1.12 New Redolog Version: 1.22
Thu Jul 31 12:32:23 2008: Verified redolog version 1.12.
Thu Jul 31 12:32:23 2008: Updating Redolog schema version from 1.12 to 1.22.
Schema upgrade required
Running /opt/zimbra/libexec/scripts/migrate20070306-Pop3MessageUid.pl
Thu Jul 31 12:32:26 2008: Verified schema version 36.
Thu Jul 31 12:33:49 2008: Verified schema version 36.
Thu Jul 31 12:33:49 2008: Updating DB schema version from 36 to 37.
Running /opt/zimbra/libexec/scripts/migrate20070606-WidenMetadata.pl
Thu Jul 31 12:34:39 2008: Verified schema version 37.
[...................................]
Thu Jul 31 12:35:24 2008 Thu Jul 31 12:35:24 2008: Verified schema version 40.
Thu Jul 31 12:35:25 2008 Thu Jul 31 12:35:25 2008: Verified schema version 40.
Thu Jul 31 12:35:25 2008 Thu Jul 31 12:35:25 2008: Updating DB schema version from 40 to 41.
Thu Jul 31 12:35:25 2008 Running /opt/zimbra/libexec/scripts/migrate20070630-LastSoapAccess.pl
Thu Jul 31 12:35:27 2008 Thu Jul 31 12:35:27 2008: Verified schema version 41.
Thu Jul 31 12:35:30 2008 Thu Jul 31 12:35:30 2008: Verified schema version 41.
Thu Jul 31 12:35:30 2008 Thu Jul 31 12:35:30 2008: Updating DB schema version from 41 to 42.
Thu Jul 31 12:35:31 2008 Running /opt/zimbra/libexec/scripts/migrate20070703-ScheduledTask.pl
Thu Jul 31 12:35:33 2008 Thu Jul 31 12:35:33 2008: Verified schema version 42.
Thu Jul 31 12:35:33 2008 ERROR 1050 (42S01) at line 1: Table 'scheduled_task' already exists
Thu Jul 31 12:35:33 2008 Thu Jul 31 12:35:33 2008: Error while running '/opt/zimbra/bin/mysql --user=zimbra --password=password --database=zimbra --batch --skip-column-names'.
Thu Jul 31 12:35:33 2008 Script failed with code 256: - exiting
Thu Jul 31 12:35:33 2008 UPGRADE FAILED - exiting

[phoenix]

The recommended upgrade path is from 4.5.x to 4.5.11 then to 5.0.x, is that what you've tried?

[RaNd]

Originally Posted by phoenix

The recommended upgrade path is from 4.5.x to 4.5.11 then to 5.0.x, is that what you've tried?

Exactly ,since the upgrade directly from 4.5.5 to 5.x.x failed . . .

Also tried from 4.5.11 to 5.0.0 and 5.0.7 but with no luck . . .

Some moths ago we had a power outage and the ldap was corrupted,
I restore it from a backup but sometimes it returns:

b_recover: Log sequence error: page LSN 1 540201; previous LSN 6 6506556
db_recover: Recovery function for LSN 1 1279 failed on forward pass
db_recover: PANIC: Invalid argument
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
[....]
db_recover: DB_ENV->open: DB_RUNRECOVERY: Fatal error, run database recovery


when I restore it from the backup to test . .

[phoenix]

Did you check the MySQL tables for errors?

Logger - Zimbra :: Wiki
[SOLVED] mysql errors upgrading Zimbra-4.5.10 to 5.00 or 5.04

Check them for corruption, fix them if there is any and run the upgrade again - with suitable backups of course.

[RaNd]

Thnx!
I had completly forgot to chech MySql tables. 4 tables were corrupted.
I'll try the upgrade and post results