In general, we encourage all of our users to maintain the latest build.
Also, keep in mind that we do not make all bugs public, for various reasons.
In order for myself, or any other member of the forums team to help you, we strongly encourage you to upgrade.
The two errors I asked about were:
Code:
2007-07-24 10:35:34,748 INFO [ImapServer-656] [] ProtocolHandler - Exception occurred while handling connection
java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:168)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read(BufferedInputStream.java:235)
at com.zimbra.cs.tcpserver.TcpServerInputStream.readLine(TcpServerInputStream.java:81)
at com.zimbra.cs.imap.ImapRequest.continuation(ImapRequest.java:156)
at com.zimbra.cs.imap.ImapHandler.processCommand(ImapHandler.java:226)
at com.zimbra.cs.tcpserver.ProtocolHandler.processConnection(ProtocolHandler.java:231)
at com.zimbra.cs.tcpserver.ProtocolHandler.run(ProtocolHandler.java:198)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Thread.java:595)
2007-07-24 10:35:34,749 INFO [ImapServer-656] [] imap - [144.135.112.170] exception while closing connection
java.net.SocketException: Broken pipe
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.zimbra.cs.imap.ImapHandler.sendLine(ImapHandler.java:2099)
at com.zimbra.cs.imap.ImapHandler.sendResponse(ImapHandler.java:2089)
at com.zimbra.cs.imap.ImapHandler.sendUntagged(ImapHandler.java:2078)
at com.zimbra.cs.imap.ImapHandler.dropConnection(ImapHandler.java:2048)
at com.zimbra.cs.imap.ImapHandler.dropConnection(ImapHandler.java:2034)
at com.zimbra.cs.tcpserver.ProtocolHandler.run(ProtocolHandler.java:210)
at EDU.oswego.cs.dl.util.concurrent.Pool
and
com.zimbra.cs.account.AccountServiceException: invalid attr name: [LDAP: error code 17 - password: attribute type undefined]
at com.zimbra.cs.account.AccountServiceException.INVALID_ATTR_NAME(AccountServiceException.java:115)
at com.zimbra.cs.account.ldap.LdapProvisioning.modifyAttrsInternal(LdapProvisioning.java:297)
at com.zimbra.cs.account.ldap.LdapProvisioning.modifyAttrs(LdapProvisioning.java:276)
at com.zimbra.cs.account.ldap.LdapProvisioning.modifyAttrs(LdapProvisioning.java:256)
at com.zimbra.cs.service.admin.ModifyAccount.handle(ModifyAccount.java:88)
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:270)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:168)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:90)
at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:223)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:162)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(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.invoke(StandardEngineValve.java:107)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:541)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:667)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)
Caused by: javax.naming.directory.InvalidAttributeIdentifierException: [LDAP: error code 17 - password: attribute type undefined]; remaining name 'uid=craig.bonsor,ou=people,dc=pakenhamses,dc=com,dc=au'
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3054)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2931)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2737)
at com.sun.jndi.ldap.LdapCtx.c_modifyAttributes(LdapCtx.java:1437)
at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_modifyAttributes(ComponentDirContext.java:255)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.modifyAttributes(PartialCompositeDirContext.java:172)
at javax.naming.directory.InitialDirContext.modifyAttributes(InitialDirContext.java:153)
at com.zimbra.cs.account.ldap.LdapUtil.modifyAttributes(LdapUtil.java:1053)
at com.zimbra.cs.account.ldap.LdapUtil.modifyAttrs(LdapUtil.java:595)
at com.zimbra.cs.account.ldap.LdapProvisioning.modifyAttrsInternal(LdapProvisioning.java:294)
... 25 more To wish I was asked to ask you to upgrade to see if that fixes your issue.
If you do not wish to upgrade, I understand, however, it's illogical to say:
It doesn't work, but I won't upgrade.
In an enterprise environment, I 100% understand not wanting to take your system down, but there is one particularly bad bug that can cause mail/accounts to be lost, see:
ZCS Critical Bug Alert
Ultimately, the choice to upgrade is your choice, and we will support you no matter what you choice. I just have to ask you to upgrade, as we don't know if that will fix your issue.
Sincerely,
john