ldap problem on upgrade from 5.0.16 to 6.0.5

[dylanjh]

I have 5.0.16 installed and Im trying to upgrade to 6.0.5, but everytime I run the upgrade, it stops with the following error:

Upgrading from 5.0.20_GA_3127 to 6.0.5_GA_2213
Stopping zimbra services...done.
Verifying /opt/zimbra/conf/my.cnf
Starting mysql...done.
This appears to be 5.0.20_GA
Installing LDAP configuration database...done.
Migrating ldap data...slapadd import failed.
UPGRADE FAILED - exiting.

Obviously something to do with ldap. Checking the install log file yields the following:

Thu Apr 1 12:06:26 2010 done.
Thu Apr 1 12:06:27 2010 This appears to be 5.0.20_GA
Thu Apr 1 12:06:27 2010 Installing LDAP configuration database...
Thu Apr 1 12:06:28 2010 done.
Thu Apr 1 12:06:28 2010 Migrating ldap data...
Thu Apr 1 12:06:28 2010 *** Running as zimbra user: /opt/zimbra/openldap/sbin/slapadd -q -b '' -F /opt/zimbra/data/ldap/config -l /opt/zimbra/data/ldap/ldap.60
<= str2entry: str2ad(ZIMBRADOMAINPREFMAILSIGNATUREENABLED): attribute type undefined
slapadd: could not parse entry (line=827)
Thu Apr 1 12:06:28 2010 slapadd import failed.
Thu Apr 1 12:06:28 2010 UPGRADE FAILED - exiting.

So I can see it complaining about the ldap entry "ZIMBRADOMAINPREFMAILSIGNATUREENABLED" (and three other settings associated with the disclaimer plugin)

So here's the thing, Ive removed all mention of "ZIMBRADOMAINPREFMAILSIGNATUREENABLED" and anything else to do with the disclaimer extention from the zimbra.schema file. Ive even brosed the ldap data with ldapAdmin to verify that that the settings are no longer in the ldap database.
But somehow, zmsetup.pl is finding it somewhere and including it in a file called ldap.60 which is presumably the file its going to use for the new version.

Ive checked this thread, and the associated wiki articles:
Migrating ldap data...slapadd import failed.
but still get the same result. Ive grepped the whole zimbra dir, and I cant find mention of ZIMBRADOMAINPREFMAILSIGNATUREENABLED or any of the other disclaimer settings anywhere.

Any suggestions anyone?

[phoenix]

Please read P33 in the Release Notes for Zimbra 6.x

[dylanjh]

Hi bill, thanks for your response. I have checked the release docs before. However Im still a bit confused. I noticed this paragraph:

"Important: The community-provided "Domain Disclaimer Extension" is not
compatible with ZCS 6.0. Do not upgrade to 6.0 if you run the domain
disclaimer extension."

Are you saying that I simply shouldn't upgrade to version 6 on this basis?

Also, I have followed the steps in Optimizing 5.0 to 6.0 LDAP upgrade - Zimbra :: Wiki Several times, but but I always end up with the same result; the ldap upgrade failing.

Just to make sure Im understanding this article correctly, I take it this is correct:

In olcDatabase={2}hdb.ldif :
.
.
.
olcDbIndex: displayName pres,eq,sub
olcDbIndex: sn pres,eq,sub
olcDbIndex: zimbraCalResRoom eq,sub
olcDbIndex: zimbraCalResCapacity eq
olcDbIndex: zimbraCalResBuilding eq,sub
olcDbIndex: zimbraCalResFloor eq,sub
olcDbIndex: ZIMBRADOMAINPREFMAILSIGNATUREENABLED eq
olcDbIndex: ZIMBRADOMAINPREFMAILSIGNATUREHTML eq
olcDbIndex: ZIMBRADOMAINPREFMAILSIGNATURE eq
olcDbLinearIndex: FALSE
olcDbMode: 0600
olcDbSearchStack: 16
olcDbShmKey: 0
olcDbCacheFree: 1
.
.

Then run zmsetup.pl

Or have I got it all wrong?

Thanks In advance
Dylan

[phoenix]

You need to remove the disclaimer as it's simply not compatible with ZImbra 6.x, see the details in the bug report: Bug 37698 &ndash; Domain Disclaimer Extension non-portable There are also several outstanding bug reports/enhancements that relate to the disclaimer, you may want to vote on them.

Until the Disclaimer issue is resolved you may want to use a mandatory signature in your email, check the Release Notes P8. If you are about to upgrade then I'd suggest you might want to wait for the next version which is currently targetted for early next week.

[dylanjh]

Bill,
Yes I have removed the disclaimer schema customizations from the zimbra.schema file. Or at least I think I have. I checked the instructions for the installation of the disclaimer, and as such I haved removed the three settings from the zimbra.schema file.

Ive already found a way of adding a disclaimer on a Zimbra 6 test installation. My problem is getting my production server to Zimbra 6.0 in the first place.

Now As far as I can see Ive removed everything i can to do with the additional settings I put in place, but it seems there is some kind of residual presence that I cant track down.

Ill wait until next week, see what that brings.