Zimbra desktop error pwc6033 update#

z,-gzip test compressed blobs (NEW IN 5.0.10) u,-user check only the user/mbox-id (NEW IN 5.0.11) k,-skip-fs skip blob store reverse check (NEW IN 5.0.10)

WARNING: This tool will produce large I/O loads as it will stat every single file in the Zimbra blob-store and may decompress any compressed blobs. 13:01:14,901 ERROR offline - sync failure: system failure: .ServiceException.FAILURE(ServiceException.java:253)ДЄt .(SyncExceptionHandler.java:38)ДЄt .(InitialSync.java:882)ДЄt .(InitialSync.java:840)ДЄt .(InitialSync.java:423)ДЄt .(InitialSync.java:313)ДЄt .(InitialSync.java:377)ДЄt .(InitialSync.java:188)ДЄt .(InitialSync.java:174)ДЄt .(MailboxSync.java:192)ДЄt .(OfflineMailbox.java:115)ДЄt .(OfflineMailbox.java:96)ДЄt .mailbox.DesktopMailbox$1.run(DesktopMailbox.java:117)ДЄt (Timer.java:512)ДЄt (Timer.java:462)Д¬aused by: .ServiceException: system failure: Unable to read/write message .ServiceException.FAILURE(ServiceException.java:253)ДЄt .(InitialSync.java:1014)ДЄt .(InitialSync.java:879)Д¬aused by: java.io.EOFException: Unexpected end of ZLIB input streamДЄt .fill(InflaterInputStream.java:216)ДЄt .read(InflaterInputStream.java:134)ДЄt .read(GZIPInputStream.java:87)ДЄt .(TarBuffer.java:257)ДЄt .(TarBuffer.java:223)ДЄt .(TarInputStream.java:349)ДЄt .ByteUtil.readInput(ByteUtil.java:642)ДЄt .(InitialSync.java:1003)

In the future, we will have a fix script to migrate from incorrect to correct data.

Zimbra desktop error pwc6033 update#

Please see bugs 31519, 3177 Д¬urrently, the workaround is to update to the latest TarFormatter (Zimbra Desktop) as worked around in 31937.

The following problem is caused by an inconsistency in server metadata specifying the size of BLOB-data and the on-disk file-sizes. One is unable to desktop sync and a message similar to the following appears in the log. This article applies to the following ZCS versions.