Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Administrators
Reload this Page Ldap Search Error - No Bug i think

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 07-29-2009, 09:04 AM
Active Member
  
Posts: 42
Default Ldap Search Error - No Bug i think
Since i've upgraded from Zimbra 5.0 to 6.0 Beta 2 i get an Ldap search error when access the internal GAL in the Webclient.

After upgrading to 6.0 RC1 the error still exists. It's no bug but an error that can be resolved, or not? but i don't know how.

Someone has made an bugticket, but this is uncomfirmed as bug.

Code:
com.zimbra.common.service.ServiceException: system failure: ldap search failed
ExceptionId:btpool0-31:1248882489881:6a9d1ff30f31b227
Code:service.FAILURE
        at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:251)
        at com.zimbra.cs.gal.GalSearchControl.ldapSearch(GalSearchControl.java:390)
        at com.zimbra.cs.gal.GalSearchControl.search(GalSearchControl.java:113)
        at com.zimbra.cs.service.account.SearchGal.handle(SearchGal.java:76)
        at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:415)
        at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:273)
        at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:157)
        at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:273)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
        at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:187)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
        at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
        at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1148)
        at org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:81)
        at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:129)
        at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1139)
        at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:378)
        at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
        at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
        at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
        at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)
        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(HandlerWrapper.java:152)
        at org.mortbay.jetty.handler.rewrite.RewriteHandler.handle(RewriteHandler.java:230)
        at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
        at org.mortbay.jetty.Server.handle(Server.java:324)
        at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:535)
        at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:886)
        at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:747)
        at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
        at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
        at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
        at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451)
Caused by: java.lang.NullPointerException
        at java.util.Hashtable.put(Hashtable.java:394)
        at com.zimbra.cs.account.ldap.ZimbraLdapContext.<init>(ZimbraLdapContext.java:404)
        at com.zimbra.cs.account.ldap.LdapUtil.doGalSearch(LdapUtil.java:992)
        at com.zimbra.cs.account.ldap.LdapUtil.galSearch(LdapUtil.java:979)
        at com.zimbra.cs.gal.GalSearchControl.ldapSearch(GalSearchControl.java:388)
        ... 32 more

Code:
method:	SearchGalRequest
msg:	system failure: ldap search failed
code:	service.FAILURE
detail:	soap:Receiver
trace:	btpool0-14:1248882515612:6a9d1ff30f31b227
request:	

Body: {
  SearchGalRequest: {
    _jsns: "urn:zimbraAccount",
    limit: 50,
    name: ".",
    offset: 0,
    sortBy: "nameAsc",
    type: "account"
   }
 },
Header: {
  context: {
    _jsns: "urn:zimbra",
    account: {
      _content: "xxxxx@xxx.at",
      by: "name"
     },
    authToken: "(removed)",
    notify: {
      seq: 6
     },
    session: {
      _content: 110,
      id: 110
     },
    userAgent: {
      name: "ZimbraWebClient - FF3.0 (Win)",
      version: "6.0.0_RC1_1684.SuSEES10"
     }
   }
 }
Reply With Quote
  #2 (permalink)  
Old 07-29-2009, 11:54 AM
Active Member
  
Posts: 42
Default
i found the problem,

i have a gal across two domains, so an internal and external ldap, if i use internal only for one domain it works but if i add an external ldap which is an other domain on the same machine with the following it doesn't works.

Somebody knows the correct LDAP Filter options that works with ZCS 6.0 ? - the one in the wiki does not work.
Reply With Quote
  #3 (permalink)  
Old 09-04-2009, 09:08 AM
Loyal Member
  
Posts: 96
Default
I'm getting this same problem on the 6.0 release NE. I found that if I enter in a bind DN that searching works but if I leave it as anonymous it fails:


Code:
2009-09-04 12:02:05,101 ERROR [ScheduledTask-3] [name=galsync@domain.com;mid=39;ds=zimbra2;] gal - Error executing gal search
java.lang.NullPointerException
	at java.util.Hashtable.put(Hashtable.java:394)
	at com.zimbra.cs.account.ldap.ZimbraLdapContext.<init>(ZimbraLdapContext.java:404)
	at com.zimbra.cs.account.ldap.LdapUtil.doGalSearch(LdapUtil.java:992)
	at com.zimbra.cs.account.ldap.LdapUtil.galSearch(LdapUtil.java:979)
	at com.zimbra.cs.gal.GalImport.searchGal(GalImport.java:143)
	at com.zimbra.cs.gal.GalImport.importGal(GalImport.java:104)
	at com.zimbra.cs.gal.GalImport.importData(GalImport.java:54)
	at com.zimbra.cs.datasource.DataSourceManager.importData(DataSourceManager.java:167)
	at com.zimbra.cs.datasource.DataSourceManager.importData(DataSourceManager.java:130)
	at com.zimbra.cs.datasource.DataSourceTask.call(DataSourceTask.java:82)
	at com.zimbra.cs.datasource.DataSourceTask.call(DataSourceTask.java:28)
	at com.zimbra.common.util.TaskScheduler$TaskRunner.call(TaskScheduler.java:96)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:207)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:619)
2009-09-04 12:02:05,101 INFO  [ScheduledTask-3] [name=galsync@domain.com;mid=39;ds=zimbra2;] datasource - Import completed for data source 'zimbra2'
When I run an ldapsearch from the command line on the zimbra server with the search filter I'm using it works just fine:

Code:
/opt/zimbra/openldap/bin/ldapsearch -b "ou=People,dc=domain,dc=com" -x -h host.domain.com "(|(cn=username*)(sn=username*)(gn=username*)(mail=username*))"
Last edited by cayaraa; 09-04-2009 at 10:51 AM..
Reply With Quote
  #4 (permalink)  
Old 09-20-2009, 10:07 AM
Junior Member
  
Posts: 7
Default Interesting
I am having the same issue. When I put in the bind credentials it started working, however, it will not let me hit 'OK' on the selection box after I pick the address...

This seems like a bug...
Reply With Quote
  #5 (permalink)  
Old 10-01-2009, 02:24 AM
Intermediate Member
  
Posts: 19
Default
looks like this could be the reason when I look at the logs.

missing filter def cn=*%s* in zimbraGalLdapFilterDef

can someone show the path on how to solve this?
Reply With Quote
  #6 (permalink)  
Old 10-01-2009, 02:58 AM
Active Member
  
Posts: 40
Default
I had the same exception.
It turned out to be a wrong config (missed bind DN/password).



Quote:
Originally Posted by cayaraa View Post
I'm getting this same problem on the 6.0 release NE. I found that if I enter in a bind DN that searching works but if I leave it as anonymous it fails:


Code:
2009-09-04 12:02:05,101 ERROR [ScheduledTask-3] [name=galsync@domain.com;mid=39;ds=zimbra2;] gal - Error executing gal search
java.lang.NullPointerException
	at java.util.Hashtable.put(Hashtable.java:394)
	at com.zimbra.cs.account.ldap.ZimbraLdapContext.<init>(ZimbraLdapContext.java:404)
	at com.zimbra.cs.account.ldap.LdapUtil.doGalSearch(LdapUtil.java:992)
	at com.zimbra.cs.account.ldap.LdapUtil.galSearch(LdapUtil.java:979)
	at com.zimbra.cs.gal.GalImport.searchGal(GalImport.java:143)
	at com.zimbra.cs.gal.GalImport.importGal(GalImport.java:104)
	at com.zimbra.cs.gal.GalImport.importData(GalImport.java:54)
	at com.zimbra.cs.datasource.DataSourceManager.importData(DataSourceManager.java:167)
	at com.zimbra.cs.datasource.DataSourceManager.importData(DataSourceManager.java:130)
	at com.zimbra.cs.datasource.DataSourceTask.call(DataSourceTask.java:82)
	at com.zimbra.cs.datasource.DataSourceTask.call(DataSourceTask.java:28)
	at com.zimbra.common.util.TaskScheduler$TaskRunner.call(TaskScheduler.java:96)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:207)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:619)
2009-09-04 12:02:05,101 INFO  [ScheduledTask-3] [name=galsync@domain.com;mid=39;ds=zimbra2;] datasource - Import completed for data source 'zimbra2'
When I run an ldapsearch from the command line on the zimbra server with the search filter I'm using it works just fine:

Code:
/opt/zimbra/openldap/bin/ldapsearch -b "ou=People,dc=domain,dc=com" -x -h host.domain.com "(|(cn=username*)(sn=username*)(gn=username*)(mail=username*))"
Last edited by agnes; 10-01-2009 at 08:01 AM..
Reply With Quote
Reply

« Previous Thread | Today's Posts or Week's Posts | Next Thread »

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes
Linear Mode Linear Mode


Similar Threads

Product Information

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com


Home - Blog - Contact Us - Archive - Top


 

SEO by vBSEO ©2011, Crawlability, Inc.