zimbra 6.0.8 FOSS - Ubuntu 10.04 LTS - LDAP errors

[imx]

Seeing the below errors, quite frequently now - didnt do for the first few days the box was up! I have to restart Zimbra to get things working again

Running Zimbra 6.0.8 FOSS 64bit - Ubuntu 10.04 LTS - Anyone any thoughts? Ive tried the zmfixperms extended in case that was anything!

Anyone else seeing this?

Cheers,

iMx

com.zimbra.common.service.ServiceException: system failure: ZimbraLdapContext
ExceptionId:btpool0-14://e.xxxxx.net:7071/service/admin/soap/ModifyCosRequest:1286803324801:b68edc1da7fcf35d
Code:service.FAILURE
at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:248)
at com.zimbra.cs.account.ldap.ZimbraLdapContext.<init >(ZimbraLdapContext.java:416)
at com.zimbra.cs.account.ldap.ZimbraLdapContext.<init >(ZimbraLdapContext.java:373)
at com.zimbra.cs.account.ldap.LdapProvisioning.modify AttrsInternal(LdapProvisioning.java:337)
at com.zimbra.cs.account.ldap.LdapProvisioning.modify Attrs(LdapProvisioning.java:316)
at com.zimbra.cs.account.ldap.LdapProvisioning.modify Attrs(LdapProvisioning.java:297)
at com.zimbra.cs.service.admin.ModifyCos.handle(Modif yCos.java:56)
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:420)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:274)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:158)
at com.zimbra.soap.SoapServlet.doWork(SoapServlet.jav a:291)
at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:212)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:727)
at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:181)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:511)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1166)
at com.zimbra.cs.servlet.SetHeaderFilter.doFilter(Set HeaderFilter.java:79)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1157)
at org.mortbay.servlet.UserAgentFilter.doFilter(UserA gentFilter.java:81)
at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter .java:132)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1157)
at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:388)
at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(Se ssionHandler.java:182)
at org.mortbay.jetty.handler.ContextHandler.handle(Co ntextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.java:418)
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(Ha ndlerWrapper.java:152)
at org.mortbay.jetty.handler.rewrite.RewriteHandler.h andle(RewriteHandler.java:230)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152)
at org.mortbay.jetty.handler.DebugHandler.handle(Debu gHandler.java:77)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at org.mortbay.jetty.HttpConnection.handleRequest(Htt pConnection.java:543)
at org.mortbay.jetty.HttpConnection$RequestHandler.co ntent(HttpConnection.java:939)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:755)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpPa rser.java:212)
at org.mortbay.jetty.HttpConnection.handle(HttpConnec tion.java:405)
at org.mortbay.io.nio.SelectChannelEndPoint.run(Selec tChannelEndPoint.java:413)
at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(BoundedThreadPool.java:451)
Caused by: javax.naming.CommunicationException: Bad file descriptor [Root exception is java.net.SocketException: Bad file descriptor]
at com.sun.jndi.ldap.LdapCtx.extendedOperation(LdapCt x.java:3213)
at javax.naming.ldap.InitialLdapContext.extendedOpera tion(InitialLdapContext.java:164)
at com.zimbra.cs.account.ldap.ZimbraLdapContext.<init >(ZimbraLdapContext.java:406)
... 40 more
Caused by: java.net.SocketException: Bad file descriptor
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutp utStream.java:92)
at java.net.SocketOutputStream.write(SocketOutputStre am.java:136)
at java.io.BufferedOutputStream.flushBuffer(BufferedO utputStream.java:65)
at java.io.BufferedOutputStream.flush(BufferedOutputS tream.java:123)
at com.sun.jndi.ldap.Connection.writeRequest(Connecti on.java:396)
at com.sun.jndi.ldap.LdapClient.extendedOp(LdapClient .java:1172)
at com.sun.jndi.ldap.LdapCtx.extendedOperation(LdapCt x.java:3160)
... 42 more

[imx]

Soap Exceptions on 6.0.8_GA_2661.UBUNTU10_64

Just seen this thread...will read....

[imx]

Ok read the posts...checked the bug....no fix :/ Anyone any ideas?

[BCamp]

Have you looked at this?

Bug 42870 &ndash; "Bad file descriptor" SocketException causes system failure every several hours

Post 81 has a fix for the bad file descriptor errors I was receiving. Worked for me and has been working fine since.

[imx]

Nicely spotted BCamp, will take a look

[imx]

Certainly improved if not fixed for me...... will update further tomorrow if its not; am ashamed i didnt spot this earlier

[BCamp]

I hope that clears it up for you. Best of luck!

[acesuares]

My Zimbra installation has in /etc/security/limits.conf already two entries, but Post 81 says they should be 'root' and in my limits.conf they are 'zimbra'. Should I change them to root? I think not...?

UPDATE: apparently, one has to add these two lines mentioned in post 81 to the file. So my /etc/security/limits.conf now reads:

# End of file
zimbra soft nofile 524288
zimbra hard nofile 524288

# Bug 42870 &ndash; "Bad file descriptor" SocketException causes system failure every several hours
root soft nofile 524288
root hard nofile 524288

The two lines starting with 'zimbra' where already there, the two lines starting with 'root' where added.

[geovanni]

I installed Zimbra 6.0.8 on Ubuntu 10.04 and am having the same problem, the system after a few hours can not do ldap authentication in, forcing the server to be restarted.

I'm thinking of putting ubuntu 8 and install zimbra 6.0.4, does so, the problem is solved?

[acesuares]

Geovanni, with the solution described in 'Post 81', the problem is solved, I have been running 30 hours now without the error.