Results 1 to 3 of 3

Thread: ERROR: service.FAILURE (system failure: unable to search gal)

  1. #1
    Join Date
    Jul 2006
    Location
    Pisa
    Posts
    135
    Rep Power
    9

    Default ERROR: service.FAILURE (system failure: unable to search gal)

    Hi

    I'm using zcs 5.0.13 on unbuntu.
    I configured active directory authentication on a replica domain controller and it works well.
    If I configure GAL same parameters (zmprov gd domain)
    zimbraGalAutoCompleteLdapFilter: adAutoComplete
    zimbraGalLdapBindDn: zimbra-replication@mydomain.lan
    zimbraGalLdapBindPassword: mypassowrd
    zimbraGalLdapFilter: ad
    zimbraGalLdapPageSize: 1000
    zimbraGalLdapSearchBase: dc=mydomain,dc=lan
    zimbraGalLdapURL: ldap://10.0.4.4:389
    zimbraGalMaxResults: 100
    zimbraGalMode: ldap
    zimbraGalSyncLdapPageSize: 1000

    When I try to search GAL i receice an error:
    ERROR: service.FAILURE (system failure: unable to search gal)

    And in /opt/zimbra/log/mailbox.log I see:


    Code:service.FAILURE
    at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:253)
    at com.zimbra.cs.account.ldap.LdapUtil.searchGal(Ldap Util.java:736)
    at com.zimbra.cs.account.ldap.LdapUtil.searchLdapGal( LdapUtil.java:802)
    at com.zimbra.cs.account.ldap.LdapUtil.searchLdapGal( LdapUtil.java:787)
    at com.zimbra.cs.account.ldap.LdapProvisioning.search LdapGal(LdapProvisioning.java:4192)
    at com.zimbra.cs.account.ldap.LdapProvisioning.search Gal(LdapProvisioning.java:3967)
    at com.zimbra.cs.account.ldap.LdapProvisioning.search Gal(LdapProvisioning.java:3926)
    at com.zimbra.cs.service.account.SearchGal.handle(Sea rchGal.java:75)
    at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:429)
    at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:286)
    at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:160)
    at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:269)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:727)
    at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:190)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
    at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:487)
    at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1093)
    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:1084)
    at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:360)
    at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:216)
    at org.mortbay.jetty.servlet.SessionHandler.handle(Se ssionHandler.java:181)
    at org.mortbay.jetty.handler.ContextHandler.handle(Co ntextHandler.java:716)
    at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.java:406)
    at org.mortbay.jetty.handler.ContextHandlerCollection .handle(ContextHandlerCollection.java:211)
    at org.mortbay.jetty.handler.HandlerCollection.handle (HandlerCollection.java:114)
    at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:139)
    at org.mortbay.jetty.handler.rewrite.RewriteHandler.h andle(RewriteHandler.java:350)
    at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:139)
    at org.mortbay.jetty.Server.handle(Server.java:313)
    at org.mortbay.jetty.HttpConnection.handleRequest(Htt pConnection.java:506)
    at org.mortbay.jetty.HttpConnection$RequestHandler.co ntent(HttpConnection.java:844)
    at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:644)
    at org.mortbay.jetty.HttpParser.parseAvailable(HttpPa rser.java:211)
    at org.mortbay.jetty.HttpConnection.handle(HttpConnec tion.java:381)
    at org.mortbay.io.nio.SelectChannelEndPoint.run(Selec tChannelEndPoint.java:396)
    at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(BoundedThreadPool.java:442)
    Caused by: javax.naming.PartialResultException [Root exception is javax.naming.CommunicationException: mydomain.lan:389 [Root exception is java.net.SocketTimeo
    at com.sun.jndi.ldap.LdapNamingEnumeration.hasMoreImp l(LdapNamingEnumeration.java:224)
    at com.sun.jndi.ldap.LdapNamingEnumeration.hasMore(Ld apNamingEnumeration.java:171)
    at com.zimbra.cs.account.ldap.LdapUtil.searchGal(Ldap Util.java:691)
    ... 36 more
    Caused by: javax.naming.CommunicationException: myd.lan:389 [Root exception is java.net.SocketTimeoutException: connect timed out]
    at com.sun.jndi.ldap.LdapReferralContext.<init>(LdapR eferralContext.java:74)
    at com.sun.jndi.ldap.LdapReferralException.getReferra lContext(LdapReferralException.java:132)
    at com.sun.jndi.ldap.LdapNamingEnumeration.hasMoreRef errals(LdapNamingEnumeration.java:339)
    at com.sun.jndi.ldap.LdapNamingEnumeration.hasMoreImp l(LdapNamingEnumeration.java:208)
    ... 38 more


    Can you help me ?

    Thank you

  2. #2
    Join Date
    Nov 2005
    Posts
    33
    Rep Power
    9

    Default

    I am having the same issue. I have authentication working but I am not able to successfully test the GAL. My guess is an incorrect search term? I'm not sure what I need to put there. Suggestions? Guidance?

  3. #3
    Join Date
    Jul 2006
    Location
    Pisa
    Posts
    135
    Rep Power
    9

    Default

    In release 5.0.15 i'm not experiencing the problem, in 5.0.13 I solved using a different LDAP filter than the one proposed by zimbra.

    using zmprov gacf zimbraGalLdapFilterDef you can see the definition for adAutoComplete that you can edit, otherwise try to use ldap instead of active directory and put (|(cn=&#37;s*)(sn=%s*)(givenName=%s*)(mail=%s*))
    as filter.

Similar Threads

  1. Installation zimbra Initializing ldap...failed. (28416)
    By farrukh.nadeem in forum Installation
    Replies: 10
    Last Post: 08-14-2009, 06:52 AM
  2. Replies: 4
    Last Post: 08-04-2008, 06:17 PM
  3. [SOLVED] Mailserver down when send file attach of 50Mb
    By ZMilton in forum Administrators
    Replies: 20
    Last Post: 04-10-2008, 11:44 AM
  4. Replies: 2
    Last Post: 02-12-2008, 10:55 AM
  5. 3.0 to 4.5.3 Upgrade failed (mysql error)
    By dealt in forum Installation
    Replies: 35
    Last Post: 03-19-2007, 10:30 PM

Posting Permissions

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