Page 1 of 2 12 LastLast
Results 1 to 10 of 12

Thread: GAL error

  1. #1
    alexz is offline Active Member
    Join Date
    Oct 2005
    Posts
    46
    Rep Power
    9

    Question GAL search error

    I'm trying to get GAL integration with AD to to work. I think I have the correct DN in the setting. When I run a test on the letter A the search succeeds and lists all entries with the letter A. However, if I type thing more specific (like Al) the search fails. This is in the Configure GAL section in the admin UI. This is the error when trying to search for Al (in the end I want to be able to say search for Alex):

    avax.naming.PartialResultException [Root exception is javax.naming.CommunicationException: exonline.intranet:389 [Root exception is java.net.ConnectException: Connection refused]]
    at com.sun.jndi.ldap.LdapNamingEnumeration.hasMoreImp l(LdapNamingEnumeration.java:224)
    at com.sun.jndi.ldap.LdapNamingEnumeration.hasMoreRef errals(LdapNamingEnumeration.java:362)
    at com.sun.jndi.ldap.LdapNamingEnumeration.hasMoreImp l(LdapNamingEnumeration.java:208)
    at com.sun.jndi.ldap.LdapNamingEnumeration.hasMoreRef errals(LdapNamingEnumeration.java:362)
    at com.sun.jndi.ldap.LdapNamingEnumeration.hasMoreImp l(LdapNamingEnumeration.java:208)
    at com.sun.jndi.ldap.LdapNamingEnumeration.hasMore(Ld apNamingEnumeration.java:171)
    at com.zimbra.cs.account.ldap.LdapUtil.searchLdapGal( LdapUtil.java:823)
    at com.zimbra.cs.account.ldap.Check.checkGalConfig(Ch eck.java:190)
    at com.zimbra.cs.service.admin.CheckGalConfig.handle( CheckGalConfig.java:58)
    at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:255)
    at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:163)
    at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:84)
    at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:228)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:709)
    at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:154)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:802)
    at org.apache.catalina.core.ApplicationFilterChain.in ternalDoFilter(ApplicationFilterChain.java:252)
    at org.apache.catalina.core.ApplicationFilterChain.do Filter(ApplicationFilterChain.java:173)
    at org.apache.catalina.core.StandardWrapperValve.invo ke(StandardWrapperValve.java:213)
    at org.apache.catalina.core.StandardContextValve.invo ke(StandardContextValve.java:178)
    at org.apache.catalina.core.StandardHostValve.invoke( StandardHostValve.java:126)
    at org.apache.catalina.valves.ErrorReportValve.invoke (ErrorReportValve.java:105)
    at org.apache.catalina.core.StandardEngineValve.invok e(StandardEngineValve.java:107)
    at org.apache.catalina.valves.AccessLogValve.invoke(A ccessLogValve.java:541)
    at org.apache.catalina.connector.CoyoteAdapter.servic e(CoyoteAdapter.java:148)
    at org.apache.coyote.http11.Http11Processor.process(H ttp11Processor.java:869)
    at org.apache.coyote.http11.Http11BaseProtocol$Http11 ConnectionHandler.processConnection(Http11BaseProt ocol.java:667)
    at org.apache.tomcat.util.net.PoolTcpEndpoint.process Socket(PoolTcpEndpoint.java:527)
    at org.apache.tomcat.util.net.LeaderFollowerWorkerThr ead.runIt(LeaderFollowerWorkerThread.java:80)
    at org.apache.tomcat.util.threads.ThreadPool$ControlR unnable.run(ThreadPool.java:684)
    at java.lang.Thread.run(Thread.java:595)
    Caused by: javax.naming.CommunicationException: exonline.intranet:389 [Root exception is java.net.ConnectException: Connection refused]
    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)
    ... 30 more
    Caused by: java.net.ConnectException: Connection refused
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(PlainSocketImpl .java:333)
    at java.net.PlainSocketImpl.connectToAddress(PlainSoc ketImpl.java:195)
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.j ava:182)
    at java.net.SocksSocketImpl.connect(SocksSocketImpl.j ava:366)
    at java.net.Socket.connect(Socket.java:507)
    at sun.reflect.GeneratedMethodAccessor33.invoke(Unkno wn Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at com.sun.jndi.ldap.Connection.createSocket(Connecti on.java:333)
    at com.sun.jndi.ldap.Connection.<init>(Connection.jav a:181)
    at com.sun.jndi.ldap.LdapClient.<init>(LdapClient.jav a:118)
    at com.sun.jndi.ldap.LdapClientFactory.createPooledCo nnection(LdapClientFactory.java:44)
    at com.sun.jndi.ldap.pool.Connections.<init>(Connecti ons.java:97)
    at com.sun.jndi.ldap.pool.Pool.getPooledConnection(Po ol.java:114)
    at com.sun.jndi.ldap.LdapPoolManager.getLdapClient(Ld apPoolManager.java:310)
    at com.sun.jndi.ldap.LdapClient.getInstance(LdapClien t.java:1572)
    at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:259 6)
    at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:283)
    at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapC txFactory.java:175)
    at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstanc e(LdapCtxFactory.java:134)
    at com.sun.jndi.url.ldap.ldapURLContextFactory.getObj ectInstance(ldapURLContextFactory.java:35)
    at javax.naming.spi.NamingManager.getURLObject(Naming Manager.java:584)
    at javax.naming.spi.NamingManager.processURL(NamingMa nager.java:364)
    at javax.naming.spi.NamingManager.processURLAddrs(Nam ingManager.java:344)
    at javax.naming.spi.NamingManager.getObjectInstance(N amingManager.java:316)
    at com.sun.jndi.ldap.LdapReferralContext.<init>(LdapR eferralContext.java:93)
    ... 33 more


    When I do a search when logged in as a user I get the following error:

    javax.naming.PartialResultException [Root exception is javax.naming.CommunicationException: exonline.intranet:389 [Root exception is java.net.ConnectException: Connection refused]]
    at com.sun.jndi.ldap.LdapNamingEnumeration.hasMoreImp l(LdapNamingEnumeration.java:224)
    at com.sun.jndi.ldap.LdapNamingEnumeration.hasMoreRef errals(LdapNamingEnumeration.java:362)
    at com.sun.jndi.ldap.LdapNamingEnumeration.hasMoreImp l(LdapNamingEnumeration.java:208)
    at com.sun.jndi.ldap.LdapNamingEnumeration.hasMoreRef errals(LdapNamingEnumeration.java:362)
    at com.sun.jndi.ldap.LdapNamingEnumeration.hasMoreImp l(LdapNamingEnumeration.java:208)
    at com.sun.jndi.ldap.LdapNamingEnumeration.hasMore(Ld apNamingEnumeration.java:171)
    at com.zimbra.cs.account.ldap.LdapUtil.searchLdapGal( LdapUtil.java:823)
    at com.zimbra.cs.account.ldap.Check.checkGalConfig(Ch eck.java:190)
    at com.zimbra.cs.service.admin.CheckGalConfig.handle( CheckGalConfig.java:58)
    at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:255)
    at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:163)
    at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:84)
    at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:228)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:709)
    at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:154)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:802)
    at org.apache.catalina.core.ApplicationFilterChain.in ternalDoFilter(ApplicationFilterChain.java:252)
    at org.apache.catalina.core.ApplicationFilterChain.do Filter(ApplicationFilterChain.java:173)
    at org.apache.catalina.core.StandardWrapperValve.invo ke(StandardWrapperValve.java:213)
    at org.apache.catalina.core.StandardContextValve.invo ke(StandardContextValve.java:178)
    at org.apache.catalina.core.StandardHostValve.invoke( StandardHostValve.java:126)
    at org.apache.catalina.valves.ErrorReportValve.invoke (ErrorReportValve.java:105)
    at org.apache.catalina.core.StandardEngineValve.invok e(StandardEngineValve.java:107)
    at org.apache.catalina.valves.AccessLogValve.invoke(A ccessLogValve.java:541)
    at org.apache.catalina.connector.CoyoteAdapter.servic e(CoyoteAdapter.java:148)
    at org.apache.coyote.http11.Http11Processor.process(H ttp11Processor.java:869)
    at org.apache.coyote.http11.Http11BaseProtocol$Http11 ConnectionHandler.processConnection(Http11BaseProt ocol.java:667)
    at org.apache.tomcat.util.net.PoolTcpEndpoint.process Socket(PoolTcpEndpoint.java:527)
    at org.apache.tomcat.util.net.LeaderFollowerWorkerThr ead.runIt(LeaderFollowerWorkerThread.java:80)
    at org.apache.tomcat.util.threads.ThreadPool$ControlR unnable.run(ThreadPool.java:684)
    at java.lang.Thread.run(Thread.java:595)
    Caused by: javax.naming.CommunicationException: exonline.intranet:389 [Root exception is java.net.ConnectException: Connection refused]
    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)
    ... 30 more
    Caused by: java.net.ConnectException: Connection refused
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(PlainSocketImpl .java:333)
    at java.net.PlainSocketImpl.connectToAddress(PlainSoc ketImpl.java:195)
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.j ava:182)
    at java.net.SocksSocketImpl.connect(SocksSocketImpl.j ava:366)
    at java.net.Socket.connect(Socket.java:507)
    at sun.reflect.GeneratedMethodAccessor33.invoke(Unkno wn Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at com.sun.jndi.ldap.Connection.createSocket(Connecti on.java:333)
    at com.sun.jndi.ldap.Connection.<init>(Connection.jav a:181)
    at com.sun.jndi.ldap.LdapClient.<init>(LdapClient.jav a:118)
    at com.sun.jndi.ldap.LdapClientFactory.createPooledCo nnection(LdapClientFactory.java:44)
    at com.sun.jndi.ldap.pool.Connections.<init>(Connecti ons.java:97)
    at com.sun.jndi.ldap.pool.Pool.getPooledConnection(Po ol.java:114)
    at com.sun.jndi.ldap.LdapPoolManager.getLdapClient(Ld apPoolManager.java:310)
    at com.sun.jndi.ldap.LdapClient.getInstance(LdapClien t.java:1572)
    at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:259 6)
    at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:283)
    at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapC txFactory.java:175)
    at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstanc e(LdapCtxFactory.java:134)
    at com.sun.jndi.url.ldap.ldapURLContextFactory.getObj ectInstance(ldapURLContextFactory.java:35)
    at javax.naming.spi.NamingManager.getURLObject(Naming Manager.java:584)
    at javax.naming.spi.NamingManager.processURL(NamingMa nager.java:364)
    at javax.naming.spi.NamingManager.processURLAddrs(Nam ingManager.java:344)
    at javax.naming.spi.NamingManager.getObjectInstance(N amingManager.java:316)
    at com.sun.jndi.ldap.LdapReferralContext.<init>(LdapR eferralContext.java:93)
    ... 33 more
    Last edited by alexz; 04-21-2006 at 05:35 AM.
    Sincerely,

    Alex

  2. #2
    bobby is offline Zimbra Employee
    Join Date
    Nov 2005
    Posts
    518
    Rep Power
    10

    Default

    >Caused by: javax.naming.CommunicationException: exonline.intranet:389 [Root exception is java.net.ConnectException: Connection refused]
    >
    exonline.intranet is AD? what happens if you "telnet exonline.intranet 389"?

  3. #3
    alexz is offline Active Member
    Join Date
    Oct 2005
    Posts
    46
    Rep Power
    9

    Default

    Quote Originally Posted by bobby
    exonline.intranet is AD? what happens if you "telnet exonline.intranet 389"?
    Yes. exonline.intranet is an AD forest. It's not a fqdn so I can't telnet to it.

    Here is the GAL config as entered into the wizard:

    GAL mode: External, most results =100
    Server type= Active Directory
    LDAP URL: dc.exonline.intranet (AD appears automatically in the LDAP filter and dc=exonline,dc=intranet appears under LDAP search base). Port 389 is selected
    GAL Settings: bind DN: cn=zimbra,ou=External,dc=exonline,dc=intranet
    (In AD there is an OU callled External and the user account Zimbra is in the External OU)
    Bind password: zimbra (same as in AD)

    Next screen is the test screen. In the search term field I enter
    "A" - no quotes. I get responses. I enter "Al" and the errors you saw appear.

    I also tried using the Administrator account in the Users container. Same result. I can search by one letter but not by a word.
    Last edited by alexz; 04-21-2006 at 01:24 PM.
    Sincerely,

    Alex

  4. #4
    KevinH's Avatar
    KevinH is offline Expert Member
    Join Date
    Aug 2005
    Location
    San Mateo, CA
    Posts
    4,789
    Rep Power
    18

    Default

    You must use the FQDN of the AD machine. Zimbra will need to connect and hence needs a value that is FQDN and can be resolved in DNS.
    Looking for new beta users -> Co-Founder of Acompli. Previously worked at Zimbra (and Yahoo! & VMware) since 2005.

  5. #5
    alexz is offline Active Member
    Join Date
    Oct 2005
    Posts
    46
    Rep Power
    9

    Question

    Quote Originally Posted by KevinH
    You must use the FQDN of the AD machine. Zimbra will need to connect and hence needs a value that is FQDN and can be resolved in DNS.
    Hi, Kevin - Where in the wizard does the FQDN go? I listed all the options on the GAL wizard on my post above. If you're referring the FQDN of the domain controller I did list it as dc.exonline.net and it answers on port 389. Note that if I use just one character (like A) the test does the search succesfully and returns a list of entries that start with A. However, when I add characters beyond A then I get the error. So I know that Zimbra server authenticates to the AD server and it knows how to query it.

    Maybe the question us how do I make the query append "dc" to "exonline.intranet:389", which is what the first part of the error references?
    Last edited by alexz; 04-21-2006 at 06:17 PM.
    Sincerely,

    Alex

  6. #6
    KevinH's Avatar
    KevinH is offline Expert Member
    Join Date
    Aug 2005
    Location
    San Mateo, CA
    Posts
    4,789
    Rep Power
    18

    Default

    The first error you posted was a connection error. So it seems you've solved that. What error are you getting now?
    Looking for new beta users -> Co-Founder of Acompli. Previously worked at Zimbra (and Yahoo! & VMware) since 2005.

  7. #7
    alexz is offline Active Member
    Join Date
    Oct 2005
    Posts
    46
    Rep Power
    9

    Default

    Quote Originally Posted by KevinH
    The first error you posted was a connection error. So it seems you've solved that. What error are you getting now?
    It's the same error. My point is that I don't get an error if I search just one letter. When I use more then one letter then I get the following error. Is Zimbra supposed to use the fqdn instead of just the domain name (see in bold - the error only specifies the domain name)? I defined the fqdn of the LDAP server by the time it reaches the query stage:

    avax.naming.PartialResultException [Root exception is javax.naming.CommunicationException: exonline.intranet:389 [Root exception is java.net.ConnectException: Connection refused]]
    at com.sun.jndi.ldap.LdapNamingEnumeration.hasMoreImp l(LdapNamingEnumeration.java:224)
    at com.sun.jndi.ldap.LdapNamingEnumeration.hasMoreRef errals(LdapNamingEnumeration.java:362)
    at com.sun.jndi.ldap.LdapNamingEnumeration.hasMoreImp l(LdapNamingEnumeration.java:208)
    at com.sun.jndi.ldap.LdapNamingEnumeration.hasMoreRef errals(LdapNamingEnumeration.java:362)
    at com.sun.jndi.ldap.LdapNamingEnumeration.hasMoreImp l(LdapNamingEnumeration.java:208)
    at com.sun.jndi.ldap.LdapNamingEnumeration.hasMore(Ld apNamingEnumeration.java:171)
    at com.zimbra.cs.account.ldap.LdapUtil.searchLdapGal( LdapUtil.java:823)
    at com.zimbra.cs.account.ldap.Check.checkGalConfig(Ch eck.java:190)
    at com.zimbra.cs.service.admin.CheckGalConfig.handle( CheckGalConfig.java:58)
    at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:255)
    at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:163)
    at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:84)
    at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:228)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:709)
    at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:154)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:802)
    at org.apache.catalina.core.ApplicationFilterChain.in ternalDoFilter(ApplicationFilterChain.java:252)
    at org.apache.catalina.core.ApplicationFilterChain.do Filter(ApplicationFilterChain.java:173)
    at org.apache.catalina.core.StandardWrapperValve.invo ke(StandardWrapperValve.java:213)
    at org.apache.catalina.core.StandardContextValve.invo ke(StandardContextValve.java:178)
    at org.apache.catalina.core.StandardHostValve.invoke( StandardHostValve.java:126)
    at org.apache.catalina.valves.ErrorReportValve.invoke (ErrorReportValve.java:105)
    at org.apache.catalina.core.StandardEngineValve.invok e(StandardEngineValve.java:107)
    at org.apache.catalina.valves.AccessLogValve.invoke(A ccessLogValve.java:541)
    at org.apache.catalina.connector.CoyoteAdapter.servic e(CoyoteAdapter.java:148)
    at org.apache.coyote.http11.Http11Processor.process(H ttp11Processor.java:869)
    at org.apache.coyote.http11.Http11BaseProtocol$Http11 ConnectionHandler.processConnection(Http11BaseProt ocol.java:667)
    at org.apache.tomcat.util.net.PoolTcpEndpoint.process Socket(PoolTcpEndpoint.java:527)
    at org.apache.tomcat.util.net.LeaderFollowerWorkerThr ead.runIt(LeaderFollowerWorkerThread.java:80)
    at org.apache.tomcat.util.threads.ThreadPool$ControlR unnable.run(ThreadPool.java:684)
    at java.lang.Thread.run(Thread.java:595)
    Caused by: javax.naming.CommunicationException: exonline.intranet:389 [Root exception is java.net.ConnectException: Connection refused]
    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)
    ... 30 more
    Caused by: java.net.ConnectException: Connection refused
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(PlainSocketImpl .java:333)
    at java.net.PlainSocketImpl.connectToAddress(PlainSoc ketImpl.java:195)
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.j ava:182)
    at java.net.SocksSocketImpl.connect(SocksSocketImpl.j ava:366)
    at java.net.Socket.connect(Socket.java:507)
    at sun.reflect.GeneratedMethodAccessor33.invoke(Unkno wn Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at com.sun.jndi.ldap.Connection.createSocket(Connecti on.java:333)
    at com.sun.jndi.ldap.Connection.<init>(Connection.jav a:181)
    at com.sun.jndi.ldap.LdapClient.<init>(LdapClient.jav a:118)
    at com.sun.jndi.ldap.LdapClientFactory.createPooledCo nnection(LdapClientFactory.java:44)
    at com.sun.jndi.ldap.pool.Connections.<init>(Connecti ons.java:97)
    at com.sun.jndi.ldap.pool.Pool.getPooledConnection(Po ol.java:114)
    at com.sun.jndi.ldap.LdapPoolManager.getLdapClient(Ld apPoolManager.java:310)
    at com.sun.jndi.ldap.LdapClient.getInstance(LdapClien t.java:1572)
    at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:259 6)
    at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:283)
    at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapC txFactory.java:175)
    at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstanc e(LdapCtxFactory.java:134)
    at com.sun.jndi.url.ldap.ldapURLContextFactory.getObj ectInstance(ldapURLContextFactory.java:35)
    at javax.naming.spi.NamingManager.getURLObject(Naming Manager.java:584)
    at javax.naming.spi.NamingManager.processURL(NamingMa nager.java:364)
    at javax.naming.spi.NamingManager.processURLAddrs(Nam ingManager.java:344)
    at javax.naming.spi.NamingManager.getObjectInstance(N amingManager.java:316)
    at com.sun.jndi.ldap.LdapReferralContext.<init>(LdapR eferralContext.java:93)
    ... 33 more
    Last edited by alexz; 04-21-2006 at 07:41 PM.
    Sincerely,

    Alex

  8. #8
    alexz is offline Active Member
    Join Date
    Oct 2005
    Posts
    46
    Rep Power
    9

    Default

    [QUOTE=KevinH]Well you seem to have entered "dc.exonline.intranet" but the exception is reporting two different AD hosts.

    Here is an error that shows up when I try to do a GAL lookup from a new e-mail:

    msg - system failure: unable to search GAL
    com.zimbra.cs.service.ServiceException: system failure: unable to search GAL
    at com.zimbra.cs.service.ServiceException.FAILURE(Ser viceException.java:131)
    at com.zimbra.cs.account.ldap.LdapDomain.searchLdapGa l(LdapDomain.java:323)
    at com.zimbra.cs.account.ldap.LdapDomain.searchGal(Ld apDomain.java:155)
    at com.zimbra.cs.service.account.SearchGal.handle(Sea rchGal.java:74)
    at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:255)
    at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:163)
    at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:84)
    at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:228)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:709)
    at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:154)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:802)
    at org.apache.catalina.core.ApplicationFilterChain.in ternalDoFilter(ApplicationFilterChain.java:252)
    at org.apache.catalina.core.ApplicationFilterChain.do Filter(ApplicationFilterChain.java:173)
    at org.apache.catalina.core.StandardWrapperValve.invo ke(StandardWrapperValve.java:213)
    at org.apache.catalina.core.StandardContextValve.invo ke(StandardContextValve.java:178)
    at org.apache.catalina.core.StandardHostValve.invoke( StandardHostValve.java:126)
    at org.apache.catalina.valves.ErrorReportValve.invoke (ErrorReportValve.java:105)
    at org.apache.catalina.core.StandardEngineValve.invok e(StandardEngineValve.java:107)
    at org.apache.catalina.valves.AccessLogValve.invoke(A ccessLogValve.java:541)
    at org.apache.catalina.connector.CoyoteAdapter.servic e(CoyoteAdapter.java:148)
    at org.apache.coyote.http11.Http11Processor.process(H ttp11Processor.java:869)
    at org.apache.coyote.http11.Http11BaseProtocol$Http11 ConnectionHandler.processConnection(Http11BaseProt ocol.java:667)
    at org.apache.tomcat.util.net.PoolTcpEndpoint.process Socket(PoolTcpEndpoint.java:527)
    at org.apache.tomcat.util.net.LeaderFollowerWorkerThr ead.runIt(LeaderFollowerWorkerThread.java:80)
    at org.apache.tomcat.util.threads.ThreadPool$ControlR unnable.run(ThreadPool.java:684)
    at java.lang.Thread.run(Thread.java:595)
    Caused by: javax.naming.PartialResultException [Root exception is javax.naming.CommunicationException: exonline.intranet:389 [Root exception is java.net.ConnectException: Connection refused]]
    at com.sun.jndi.ldap.LdapNamingEnumeration.hasMoreImp l(LdapNamingEnumeration.java:224)
    at com.sun.jndi.ldap.LdapNamingEnumeration.hasMoreRef errals(LdapNamingEnumeration.java:362)
    at com.sun.jndi.ldap.LdapNamingEnumeration.hasMoreImp l(LdapNamingEnumeration.java:208)
    at com.sun.jndi.ldap.LdapNamingEnumeration.hasMoreRef errals(LdapNamingEnumeration.java:362)
    at com.sun.jndi.ldap.LdapNamingEnumeration.hasMoreImp l(LdapNamingEnumeration.java:208)
    at com.sun.jndi.ldap.LdapNamingEnumeration.hasMore(Ld apNamingEnumeration.java:171)
    at com.zimbra.cs.account.ldap.LdapUtil.searchLdapGal( LdapUtil.java:823)
    at com.zimbra.cs.account.ldap.LdapDomain.searchLdapGa l(LdapDomain.java:321)
    ... 24 more
    Caused by: javax.naming.CommunicationException: exonline.intranet:389 [Root exception is java.net.ConnectException: Connection refused]
    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)
    ... 31 more
    Caused by: java.net.ConnectException: Connection refused
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(PlainSocketImpl .java:333)
    at java.net.PlainSocketImpl.connectToAddress(PlainSoc ketImpl.java:195)
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.j ava:182)
    at java.net.SocksSocketImpl.connect(SocksSocketImpl.j ava:366)
    at java.net.Socket.connect(Socket.java:507)
    at sun.reflect.GeneratedMethodAccessor33.invoke(Unkno wn Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at com.sun.jndi.ldap.Connection.createSocket(Connecti on.java:333)
    at com.sun.jndi.ldap.Connection.<init>(Connection.jav a:181)
    at com.sun.jndi.ldap.LdapClient.<init>(LdapClient.jav a:118)
    at com.sun.jndi.ldap.LdapClientFactory.createPooledCo nnection(LdapClientFactory.java:44)
    at com.sun.jndi.ldap.pool.Connections.<init>(Connecti ons.java:97)
    at com.sun.jndi.ldap.pool.Pool.getPooledConnection(Po ol.java:114)
    at com.sun.jndi.ldap.LdapPoolManager.getLdapClient(Ld apPoolManager.java:310)
    at com.sun.jndi.ldap.LdapClient.getInstance(LdapClien t.java:1572)
    at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:259 6)
    at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:283)
    at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapC txFactory.java:175)
    at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstanc e(LdapCtxFactory.java:134)
    at com.sun.jndi.url.ldap.ldapURLContextFactory.getObj ectInstance(ldapURLContextFactory.java:35)
    at javax.naming.spi.NamingManager.getURLObject(Naming Manager.java:584)
    at javax.naming.spi.NamingManager.processURL(NamingMa nager.java:364)
    at javax.naming.spi.NamingManager.processURLAddrs(Nam ingManager.java:344)
    at javax.naming.spi.NamingManager.getObjectInstance(N amingManager.java:316)
    at com.sun.jndi.ldap.LdapReferralContext.<init>(LdapR eferralContext.java:93)
    ... 34 more

    code - service.FAILURE
    method - ZmCsfeCommand.prototype.invoke
    detail - soap:Receiver
    Sincerely,

    Alex

  9. #9
    KevinH's Avatar
    KevinH is offline Expert Member
    Join Date
    Aug 2005
    Location
    San Mateo, CA
    Posts
    4,789
    Rep Power
    18

    Default

    I think you should verify what you've entered in the GAL config screens. You also may want to restart tomcat to make sure it's not caching an old setting. It's clear in the error that Zimbra can't connect and is connecting to a different LDAP host than you claim to have configured.
    Looking for new beta users -> Co-Founder of Acompli. Previously worked at Zimbra (and Yahoo! & VMware) since 2005.

  10. #10
    alexz is offline Active Member
    Join Date
    Oct 2005
    Posts
    46
    Rep Power
    9

    Default

    Quote Originally Posted by KevinH
    I think you should verify what you've entered in the GAL config screens. You also may want to restart tomcat to make sure it's not caching an old setting. It's clear in the error that Zimbra can't connect and is connecting to a different LDAP host than you claim to have configured.
    I don't know...There are only a few screens. I went over the config 100 times. Here is the summary:

    GAL mode: Both
    Most results returned by GAL search: 100
    Server type: Active Directory
    LDAP URL: ldap://dc.exonline.intranet:389
    LDAP filter:*
    LDAP search base: dc=exonline,dc=intranet
    Use DN/Password to bind to external server: Yes
    Bind DN: cn=zimbrauser;ou=External;dc=exonline; dc=intranet

    Check this out - On that GAL Settings Summary screen - if I select all the text (so that I can paste the results here) and copy and paste I see LDAP filter:* ....But LDAP Filter is doesn't appear on that summary page. It's only when I copy and paste (I tried copy and pasting into a Word doc too and that LDAP Filter appears when I paste but does not appear on the GAL Setttings Summary screen). Weird stuff.

    What you're saying is that the search disregards the LDAP URL and tries to search against exonline.intranet:389 instead of dc.exonline.intranet. Just so you know exonline.intranet is the name of the domain that I created.

    I restarted tomcat as well but got some errors on the restart. I don't know if these are supposed to happen or not but the Zimbra server seems to work fine.

    [zimbra@zimbra root]$ tomcat restart
    Using CATALINA_BASE: /opt/zimbra/tomcat
    Using CATALINA_HOME: /opt/zimbra/tomcat
    Using CATALINA_TMPDIR: /opt/zimbra/tomcat/temp
    Using JRE_HOME: /opt/zimbra/java
    Waiting ..... trying again
    Using CATALINA_BASE: /opt/zimbra/tomcat
    Using CATALINA_HOME: /opt/zimbra/tomcat
    Using CATALINA_TMPDIR: /opt/zimbra/tomcat/temp
    Using JRE_HOME: /opt/zimbra/java
    Apr 22, 2006 11:13:12 AM org.apache.catalina.startup.Catalina stopServer
    SEVERE: Catalina.stop:
    java.net.ConnectException: Connection refused
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(PlainSocketImpl .java:333)
    at java.net.PlainSocketImpl.connectToAddress(PlainSoc ketImpl.java:195)
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.j ava:182)
    at java.net.SocksSocketImpl.connect(SocksSocketImpl.j ava:366)
    at java.net.Socket.connect(Socket.java:507)
    at java.net.Socket.connect(Socket.java:457)
    at java.net.Socket.<init>(Socket.java:365)
    at java.net.Socket.<init>(Socket.java:178)
    at org.apache.catalina.startup.Catalina.stopServer(Ca talina.java:394)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.apache.catalina.startup.Bootstrap.stopServer(B ootstrap.java:324)
    at org.apache.catalina.startup.Bootstrap.main(Bootstr ap.java:415)
    Waiting ..... trying again
    Using CATALINA_BASE: /opt/zimbra/tomcat
    Using CATALINA_HOME: /opt/zimbra/tomcat
    Using CATALINA_TMPDIR: /opt/zimbra/tomcat/temp
    Using JRE_HOME: /opt/zimbra/java
    Apr 22, 2006 11:13:19 AM org.apache.catalina.startup.Catalina stopServer
    SEVERE: Catalina.stop:
    java.net.ConnectException: Connection refused
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(PlainSocketImpl .java:333)
    at java.net.PlainSocketImpl.connectToAddress(PlainSoc ketImpl.java:195)
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.j ava:182)
    at java.net.SocksSocketImpl.connect(SocksSocketImpl.j ava:366)
    at java.net.Socket.connect(Socket.java:507)
    at java.net.Socket.connect(Socket.java:457)
    at java.net.Socket.<init>(Socket.java:365)
    at java.net.Socket.<init>(Socket.java:178)
    at org.apache.catalina.startup.Catalina.stopServer(Ca talina.java:394)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.apache.catalina.startup.Bootstrap.stopServer(B ootstrap.java:324)
    at org.apache.catalina.startup.Bootstrap.main(Bootstr ap.java:415)
    Waiting .. shutdown ok
    [zimbra@zimbra root]$
    Sincerely,

    Alex

Page 1 of 2 12 LastLast

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Replies: 23
    Last Post: 01-24-2013, 03:44 PM
  2. Zimbra fails after working for 2 weeks
    By Linsys in forum Administrators
    Replies: 10
    Last Post: 10-07-2008, 12:42 AM
  3. M3 problem with shares
    By titangears in forum Users
    Replies: 4
    Last Post: 01-12-2006, 01:01 PM
  4. Replies: 14
    Last Post: 12-22-2005, 04:59 PM
  5. Building native libraries on MacOS X
    By ajmas in forum Developers
    Replies: 3
    Last Post: 10-14-2005, 11:00 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
  •