Error on Add / Delete Accounts - LDAP: error code 80
Hi..I am having this strange problem of not able to add/delete any email accounts anymore. Everything was working fine after my fresh install.
Setup: FC5 min install and updates + Release 4.0.4_GA_457.FC5_20061115174033 FC5 FOSS edition
1) Currently Email server is receiving and sending mails just fine and i was able to create all accounts just fine initially.
2) I can log into user and admin interfaces properly without issues
3) All services are showing they are ok
[zimbra@email ~]$ zmcontrol status
antispam Running
antivirus Running
ldap Running
logger Running
mailbox Running
mta Running
snmp Running
spell Running
4) I have stopped and started tomcat and rebooted the server also just in case
Problems: when I try to ADD or DELETE any account or alias I get following error
Message: system failure: createAccount
com.zimbra.cs.service.ServiceException: system failure: createAccount
at com.zimbra.cs.service.ServiceException.FAILURE(Ser viceException.java:174)
at com.zimbra.cs.account.ldap.LdapProvisioning.create Subcontext(LdapProvisioning.java:2575)
at com.zimbra.cs.account.ldap.LdapProvisioning.create Account(LdapProvisioning.java:628)
at com.zimbra.cs.account.ldap.LdapProvisioning.create Account(LdapProvisioning.java:504)
at com.zimbra.cs.service.admin.CreateAccount.handle(C reateAccount.java:65)
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 'uid=testing,ou=people,dc=xxxxxxxxxxxxxxxxx,dc=com '
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.LdapProvisioning.create Subcontext(LdapProvisioning.java:2561)
... 25 more
Error code: service.FAILURE
Method: ZmCsfeCommand.prototype.invoke
Details:soap:Receiver
Message: system failure: unable to purge account: c5621cb1-c00b-4ff7-91dc-a6796d165001
com.zimbra.cs.service.ServiceException: system failure: unable to purge account: c5621cb1-c00b-4ff7-91dc-a6796d165001
at com.zimbra.cs.service.ServiceException.FAILURE(Ser viceException.java:174)
at com.zimbra.cs.account.ldap.LdapProvisioning.delete Account(LdapProvisioning.java:1497)
at com.zimbra.cs.service.admin.DeleteAccount.handle(D eleteAccount.java:77)
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 - entry index delete failed]; remaining name 'uid=raj,ou=people,dc=email,dc=xxxxxxxxxxxxxx,dc=c om' 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_unbind(LdapCtx.java:59 6)
at com.sun.jndi.toolkit.ctx.ComponentContext.p_unbind (ComponentContext.java:634)
at com.sun.jndi.toolkit.ctx.PartialCompositeContext.u nbind(PartialCompositeContext.java:227)
at com.sun.jndi.toolkit.ctx.PartialCompositeContext.u nbind(PartialCompositeContext.java:218)
at javax.naming.InitialContext.unbind(InitialContext. java:375)
at com.zimbra.cs.account.ldap.LdapProvisioning.delete Account(LdapProvisioning.java:1494)
... 23 more
Error code: service.FAILURE
Method: ZmCsfeCommand.prototype.invoke
Details:soap:Receiver
Can someone point me to the problem..
Thanks
Raj
Current non-Debian kernel = no problems
Quote:
Originally Posted by
raj 
* Q is why would a perfectly running install gets its permissions screwed up. Is their any known bug for FC5 + Release 4.0.4_GA
Old Linux kernel versions had a pretty vicious bug in how they handled dropping permissions that would result in random files getting set to root ownership. The current kernel version for all OSes (except Debian) for which there are Zimbra OSS releases should fix this issue.
