zimbra 0.92 build 1433: append message errors

**kellner** · 01-10-2009, 03:17 AM

(System: Ubuntu Intrepid Ibex)

Zimbra keeps generating errors synching with an IMAP mailbox. I find these messages in the "Errors" folder:

Code:

Product name:    Zimbra Desktop
Product version: 0.92
Build ID:        1433
Release type:    BETA
OS Platform:     Linux i386 2.6.27-9-generic
Time of event:   2009-01-10 11:28:03
Error type:      APPEND failed: Invalid date-time in Append command
Error summary:   Append message failed

Failure details - PLEASE REMOVE ANY SENSITIVE INFORMATION
----------------------------------------------------------------------------

com.zimbra.cs.mailclient.CommandFailedException: APPEND failed: Invalid date-time in Append command
        at com.zimbra.cs.mailclient.imap.ImapRequest.checkStatus(ImapRequest.java:94)
        at com.zimbra.cs.mailclient.imap.ImapRequest.sendCheckStatus(ImapRequest.java:80)
        at com.zimbra.cs.mailclient.imap.ImapConnection.append(ImapConnection.java:225)
        at com.zimbra.cs.datasource.RemoteFolder.appendMessage(RemoteFolder.java:92)
        at com.zimbra.cs.datasource.ImapFolderSync.appendMessage(ImapFolderSync.java:545)
        at com.zimbra.cs.datasource.ImapFolderSync.appendMessages(ImapFolderSync.java:531)
        at com.zimbra.cs.datasource.ImapFolderSync.appendNewMessages(ImapFolderSync.java:506)
        at com.zimbra.cs.datasource.ImapFolderSync.finishSync(ImapFolderSync.java:379)
        at com.zimbra.cs.datasource.ImapSync.finishSync(ImapSync.java:240)
        at com.zimbra.cs.datasource.ImapSync.syncFolders(ImapSync.java:159)
        at com.zimbra.cs.datasource.ImapSync.importData(ImapSync.java:119)
        at com.zimbra.cs.datasource.DataSourceManager.importData(DataSourceManager.java:154)
        at com.zimbra.cs.mailbox.LocalMailbox.importData(LocalMailbox.java:367)
        at com.zimbra.cs.mailbox.LocalMailbox.syncAllLocalDataSources(LocalMailbox.java:340)
        at com.zimbra.cs.mailbox.LocalMailbox.sync(LocalMailbox.java:401)
        at com.zimbra.cs.service.offline.OfflineSync.handle(OfflineSync.java:48)
        at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:429)
        at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:286)
        at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:160)
        at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:269)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
        at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:190)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
        at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
        at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362)
        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:716)
        at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:406)
        at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:211)
        at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
        at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
        at org.mortbay.jetty.handler.RewriteHandler.handle(RewriteHandler.java:176)
        at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
        at org.mortbay.jetty.Server.handle(Server.java:313)
        at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:506)
        at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:844)
        at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:644)
        at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
        at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:381)
        at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:396)
        at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)

----------------------------------------------------------------------------

I have enabled a debug trace; in zdesktop.log, I find messages that suggest a timeout of the connection to the IMAP server:

Code:

com.zimbra.common.service.ServiceException: system failure: Synchronization of folder '/Inbox/researchstuff' failed
ExceptionId:btpool0-14:1231583604301:50a2084be375c852
Code:service.FAILURE
	at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:253)
	at com.zimbra.cs.datasource.ImapSync.syncFailed(ImapSync.java:261)
	at com.zimbra.cs.datasource.ImapSync.finishSync(ImapSync.java:243)
	at com.zimbra.cs.datasource.ImapSync.syncFolders(ImapSync.java:159)
	at com.zimbra.cs.datasource.ImapSync.importData(ImapSync.java:119)
	at com.zimbra.cs.datasource.DataSourceManager.importData(DataSourceManager.java:154)
	at com.zimbra.cs.mailbox.LocalMailbox.importData(LocalMailbox.java:367)
	at com.zimbra.cs.mailbox.LocalMailbox.syncAllLocalDataSources(LocalMailbox.java:340)
	at com.zimbra.cs.mailbox.LocalMailbox.sync(LocalMailbox.java:401)
	at com.zimbra.cs.service.offline.OfflineSync.handle(OfflineSync.java:48)
	at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:429)
	at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:286)
	at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:160)
	at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:269)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
	at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:190)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
	at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362)
	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:716)
	at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:406)
	at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:211)
	at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
	at org.mortbay.jetty.handler.RewriteHandler.handle(RewriteHandler.java:176)
	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
	at org.mortbay.jetty.Server.handle(Server.java:313)
	at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:506)
	at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:844)
	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:644)
	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:381)
	at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:396)
	at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)
Caused by: com.zimbra.common.service.ServiceException: system failure: Append message failed
ExceptionId:btpool0-14:1231583604299:50a2084be375c852
Code:service.FAILURE
	at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:253)
	at com.zimbra.cs.datasource.ImapFolderSync.checkCanContinue(ImapFolderSync.java:1134)
	at com.zimbra.cs.datasource.ImapFolderSync.syncFailed(ImapFolderSync.java:1105)
	at com.zimbra.cs.datasource.ImapFolderSync.appendMessages(ImapFolderSync.java:535)
	at com.zimbra.cs.datasource.ImapFolderSync.appendNewMessages(ImapFolderSync.java:506)
	at com.zimbra.cs.datasource.ImapFolderSync.finishSync(ImapFolderSync.java:379)
	at com.zimbra.cs.datasource.ImapSync.finishSync(ImapSync.java:240)
	... 33 more
Caused by: java.io.IOException: Error in response handler
	at com.zimbra.cs.mailclient.imap.ImapConnection.waitForResponse(ImapConnection.java:532)
	at com.zimbra.cs.mailclient.imap.ImapConnection.sendRequest(ImapConnection.java:460)
	at com.zimbra.cs.mailclient.imap.ImapRequest.send(ImapRequest.java:75)
	at com.zimbra.cs.mailclient.imap.ImapRequest.sendCheckStatus(ImapRequest.java:79)
	at com.zimbra.cs.mailclient.imap.ImapConnection.append(ImapConnection.java:225)
	at com.zimbra.cs.datasource.RemoteFolder.appendMessage(RemoteFolder.java:92)
	at com.zimbra.cs.datasource.ImapFolderSync.appendMessage(ImapFolderSync.java:545)
	at com.zimbra.cs.datasource.ImapFolderSync.appendMessages(ImapFolderSync.java:531)
	... 36 more
Caused by: java.net.SocketTimeoutException: Read timed out
	at java.net.SocketInputStream.socketRead0(Native Method)
	at java.net.SocketInputStream.read(Unknown Source)
	at com.sun.net.ssl.internal.ssl.InputRecord.readFully(Unknown Source)
	at com.sun.net.ssl.internal.ssl.InputRecord.read(Unknown Source)
	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Unknown Source)
	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readDataRecord(Unknown Source)
	at com.sun.net.ssl.internal.ssl.AppInputStream.read(Unknown Source)
	at com.sun.net.ssl.internal.ssl.AppInputStream.read(Unknown Source)
	at com.zimbra.cs.mailclient.util.TraceInputStream.read(TraceInputStream.java:73)
	at com.zimbra.cs.mailclient.MailInputStream.peek(MailInputStream.java:99)
	at com.zimbra.cs.mailclient.MailInputStream.peekChar(MailInputStream.java:127)
	at com.zimbra.cs.mailclient.imap.ImapInputStream.readText(ImapInputStream.java:225)
	at com.zimbra.cs.mailclient.imap.ImapResponse.readResponse(ImapResponse.java:48)
	at com.zimbra.cs.mailclient.imap.ImapResponse.read(ImapResponse.java:41)
	at com.zimbra.cs.mailclient.imap.ImapConnection.readResponse(ImapConnection.java:596)
	at com.zimbra.cs.mailclient.imap.ImapConnection.nextResponse(ImapConnection.java:590)
	at com.zimbra.cs.mailclient.imap.ImapConnection.access$000(ImapConnection.java:42)
	at com.zimbra.cs.mailclient.imap.ImapConnection$4.run(ImapConnection.java:557)
	at java.lang.Thread.run(Unknown Source)

I stumbled across a tip in another thread, which I applied: in conf/localconfig.xml, I added:

Code:

<key name="javamail_imap_timeout">
<value>300</value>
</key>

This, however, hasn't changed anything (restarted Zimbra to be sure it takes effect).

What's the damage done? What worries me is that due to these time errors, Zimbra seems to mark certain messages as having encountered them, and then skips these messages while syncing:

Code:

WARN  [btpool0-17] [mid=2;] datasource - Skipping append of item 9865 due to previous errors

This really worries me - what's the point in using Zimbra when I can apparently not be sure that it syncs properly?

**jjzhuang** · 01-13-2009, 10:37 PM

The second issue you posted has been addressed and will be in the next cut.

The first issue, regarding Invalid date-time in Append command, we don't have enough information. But in the next cut we will generate more information.

**kellner** · 01-13-2009, 11:07 PM

Thanks! I'm looking forward to the next cut.

**kamus** · 01-19-2009, 08:02 AM

Originally Posted by jjzhuang

The second issue you posted has been addressed and will be in the next cut.

The first issue, regarding Invalid date-time in Append command, we don't have enough information. But in the next cut we will generate more information.

I have same problem here we use OS Edition and ubuntu 8.04

Log file looks like as

Code:

Product name:    Zimbra Desktop
Product version: 0.92
Build ID:        1433
Release type:    BETA
OS Platform:     Linux i386 2.6.27-9-generic
Time of event:   2009-01-19 11:11:58
Error type:      APPEND failed: Invalid internal date.
Error summary:   Append message failed

Failure details - PLEASE REMOVE ANY SENSITIVE INFORMATION
----------------------------------------------------------------------------

com.zimbra.cs.mailclient.CommandFailedException: APPEND failed: Invalid internal date.
        at com.zimbra.cs.mailclient.imap.ImapRequest.checkStatus(ImapRequest.java:94)
        at com.zimbra.cs.mailclient.imap.ImapRequest.sendCheckStatus(ImapRequest.java:80)
        at com.zimbra.cs.mailclient.imap.ImapConnection.append(ImapConnection.java:225)
        at com.zimbra.cs.datasource.RemoteFolder.appendMessage(RemoteFolder.java:92)
        at com.zimbra.cs.datasource.ImapFolderSync.appendMessagesNoUidPlus(ImapFolderSync.java:580)
        at com.zimbra.cs.datasource.ImapFolderSync.appendNewMessages(ImapFolderSync.java:508)
        at com.zimbra.cs.datasource.ImapFolderSync.finishSync(ImapFolderSync.java:379)
        at com.zimbra.cs.datasource.ImapSync.finishSync(ImapSync.java:240)
        at com.zimbra.cs.datasource.ImapSync.syncFolders(ImapSync.java:159)
        at com.zimbra.cs.datasource.ImapSync.importData(ImapSync.java:119)
        at com.zimbra.cs.datasource.DataSourceManager.importData(DataSourceManager.java:154)
        at com.zimbra.cs.mailbox.LocalMailbox.importData(LocalMailbox.java:367)
        at com.zimbra.cs.mailbox.LocalMailbox.syncAllLocalDataSources(LocalMailbox.java:340)
        at com.zimbra.cs.mailbox.LocalMailbox.sync(LocalMailbox.java:401)
        at com.zimbra.cs.service.offline.OfflineSync.handle(OfflineSync.java:48)
        at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:429)
        at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:286)
        at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:160)
        at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:269)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
        at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:190)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
        at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
        at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362)
        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:716)
        at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:406)
        at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:211)
        at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
        at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
        at org.mortbay.jetty.handler.RewriteHandler.handle(RewriteHandler.java:176)
        at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
        at org.mortbay.jetty.Server.handle(Server.java:313)
        at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:506)
        at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:844)
        at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:644)
        at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
        at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:381)
        at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:396)
        at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)

----------------------------------------------------------------------------

**jjzhuang** · 01-20-2009, 03:34 PM

Please wait for the next cut. Thanks!

Zimbra

Thread: zimbra 0.92 build 1433: append message errors

LinkBack

Thread Tools

Search Thread

Display

zimbra 0.92 build 1433: append message errors

Thread Information

Users Browsing this Thread

Similar Threads

[SOLVED] Clamav problem ? What's happening ?

How to install Zimbra Debian 3.1 binaries on Debian Etch 4.0 [Workaround]

Zimbra shutdowns every n hours.

zmtlsctl give LDAP error

3.1 on FC4 problems

Posting Permissions