Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Installation

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 01-11-2007, 01:59 PM
New Member
 
Posts: 3
Default Changing the LDAP default password

Following the directions here:

http://wiki.zimbra.com/index.php?tit...ySQL_Passwords

I change my ldap password by doing:

zmcontrol stop
zmldappasswd --root newpass
zmldappasswd newpass

Running:
zmlocalconfig -s |fgrep ldap

confims the password has been changed to the new password.

I restarted all services, including tomcat.

It's clear that I have LDAP connectivity issues, but slapd is running:

zimbra 30721 0.0 1.0 56892 2600 ? Ssl 15:18 0:00 /opt/zimbra/openldap-2.3.21/libexec/slapd -l LOCAL0 -4 -u zimbra -h ldap://derb.slurb.com:389 -f /opt/zimbra/conf/slapd.conf

DNS things look to be correct:

[root@derb log]# host derb.slurb.com
derb.slurb.com has address 172.19.3.3
[root@derb log]# ifconfig eth0 |fgrep inet
inet addr:172.19.3.3 Bcast:172.19.3.255 Mask:255.255.255.0

Additionally, this was working fine prior to the ldap password change.

When I login to the admin console I get an error and stack trace. (see below). It almost makes me think I changed what the zimbra clients think the password is but I didn't really change it in ldap. I'm not sure. Thoughts appreciated.

-rob



Message: system failure: unable to list all servers
com.zimbra.cs.service.ServiceException: system failure: unable to list all servers
at com.zimbra.cs.service.ServiceException.FAILURE(Ser viceException.java:174)
at com.zimbra.cs.account.ldap.LdapProvisioning.getAll Servers(LdapProvisioning.java:1809)
at com.zimbra.cs.service.admin.GetAllServers.handle(G etAllServers.java:55)
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:261)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:162)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:84)
at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:223)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:709)
at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:173)
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.NamingException: [LDAP: error code 80 - internal error]; remaining name 'cn=servers,cn=zimbra'
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.jav a:3029)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCt x.java:2931)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCt x.java:2737)
at com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1 808)
at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:17 31)
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 com.sun.jndi.toolkit.ctx.PartialCompositeDirContex t.search(PartialCompositeDirContext.java:321)
at javax.naming.directory.InitialDirContext.search(In itialDirContext.java:248)
at com.zimbra.cs.account.ldap.LdapProvisioning.getAll Servers(LdapProvisioning.java:1801)
... 23 more

Error code: service.FAILURE
Method: ZmCsfeCommand.prototype.invoke
Details:soap:Receiver
Reply With Quote
  #2 (permalink)  
Old 01-11-2007, 07:23 PM
Former Zimbran
 
Posts: 5,606
Default

Have you changed the name of your sever recently?
Caused by: javax.naming.NamingException: [LDAP: error code 80 - internal error]; remaining name 'cn=servers,cn=zimbra'

run a zmlocalconfig and look to see if things look normal. You can run the -s switch, but don't post that, as it will display your passwords.
Reply With Quote
  #3 (permalink)  
Old 01-12-2007, 06:04 PM
New Member
 
Posts: 3
Default

I didn't change the hostname, so I don't think that was it. That being said, because it was a fresh install, I opted to just re-install from scratch.

Thanks anyway,

-rob
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads

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




 

SEO by vBSEO ©2011, Crawlability, Inc.