Force LDAP Upgrade?

[jholder]

Hi-
I"m working with someone with a couple problems, and I think they stem from a failed LDAP upgrade, but you decide.

LDAP isn't binding to loopback address, but is binding to the fqdn and ip address. (Checked DNS and hosts file. Both are fine)
>How? telnet localhost 389 failed; however, telnet x.x.x.x succeeds

zmprov Failes because it can't contact localhost
>zmprov returns i/o exception, conneciton failed.

zmsetup.pl, this error is in the zmsetup log:
ERROR: service.INVALID_REQUEST (invalid request: LDAP schema violation: [LDAP: error code 65 - attribute 'zimbraCertAuthorityKeySelfSigned' not allowed]) (cause: javax.naming.directory.SchemaViolationException [LDAP: error code 65 - attribute 'zimbraCertAuthorityKeySelfSigned' not allowed])
(many others too)

I'm thinking that the cn for zimbraCertAuthority,etc isn't installed becase perhaps LDAP didn't get upgraded??
I tried running zmetup.pl, zmldapdif, and ldapinit with null results

My question: Do you agree, or not? If you do, how do I force an ldap upgrade?

john

[marcmac]

Sounds like the schema file is missing. We bind to the name in ldap_url, so the ldap server should be accessible on that interface

[jholder]

The ldap url seems okay ldap://<fqdn>:389

How would I fix a schema file problem?

[rvissers]

This thread ended up being from my failed upgrade. I just wanted to say that both Wanabetenor & Phoenix went way above and beyond the call of duty to help me out with the problem (and taught me quite a few things about Zimbra during the whole process) and they deserve much public kudos for helping out a junior admin like myself.

Thanks!