Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Installation

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 11-14-2009, 08:39 AM
Intermediate Member
 
Posts: 17
Default [SOLVED] Upgrade from 5.0.20 to 6.0.2 LDAP error

I have upgraded two different server from 5.0.14 to 5.0.20 without any problem.
When I try to upgrade to 6.0.2 I get the same error on both server:
It convert MySQL schema to 63 without problem, and after when it start to migrate LDAP crash with the error:
"Migrating ldap data...slapadd import failed.
UPGRADE FAILED - exiting"

If I restart the installation it crash in the same point, in the log I dont have any further information about the error.
I was obliged to uninstall the failed 6.0.2 and restore 5.0.20 from backup maked by me previously.

I have followed the two wiki:
- Optimizing 50 to 60 LDAP upgrade - Zimbra :: Wiki
- Managing Customized BDB configurations - Zimbra :: Wiki
without result, I dont use Samba and I dont have Samba.Schema. What I'm missing? Some .schema or some .ldif to edit/copy/upgrade for make it compatible with the new schema of 6.0.20?

Thank you for your support
__________________
CentOS 5.4 32 bit
Zimbra 6.0.4_GA_2038.RHEL5
Reply With Quote
  #2 (permalink)  
Old 11-14-2009, 11:25 AM
Moderator
 
Posts: 6,236
Default

The installer needs to know about other versions, so when a FRANKLIN(5) is released after a particular GNR(6) build - you can't upgrade from that 'newer' v5 to an 'older' v6.

I know it defies expected logic since it's a 'newer' v5 but schema wise it's not yet built into the 'older' v6's upgrade steps.

For exiting earlier: Bug 42687 – ZCS install should identify and validate version from which upgraded & discussed in: Bug 42609 – Upgrade from 5.0.19 to 6.0.0 or 6.0.1 fails - slapadd import failed around zimbraFeatureVoiceChangePinEnabled.

If you flip through the announcements section you'll get a sense of release dates.

So the only 5 > 6 paths that are possible right now are:
5.0.19 & prior > 6.0.2+
5.0.18 & prior > 6.0.2 (& anything after 6.0.0RC1 but not worth your time)

Thus you will have to wait till 5.0.21 & 6.0.4 since you can't upgrade major versions from a FRANKLIN(5) release that is 'newer' than an 'older' GNR(6) release. (Not gonna discuss possible hacks here.)

5.0.20 is 'newer' than 6.0.2 and actually still 'newer' than the upcoming 6.0.3 because its essentially 6.0.2 with security fixes.
Reply With Quote
  #3 (permalink)  
Old 11-15-2009, 06:30 PM
Intermediate Member
 
Posts: 17
Default

Thank you for your exhaustive explanation!
Ok, I wait for the two release that you have reccomended me, any estimates of the release date?
Meanwhile can I try, just for improve my professional skill, to export users with password and import it on a new fresh installation?
What are the correct procedure?

Thank you!
__________________
CentOS 5.4 32 bit
Zimbra 6.0.4_GA_2038.RHEL5
Reply With Quote
  #5 (permalink)  
Old 11-25-2009, 05:50 PM
Intermediate Member
 
Posts: 17
Default

Thank you so much, worked fine for me!
And now for continue Cleaning up the Zimbra area

Thread solved
See you
__________________
CentOS 5.4 32 bit
Zimbra 6.0.4_GA_2038.RHEL5
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com




 

SEO by vBSEO ©2011, Crawlability, Inc.