Results 1 to 4 of 4

Thread: New Issue after upgrade to 6.0.3

  1. 12-01-2009, 09:05 AM #1
    phether
    phether is offline Active Member
    Join Date
    Mar 2007
    Posts
    27
    Rep Power
    7

    Default New Issue after upgrade to 6.0.3

    I have upgraded from 5.0.6 FOSS to 6.0.3 FOSS and have now had the following issue two days in a row.

    Both days around 11:30AM all my users start receiving "A network service error has occurred" message if already in e-mail system or logging in.

    I connect to server and run zmcontrol status and all modules including LDAP are running.

    After looking around I finally ran zmcontrol stop and then start and the error goes away, until the next day.

    With it happening both days around the same time, where should I start looking for posible causes? Which log files may hold the information I need to solve the issue?

    Thanks for your help

    Paul
    Reply With Quote Reply With Quote
  2. 12-01-2009, 09:45 AM #2
    king0770's Avatar
    king0770
    king0770 is offline Zimbra Employee
    Send a message via Yahoo to king0770
    Join Date
    Sep 2007
    Posts
    186
    Rep Power
    6

    Default

    Next time a user sees this error, ask the user the approx time they viewed the error. Then check the /opt/zimbra/log/mailbox.log file. See if there's an error stacktrace. Checking the mailbox.log file would be the first place I would check. Maybe find out exactly what the user was doing at time.
    Reply With Quote Reply With Quote
  3. 12-01-2009, 11:19 AM #3
    phether
    phether is offline Active Member
    Join Date
    Mar 2007
    Posts
    27
    Rep Power
    7

    Default

    OK, Looked at the mailbox.log file and only saw two errors prior ro 11:16AM this morning that seem to have to do with spell checking module:

    Code:
    2009-12-01 09:59:53,279 INFO  [btpool0-22:http://10.1.190.70:80/service/soap/CheckSpellingRequest] [name=mantonelli@bbsd.org;mid=11;ip=10.1.190.112;ua=ZimbraWebClient - IE7 (Win)/6.0.3_GA_1915.UBUNTU6;] SoapEngine - handler exception
com.zimbra.common.service.ServiceException: system failure: Spell check failed: iconv() [http://www.zimbra.com/forums/function.iconv]: Detected an illegal character in input string
ExceptionId:btpool0-22:http://10.1.190.70:80/service/soap/CheckSpellingRequest:1259679593279:fe6fa1a395153071
Code:service.FAILURE
	at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:247)
	at com.zimbra.cs.service.mail.CheckSpelling.handle(CheckSpelling.java:103)
	at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:418)
	at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:272)
	at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:156)
	at com.zimbra.soap.SoapServlet.doWork(SoapServlet.java:291)
	at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:212)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
	at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:181)
	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:1157)
	at org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:81)
	at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:132)
	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1148)
	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:379)
	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: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(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.handler.DebugHandler.handle(DebugHandler.java:77)
	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:525)
	at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:882)
	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:755)
	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:387)
	at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
	at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451)
    Then at 11:16AM started getting hundreds of thousand (300000) lines with errors like the following:

    Code:
    2009-12-01 11:16:26,189 WARN  [btpool0-20:http://10.1.190.70:80/service/soap/NoOpRequest] [ip=10.1.190.119;] SoapEngine - unable to construct SOAP context
com.zimbra.common.service.ServiceException: system failure: ZimbraLdapContext
ExceptionId:btpool0-20:http://10.1.190.70:80/service/soap/NoOpRequest:1259684186189:fe6fa1a395153071
Code:service.FAILURE
	at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:247)
	at com.zimbra.cs.account.ldap.ZimbraLdapContext.(ZimbraLdapContext.java:394)
	at com.zimbra.cs.account.ldap.ZimbraLdapContext.(ZimbraLdapContext.java:355)
	at com.zimbra.cs.account.ldap.LdapProvisioning.getAccountByQuery(LdapProvisioning.java:519)
	at com.zimbra.cs.account.ldap.LdapProvisioning.getAccountByNameInternal(LdapProvisioning.java:693)
	at com.zimbra.cs.account.ldap.LdapProvisioning.getAccountByName(LdapProvisioning.java:671)
	at com.zimbra.cs.account.ldap.LdapProvisioning.get(LdapProvisioning.java:579)
	at com.zimbra.cs.account.ldap.LdapProvisioning.get(LdapProvisioning.java:564)
	at com.zimbra.cs.account.Provisioning.get(Provisioning.java:666)
	at com.zimbra.soap.ZimbraSoapContext.(ZimbraSoapContext.java:218)
	at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:201)
	at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:156)
	at com.zimbra.soap.SoapServlet.doWork(SoapServlet.java:291)
	at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:212)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
	at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:181)
	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:1157)
	at org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:81)
	at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:132)
	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1148)
	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:379)
	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: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(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.handler.DebugHandler.handle(DebugHandler.java:77)
	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:525)
	at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:882)
	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:755)
	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:387)
	at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
	at org.mortbay.thread.BoundedThreadPool$PoolThread.run(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(LdapCtx.java:3213)
	at javax.naming.ldap.InitialLdapContext.extendedOperation(InitialLdapContext.java:164)
	at com.zimbra.cs.account.ldap.ZimbraLdapContext.(ZimbraLdapContext.java:384)
	... 40 more
Caused by: java.net.SocketException: Bad file descriptor
	at java.net.SocketOutputStream.socketWrite0(Native Method)
	at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
	at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
	at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
	at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
	at com.sun.jndi.ldap.Connection.writeRequest(Connection.java:393)
	at com.sun.jndi.ldap.LdapClient.extendedOp(LdapClient.java:1172)
	at com.sun.jndi.ldap.LdapCtx.extendedOperation(LdapCtx.java:3160)
	... 42 more
2009-12-01 11:19:23,345 WARN  [btpool0-22:http://127.0.0.1:80/service/soap/AuthRequest] [name=ggatto@bbsd.org;oip=10.1.201.201;ua=zclient/6.0.3_GA_1915.UBUNTU6;] account - updating zimbraLastLogonTimestamp
com.zimbra.common.service.ServiceException: system failure: ZimbraLdapContext
ExceptionId:btpool0-22:http://127.0.0.1:80/service/soap/AuthRequest:1259684363345:fe6fa1a395153071
Code:service.FAILURE
	at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:247)
	at com.zimbra.cs.account.ldap.ZimbraLdapContext.(ZimbraLdapContext.java:394)
	at com.zimbra.cs.account.ldap.ZimbraLdapContext.(ZimbraLdapContext.java:355)
	at com.zimbra.cs.account.ldap.LdapProvisioning.modifyAttrsInternal(LdapProvisioning.java:325)
	at com.zimbra.cs.account.ldap.LdapProvisioning.modifyAttrs(LdapProvisioning.java:304)
	at com.zimbra.cs.account.ldap.LdapProvisioning.modifyAttrs(LdapProvisioning.java:285)
	at com.zimbra.cs.account.Provisioning.modifyAttrs(Provisioning.java:302)
	at com.zimbra.cs.account.ldap.LdapProvisioning.updateLastLogon(LdapProvisioning.java:3334)
	at com.zimbra.cs.account.ldap.LdapProvisioning.authAccount(LdapProvisioning.java:3300)
	at com.zimbra.cs.account.ldap.LdapProvisioning.authAccount(LdapProvisioning.java:3253)
	at com.zimbra.cs.service.account.Auth.handle(Auth.java:118)
	at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:418)
	at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:272)
	at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:156)
	at com.zimbra.soap.SoapServlet.doWork(SoapServlet.java:291)
	at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:212)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
	at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:181)
	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:1157)
	at org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:81)
	at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:148)
	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1148)
	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:379)
	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: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(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.handler.DebugHandler.handle(DebugHandler.java:77)
	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:525)
	at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:882)
	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:755)
	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:387)
	at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
	at org.mortbay.thread.BoundedThreadPool$PoolThread.run(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(LdapCtx.java:3213)
	at javax.naming.ldap.InitialLdapContext.extendedOperation(InitialLdapContext.java:164)
	at com.zimbra.cs.account.ldap.ZimbraLdapContext.(ZimbraLdapContext.java:384)
	... 42 more
Caused by: java.net.SocketException: Bad file descriptor
	at java.net.SocketOutputStream.socketWrite0(Native Method)
	at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
	at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
	at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
	at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
	at com.sun.jndi.ldap.Connection.writeRequest(Connection.java:393)
	at com.sun.jndi.ldap.LdapClient.extendedOp(LdapClient.java:1172)
	at com.sun.jndi.ldap.LdapCtx.extendedOperation(LdapCtx.java:3160)
	... 44 more
2009-12-01 11:19:23,371 INFO  [btpool0-22:http://127.0.0.1:80/service/soap/AuthRequest] [oip=10.1.201.201;ua=zclient/6.0.3_GA_1915.UBUNTU6;] soap - AuthRequest
2009-12-01 11:19:23,429 INFO  [btpool0-22:https://127.0.0.1:7071/service/admin/soap/GetDomainInfoRequest] [ip=127.0.0.1;] soap - GetDomainInfoRequest
2009-12-01 11:19:23,458 INFO  [btpool0-22:http://127.0.0.1:80/service/soap/BatchRequest] [name=ggatto@bbsd.org;mid=85;oip=10.1.201.201;ua=zclient/6.0.3_GA_1915.UBUNTU6;] soap - BatchRequest
2009-12-01 11:19:23,458 INFO  [btpool0-22:http://127.0.0.1:80/service/soap/BatchRequest] [name=ggatto@bbsd.org;mid=85;oip=10.1.201.201;ua=zclient/6.0.3_GA_1915.UBUNTU6;] soap - (batch) GetInfoRequest
2009-12-01 11:19:23,476 ERROR [btpool0-22:http://127.0.0.1:80/service/soap/BatchRequest] [name=ggatto@bbsd.org;mid=85;oip=10.1.201.201;ua=zclient/6.0.3_GA_1915.UBUNTU6;] account - can't get identities
com.zimbra.common.service.ServiceException: system failure: ZimbraLdapContext
ExceptionId:btpool0-22:http://127.0.0.1:80/service/soap/BatchRequest:1259684363476:fe6fa1a395153071
Code:service.FAILURE
	at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:247)
	at com.zimbra.cs.account.ldap.ZimbraLdapContext.(ZimbraLdapContext.java:394)
	at com.zimbra.cs.account.ldap.ZimbraLdapContext.(ZimbraLdapContext.java:348)
	at com.zimbra.cs.account.ldap.LdapProvisioning.getIdentitiesByQuery(LdapProvisioning.java:4647)
	at com.zimbra.cs.account.ldap.LdapProvisioning.getAllIdentities(LdapProvisioning.java:4850)
	at com.zimbra.cs.service.account.GetInfo.doIdentities(GetInfo.java:230)
	at com.zimbra.cs.service.account.GetInfo.handle(GetInfo.java:151)
	at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:418)
	at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:262)
	at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:156)
	at com.zimbra.soap.SoapServlet.doWork(SoapServlet.java:291)
	at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:212)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
	at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:181)
	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:1157)
	at org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:81)
	at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:148)
	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1148)
	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:379)
	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: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(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.handler.DebugHandler.handle(DebugHandler.java:77)
	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:525)
	at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:882)
	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:755)
	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:387)
	at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
	at org.mortbay.thread.BoundedThreadPool$PoolThread.run(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(LdapCtx.java:3213)
	at javax.naming.ldap.InitialLdapContext.extendedOperation(InitialLdapContext.java:164)
	at com.zimbra.cs.account.ldap.ZimbraLdapContext.(ZimbraLdapContext.java:384)
	... 38 more
Caused by: java.net.SocketException: Bad file descriptor
	at java.net.SocketOutputStream.socketWrite0(Native Method)
	at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
	at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
	at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
	at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
	at com.sun.jndi.ldap.Connection.writeRequest(Connection.java:393)
	at com.sun.jndi.ldap.LdapClient.extendedOp(LdapClient.java:1172)
	at com.sun.jndi.ldap.LdapCtx.extendedOperation(LdapCtx.java:3160)
	... 40 more
    Then you see the lines stating I shut down and restarted zimbra, and everything is normal after that. I saw no errors leading up to the 11:16AM errors other then the spell check ones.

    Paul
    Reply With Quote Reply With Quote
  4. 12-01-2009, 12:11 PM #4
    king0770's Avatar
    king0770
    king0770 is offline Zimbra Employee
    Send a message via Yahoo to king0770
    Join Date
    Sep 2007
    Posts
    186
    Rep Power
    6

    Default

    Paul,

    You may want to add your address to the CC list on this bug,
    Bug 42870 – "Bad file descriptor" SocketException causes system failure every several hours

    The bug is regarding the bad file descriptor problem.
    Reply With Quote Reply With Quote
« Previous Thread | Next Thread »

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Successful upgrade from 5.0.19 to 6.0.3
    By syoung in forum Zimbra Success Stories
    Replies: 1
    Last Post: 07-08-2010, 07:14 AM
  2. Two Issues After Upgrade to 6.0.3
    By phether in forum Installation
    Replies: 17
    Last Post: 01-05-2010, 10:19 PM
  3. Post 5.06 upgrade, statistics and status issue
    By cjstone in forum Administrators
    Replies: 6
    Last Post: 07-03-2008, 09:44 AM
  4. 4.5.9 to 5.0.1 upgrade issue?
    By playnada in forum Installation
    Replies: 0
    Last Post: 01-16-2008, 04:35 AM
  5. OpenSUSE10.2 - ZCS 5RC2 to GA upgrade issue.
    By brucealeg in forum Installation
    Replies: 4
    Last Post: 01-02-2008, 10:06 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Forum Rules