[SOLVED] Sync error but seems to work

[Kallisti]

Hi! Starting with RC1 I'm getting a red wing with an exclamation mark when trying to sync. The error message is:

Kommunikationsfel ”{0}”. Kontrollera portnumret.Debug message: Unbuffered entity enclosing request can not be repeated.
Exception:
com.zimbra.common.service.ServiceException: system failure: PushChanges.sync
ExceptionId:btpool0-18:1234022659077:be250f929380d89a
Code:service.FAILURE
    at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:253)
    at com.zimbra.cs.mailbox.SyncExceptionHandler.checkRecoverableException(SyncExceptionHandler.java:40)
    at com.zimbra.cs.mailbox.PushChanges.sync(PushChanges.java:373)
    at com.zimbra.cs.mailbox.PushChanges.sync(PushChanges.java:174)
    at com.zimbra.cs.mailbox.MailboxSync.sync(MailboxSync.java:185)
    at com.zimbra.cs.mailbox.OfflineMailbox.sync(OfflineMailbox.java:140)
    at com.zimbra.cs.service.offline.OfflineSync.handle(OfflineSync.java:47)
    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.cs.zclient.ZClientException: Unbuffered entity enclosing request can not be repeated.
ExceptionId:btpool0-18:1234022659077:be250f929380d89a
Code:zclient.IO_ERROR
    at com.zimbra.cs.zclient.ZClientException.IO_ERROR(ZClientException.java:47)
    at com.zimbra.cs.zclient.ZMailbox.uploadContentAsStream(ZMailbox.java:1784)
    at com.zimbra.cs.mailbox.PushChanges.uploadMessage(PushChanges.java:527)
    at com.zimbra.cs.mailbox.PushChanges.syncMessage(PushChanges.java:1172)
    at com.zimbra.cs.mailbox.PushChanges.sync(PushChanges.java:366)
    ... 30 more
Caused by: org.apache.commons.httpclient.ProtocolException: Unbuffered entity enclosing request can not be repeated.
    at org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequestBody(EntityEnclosingMethod.java:483)
    at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:1973)
    at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:993)
    at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:397)
    at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170)
    at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396)
    at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:324)
    at com.zimbra.cs.zclient.ZMailbox.uploadContentAsStream(ZMailbox.java:1774)
    ... 33 more
If issue persists please post description and debug information here.

I'm running ZD against a 5.0.11-server. It's seems like I'm getting all the messages but I have to keep pressing send/receive..

/K

[jjzhuang]

Hmm, that part of the code hasn't been touched for a while. Do you know how to get an http or tcp dump between your box and the server? It's unclear why a "retry" is needed. Usually that implies some kind of auth issue or redirect needs. Do you know if the ZCS server is behind some kind of proxy or load balancer? Thanks!

[Kallisti]

Hi,

I'm not sure about getting a tcp-dump between my laptop and the server. Would that help? I've upgraded to 5.0.13 but no change.

My server is running behind an nginx-proxy, not configured by Zimbra. It has been running like that for a long time without any problems. The problem occured when I installed ZD RC1.

Looking in the log I see an error connected to the nginx but I don't know why it occurs:

2009-02-11 20:25:52,482 ERROR [mid=2] [] offline - sync failure: xxx@xxx
com.zimbra.common.service.ServiceException: error while proxying request to target server unable to parse response: <html>
<head><title>502 Bad Gateway</title></head>
<body bgcolor="white">
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx/0.6.32</center>
</body>
</html>

ExceptionId:mid=2:1234380352481:be250f929380d89a
Code:service.PROXY_ERROR Arg:(url, STR, "https://xxx/service/soap/")
    at com.zimbra.common.service.ServiceException.PROXY_ERROR(ServiceException.java:303)

when I go to that url on the same laptop ("https://xxx/service/soap/") I get a jetty/zimbra-error (complaining about this url not supporting get) not an nginx-error. So why does ZD get an nginx error and my browser a jetty error?

I also see I get the sync error right after starting change push:

2009-02-11 20:55:48,303 DEBUG [btpool0-21] [mid=2;] offline - ending delta sync [token 1428106]
2009-02-11 20:55:50,541 DEBUG [btpool0-21] [mid=2;] offline - starting change push
2009-02-11 20:56:21,540 ERROR [btpool0-21] [mid=2;] offline - sync failure: xxx@xxx
com.zimbra.common.service.ServiceException: system failure: PushChanges.sync
ExceptionId:btpool0-21:1234382181540:be250f929380d89a
Code:service.FAILURE
    at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:253)

That seems to be why I have to press send/receive. The sync process works (I get new mail into the inbox and mail are sent from the outbox) but after a while the error occurs and ZD assumes i have a bad connection or something, which is ignored when I force a send/receive.

/K

[jjzhuang]

Your sync doesn't really work. It's downloading fine, but not pushing up changes. This appears to be a proxy related issue. Can you try directly pointing ZD to the ZCS server your account is on? See if that makes a difference.

[Kallisti]

What changes isn't being pushed? I've got a couple of mail sent from the outbox and, as I remember it, read/unread status etc where also updated on the server. I can't try it now at work as ZD can't be proxied even with third party software. When I get outside I'll try to connect directly to the server (even though I have made no changes to it or the dmz setup) and see if I get another result.

/K

[jjzhuang]

from what i can see it's failing on pushing a message content to server. this is most likely a Draft message.

[Kallisti]

I opened up the firewall for the internal port and tried to sync. Alas I got a nice green ring! Trying to go back to the proxied and firewalled setting did not give me the error again, so I'm marking it solved, although I have no idea what solved it..

Thanks for the help!
/K