Results 1 to 5 of 5

Thread: LDAP problems after migrating from 6 to 7.1

  1. #1
    Join Date
    Jul 2011
    Posts
    3
    Rep Power
    4

    Default LDAP problems after migrating from 6 to 7.1

    I've migrated Zimbra from 6.0.5 32 bit to 7.1 64 bit accordingly to the guide Network Edition: Moving from 32-bit to 64-bit Server - Zimbra :: Wiki

    Most of the things seem to be working just fine. But in some cases I hit LDAP errors like follows. Any ideas, what could be wrong with LDAP or whatever?

    1. Nothing special, just want to change value:
    zimbra@zmbr:~$ zmprov mcf zimbraMtaSaslAuthEnable yes
    ERROR: account.INVALID_ATTR_VALUE (invalid attr value: [LDAP: error code 21 - zimbraMtaSaslAuthEnable: value #0 invalid per syntax])

    2. After changing language in web-interface I press Save and got:
    invalid attr value: [LDAP: error code 21 - zimbraPrefDefaultPrintFontSize: attribute type undefined]

    3. In some cases the are errors with java and LDAP in web-interface:
    method: [unknown]
    msg: system failure: ldap search failed
    code: service.FAILURE
    detail: soap:Receiver
    trace: com.zimbra.common.service.ServiceException: system failure: ldap search failed ExceptionId:btpool0-175://mail.pntl.ru/service/soap/GetDistributionListMembersRequest:1309953722022:0f f3fd3f5cb85f5a Code:service.FAILURE at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:248) at com.zimbra.cs.gal.GalSearchControl.ldapSearch(GalS earchControl.java:611) at com.zimbra.cs.gal.GalSearchControl.search(GalSearc hControl.java:160) at com.zimbra.cs.gal.GalGroupMembers.searchGal(GalGro upMembers.java:261) at com.zimbra.cs.service.account.GetDistributionListM embers.handle(GetDistributionListMembers.java:56) at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:412) at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:287) at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:158) at com.zimbra.soap.SoapServlet.doWork(SoapServlet.jav a:294) at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:215) at javax.servlet.http.HttpServlet.service(HttpServlet .java:725) at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:208) at javax.servlet.http.HttpServlet.service(HttpServlet .java:814) at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1166) at com.zimbra.cs.servlet.SetHeaderFilter.doFilter(Set HeaderFilter.java:79) at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1157) at org.mortbay.servlet.UserAgentFilter.doFilter(UserA gentFilter.java:81) at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter .java:132) at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1157) at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:388) at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:218) at org.mortbay.jetty.servlet.SessionHandler.handle(Se ssionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(Co ntextHandler.java:765) at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.java:422) at org.mortbay.jetty.handler.ContextHandlerCollection .handle(ContextHandlerCollection.java:230) at org.mortbay.jetty.handler.HandlerCollection.handle (HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152) at org.mortbay.jetty.handler.rewrite.RewriteHandler.h andle(RewriteHandler.java:230) at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152) at org.mortbay.jetty.handler.DebugHandler.handle(Debu gHandler.java:77) at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(Htt pConnection.java:543) at org.mortbay.jetty.HttpConnection$RequestHandler.co ntent(HttpConnection.java:946) at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:756) at org.mortbay.jetty.HttpParser.parseAvailable(HttpPa rser.java:218) at org.mortbay.jetty.HttpConnection.handle(HttpConnec tion.java:405) at org.mortbay.io.nio.SelectChannelEndPoint.run(Selec tChannelEndPoint.java:410) at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(BoundedThreadPool.java:451) Caused by: com.zimbra.common.service.ServiceException: system failure: unable to search gal ExceptionId:btpool0-175://mail.pntl.ru/service/soap/GetDistributionListMembersRequest:1309953722022:0f f3fd3f5cb85f5a Code:service.FAILURE at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:248) at com.zimbra.cs.account.ldap.LdapUtil.searchGal(Ldap Util.java:842) at com.zimbra.cs.account.ldap.LdapUtil.doGalSearch(Ld apUtil.java:1042) at com.zimbra.cs.account.ldap.LdapUtil.galSearch(Ldap Util.java:1025) at com.zimbra.cs.gal.GalSearchControl.ldapSearch(GalS earchControl.java:609) ... 38 more Caused by: javax.naming.directory.InvalidSearchFilterExceptio n: Missing 'equals'; remaining name 'dc=pntl,dc=ru' at com.sun.jndi.ldap.Filter.encodeSimpleFilter(Filter .java:310) at com.sun.jndi.ldap.Filter.encodeFilter(Filter.java: 128) at com.sun.jndi.ldap.Filter.encodeFilterList(Filter.j ava:715) at com.sun.jndi.ldap.Filter.encodeComplexFilter(Filte r.java:635) at com.sun.jndi.ldap.Filter.encodeFilter(Filter.java: 86) at com.sun.jndi.ldap.Filter.encodeFilterString(Filter .java:56) at com.sun.jndi.ldap.LdapClient.search(LdapClient.jav a:520) at com.sun.jndi.ldap.LdapCtx.doSearch(LdapCtx.java:19 62) at com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1 824) at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:17 49) at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_sea rch(ComponentDirContext.java:368) at com.sun.jndi.toolkit.ctx.PartialCompositeDirContex t.search(PartialCompositeDirContext.java:338) at javax.naming.directory.InitialDirContext.search(In itialDirContext.java:257) at com.zimbra.cs.account.ldap.ZimbraLdapContext.searc hDir(ZimbraLdapContext.java:737) at com.zimbra.cs.account.ldap.LdapUtil.searchGal(Ldap Util.java:796) ... 41 more
    request:
    Body: {
    GetDistributionListMembersRequest: {
    _jsns: "urn:zimbraAccount",
    dl: {
    _content: "techsklad@pntl.ru"
    },
    limit: 100,
    offset: 0
    }
    },
    Header: {
    context: {
    _jsns: "urn:zimbra",
    account: {
    _content: "rodionov_n@pntl.ru",
    by: "name"
    },
    authToken: "(removed)",
    notify: {
    seq: 28
    },
    session: {
    _content: 112400,
    id: 112400
    },
    userAgent: {
    name: "ZimbraWebClient - SAF3 (Win)",
    version: "7.1.1_GA_3196"
    }
    }
    }

  2. #2
    Join Date
    Jul 2007
    Location
    Baltimore
    Posts
    1,649
    Rep Power
    11

    Default

    did you export the ldap database from zcs 6 and import it into 7? that is a very bad idea. the wiki for migrating is meant to go to the same version of zcs. many changes happen in an upgrade especially in a major version and some attributes may be removed/modified.

  3. #3
    Join Date
    Jul 2011
    Posts
    3
    Rep Power
    4

    Default

    OK, so what to do now? I suppose there must be some scripts used to upgrade from 6 to 7, that can be used outside the upgrade procedure, just to make changes in LDAP? Or there is no way to upgrade from 6 to 7 at all?

  4. #4
    Join Date
    Jul 2007
    Location
    Baltimore
    Posts
    1,649
    Rep Power
    11

    Default

    normally the process is to first migrate to the same version just 64bit flavor, then upgrade to the latest version.

    as far as how to fix what you've done, i'm honestly not sure you can. you can try running /opt/zimbra/libexec/zmsetup.pl which is the script run when you upgrade that normally performs the upgrade steps necessary for the ldap and mysql databases. It depends on the file /opt/zimbra/.install_history which you may want to copy from your old server ot hte new one so it thinks its upgrading from an old 6.x version, otherwise it won't realize that it has to do anything.

    this could potentially have a bad impact though so if you can't liek snapshot your system for an easy revert, you may not want to try this but i don't really know what else you could try

  5. #5
    Join Date
    Jul 2011
    Posts
    3
    Rep Power
    4

    Default

    Thank you very much. I hope after examining this script I'll find some tips to upgrade LDAP. Other things seem to be working perfectly,

Similar Threads

  1. LDAP Cannot bind on migration to new server
    By neekster in forum Migration
    Replies: 23
    Last Post: 03-09-2009, 02:08 AM
  2. Migrating from Postfix + LDAP to Zimbra
    By augustobsb in forum Administrators
    Replies: 2
    Last Post: 04-15-2008, 07:01 AM
  3. Zimbra + Samba LDAP auth problems
    By fajarpri in forum Installation
    Replies: 3
    Last Post: 07-04-2007, 11:39 PM
  4. 3 testing: LDAP: 389 Failed when restore zimbra
    By victorLeong in forum Administrators
    Replies: 15
    Last Post: 05-24-2007, 06:45 AM
  5. LDAP problems
    By TaskMaster in forum Installation
    Replies: 1
    Last Post: 05-02-2007, 08:29 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •