View Single Post
  #4 (permalink)  
Old 01-21-2006, 12:43 PM
FunkyPenguin FunkyPenguin is offline
Special Member
 
Posts: 140
Exclamation Upgrade from M3_436 to M4_41 failed

Just tried to upgrade ZCS on my CentOS 4.2 box and it failed

Below is what was output to screen:

Code:
Upgrading from 3.0.0_M3_436 to 3.0.0_M4_41
Proceed with upgrade? [No] y
Sat Jan 21 19:32:04 2006: Stopping zimbra services
Sat Jan 21 19:32:09 2006: Checking mysql status
Sat Jan 21 19:32:10 2006: Starting mysql
Sat Jan 21 19:32:11 2006: Checking logger mysql status
Sat Jan 21 19:32:13 2006: Starting logger mysql
Sat Jan 21 19:32:15 2006: SELECT value FROM config WHERE name = 'db.version'
Sat Jan 21 19:32:16 2006: SELECT value FROM config WHERE name = 'db.version'
This appears to be 3.0.0_M3, with no schema upgrade needed
Sat Jan 21 19:32:18 2006: Stopping mysql
Sat Jan 21 19:32:22 2006: Stopping logger mysql
Checking 3.0.M1

Checking 3.0.0_M2

Checking 3.0.0_M3

Sat Jan 21 19:32:26 2006: Updating from 3.0.0_M3
Sat Jan 21 19:32:26 2006: Checking ldap status
Sat Jan 21 19:32:27 2006: Starting ldap
Sat Jan 21 19:32:34 2006: ldap startup failed with exit code 1
UPGRADE FAILED - exiting
Any ideas? I even tried to start the zimbra service manually by running "service zimbra start" - I know this isn't the recommended way of doing it, but I'm starting to panick as now my beautiful Zimbra setup has died and I need my mail/contacts/calendar back pronto and the following was spat at me

Code:
# service zimbra start
Host hawk.forcev.net
        Starting ldap...Done.
FAILED
db_recover: Finding last valid log LSN: file: 1 offset 2441978
db_recover: Recovery starting from [1][2441854]
db_recover: Recovery complete at Sat Jan 21 19:36:11 2006
db_recover: Maximum transaction ID 800001c0 Recovery checkpoint [1][2441978]
ERROR - failed to start slapd
Reply With Quote