Create new domain

[mcevoys]

Brand new clean install on FC5/Zimbra 4.04

Primary domain works fine.

When we go to setup new (second) domain (default COS and other options), we get the following server error:

Message: system failure: unable to create domain: domain.org
com.zimbra.cs.service.ServiceException: system failure: unable to create domain: domain.org
at com.zimbra.cs.service.ServiceException.FAILURE(Ser viceException.java:174)
at com.zimbra.cs.account.ldap.LdapProvisioning.create Domain(LdapProvisioning.java:1165)
at com.zimbra.cs.service.admin.CreateDomain.handle(Cr eateDomain.java:53)
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 - index generation failed]; remaining name 'dc=org'
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.c_createSubcontext(LdapC tx.java:770)
at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_cre ateSubcontext(ComponentDirContext.java:319)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContex t.createSubcontext(PartialCompositeDirContext.java :248)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContex t.createSubcontext(PartialCompositeDirContext.java :236)
at javax.naming.directory.InitialDirContext.createSub context(InitialDirContext.java:178)
at com.zimbra.cs.account.ldap.LdapUtil.simpleCreate(L dapUtil.java:433)
at com.zimbra.cs.account.ldap.LdapProvisioning.create ParentDomains(LdapProvisioning.java:1298)
at com.zimbra.cs.account.ldap.LdapProvisioning.create Domain(LdapProvisioning.java:1124)
... 23 more

Error code: service.FAILURE
Method: ZmCsfeCommand.prototype.invoke
Details:soap:Receiver


Any ideas?

[schemers]

The root of the error is "index generation failed":

Caused by: javax.naming.NamingException: [LDAP: error code 80 - index generation failed]; remaining name 'dc=org'

which sounds like a permssion problem in the directory where LDAP indexes are stored (/opt/zimbra/openldap-data/*.bdb, IIRC).

roland

[mcevoys]

How would one go about correcting this?

[schemers]

making sure that the directory is owned by "zimbra", and the files inside are also all owned by zimbra. Something like:

chown -R zimbra /opt/zimbra/openldap-data

This should normally happen during install though, so there could definitely be other problems.