Results 1 to 10 of 20

Thread: CentOS 4.4 imapsync problems

Hybrid View

  1. #1
    Join Date
    Nov 2006
    Posts
    11
    Rep Power
    9

    Default CentOS 4.4 imapsync problems

    Hey folks... this one's got me stumped. I'm prototyping a Zimbra Network Edition install on a 30 day trial of RHEL 4 and CentOS 4.4, both under VMware. Each installation is completely independent - just multiple installs to feel out the differences. I've done a minimal install, installed compat-libstdc++-33 and compat-libstdc++-296, as well as libidn, curl, and fetchmail (as required by the Zimbra install. I've also cranked up maximum attachment size in the MTA tab of the Global Settings window to 100000k. Nothing else funny.

    While attempting to import an account using imapsync, I get interesting errors (in /opt/zimbra/log/zimbra.log) on quite a few messages (as far as I can tell, only ones with attachments) and imapsync says something like:

    Couldn't append msg #23 (Subject:[Fw: 11076 die set]) to folder Gill T&-D: Error trying to append: 859 NO APPEND failed
    Here's a zimbra.log section:
    Code:
    2006-12-28 10:39:57,772 WARN  [ImapSSLServer-1] [ip=192.168.1.3;name=stevev@mail2.mtd-inc.com;] TransformationClient - Error sending document; tell convertd never mind
    java.net.SocketException: Connection reset
            at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:96)
            at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
            at java.io.DataOutputStream.write(DataOutputStream.java:90)
            at com.zimbra.cs.convert.TransformationClient.copyChunks(TransformationClient.java:122)
            at com.zimbra.cs.convert.TransformationClient.extract(TransformationClient.java:156)
            at com.zimbra.cs.convert.SocketTransformationStub.doExtract(SocketTransformationStub.java:68)
            at com.zimbra.cs.convert.SocketTransformationStub.extract(SocketTransformationStub.java:106)
            at com.zimbra.cs.mime.handler.DefaultHandler.getContentImpl(DefaultHandler.java:85)
            at com.zimbra.cs.mime.MimeHandler.getContent(MimeHandler.java:257)
            at com.zimbra.cs.mime.ParsedMessage.analyzePart(ParsedMessage.java:589)
            at com.zimbra.cs.mime.ParsedMessage.analyzeMessage(ParsedMessage.java:508)
            at com.zimbra.cs.mime.ParsedMessage.analyze(ParsedMessage.java:252)
            at com.zimbra.cs.mailbox.Mailbox.addMessage(Mailbox.java:3054)
            at com.zimbra.cs.mailbox.Mailbox.addMessage(Mailbox.java:3040)
            at com.zimbra.cs.imap.ImapAppendOperation.callback(ImapAppendOperation.java:126)
            at com.zimbra.cs.operation.Operation.schedule(Operation.java:190)
            at com.zimbra.cs.imap.ImapHandler.doAPPEND(ImapHandler.java:1163)
            at com.zimbra.cs.imap.ImapHandler.executeRequest(ImapHandler.java:342)
            at com.zimbra.cs.imap.ImapHandler.processCommand(ImapHandler.java:227)
            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)
    2006-12-28 10:39:57,799 WARN  [ImapSSLServer-1] [ip=192.168.1.3;name=stevev@mail2.mtd-inc.com;] TransformationClient - Socket error for client at port 47350: java.net.SocketException: Broken pipe
    2006-12-28 10:39:58,826 WARN  [ImapSSLServer-1] [ip=192.168.1.3;name=stevev@mail2.mtd-inc.com;] ParsedMessage - Parse error on MIME part 3 (image/jpeg, Message-ID: <000901c62284$593aa1c0$f101a8c0@mtd2ub5020gwg>)
    com.zimbra.cs.mime.MimeHandlerException: cannot extract text
            at com.zimbra.cs.mime.handler.DefaultHandler.getContentImpl(DefaultHandler.java:92)
            at com.zimbra.cs.mime.MimeHandler.getContent(MimeHandler.java:257)
            at com.zimbra.cs.mime.ParsedMessage.analyzePart(ParsedMessage.java:589)
            at com.zimbra.cs.mime.ParsedMessage.analyzeMessage(ParsedMessage.java:508)
            at com.zimbra.cs.mime.ParsedMessage.analyze(ParsedMessage.java:252)
            at com.zimbra.cs.mailbox.Mailbox.addMessage(Mailbox.java:3054)
            at com.zimbra.cs.mailbox.Mailbox.addMessage(Mailbox.java:3040)
            at com.zimbra.cs.imap.ImapAppendOperation.callback(ImapAppendOperation.java:126)
            at com.zimbra.cs.operation.Operation.schedule(Operation.java:190)
            at com.zimbra.cs.imap.ImapHandler.doAPPEND(ImapHandler.java:1163)
            at com.zimbra.cs.imap.ImapHandler.executeRequest(ImapHandler.java:342)
            at com.zimbra.cs.imap.ImapHandler.processCommand(ImapHandler.java:227)
            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)
    Caused by: com.zimbra.cs.convert.ConversionException: Cannot connect to convertd
            at com.zimbra.cs.convert.SocketTransformationStub.doExtract(SocketTransformationStub.java:71)
            at com.zimbra.cs.convert.SocketTransformationStub.extract(SocketTransformationStub.java:106)
            at com.zimbra.cs.mime.handler.DefaultHandler.getContentImpl(DefaultHandler.java:85)
            ... 15 more
    Caused by: 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:115)
            at java.io.DataOutputStream.writeInt(DataOutputStream.java:180)
            at com.zimbra.cs.convert.TransformationClient.copyChunks(TransformationClient.java:127)
            at com.zimbra.cs.convert.TransformationClient.extract(TransformationClient.java:156)
            at com.zimbra.cs.convert.SocketTransformationStub.doExtract(SocketTransformationStub.java:68)
            ... 17 more
    2006-12-28 10:39:58,854 WARN  [ImapSSLServer-1] [ip=192.168.1.3;name=stevev@mail2.mtd-inc.com;] ParsedMessage - Message had parse errors in 1 parts (Message-Id: <000901c62284$593aa1c0$f101a8c0@mtd2ub5020gwg>, Subject: 540BWC2.jpg;540BWC1.jpg)
    2006-12-28 10:39:58,855 WARN  [ImapSSLServer-1] [ip=192.168.1.3;name=stevev@mail2.mtd-inc.com;] imap - APPEND failed
    com.zimbra.cs.service.ServiceException: system failure: failed to analyze part
            at com.zimbra.cs.service.ServiceException.FAILURE(ServiceException.java:174)
            at com.zimbra.cs.mime.ParsedMessage.analyzeMessage(ParsedMessage.java:517)
            at com.zimbra.cs.mime.ParsedMessage.analyze(ParsedMessage.java:252)
            at com.zimbra.cs.mailbox.Mailbox.addMessage(Mailbox.java:3054)
            at com.zimbra.cs.mailbox.Mailbox.addMessage(Mailbox.java:3040)
            at com.zimbra.cs.imap.ImapAppendOperation.callback(ImapAppendOperation.java:126)
            at com.zimbra.cs.operation.Operation.schedule(Operation.java:190)
            at com.zimbra.cs.imap.ImapHandler.doAPPEND(ImapHandler.java:1163)
            at com.zimbra.cs.imap.ImapHandler.executeRequest(ImapHandler.java:342)
            at com.zimbra.cs.imap.ImapHandler.processCommand(ImapHandler.java:227)
            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)
    Caused by: com.zimbra.cs.convert.ConversionException: Cannot connect to convertd
            at com.zimbra.cs.convert.SocketTransformationStub.doExtract(SocketTransformationStub.java:71)
            at com.zimbra.cs.convert.SocketTransformationStub.extract(SocketTransformationStub.java:106)
            at com.zimbra.cs.mime.handler.DefaultHandler.getContentImpl(DefaultHandler.java:85)
            at com.zimbra.cs.mime.MimeHandler.getContent(MimeHandler.java:257)
            at com.zimbra.cs.mime.ParsedMessage.analyzePart(ParsedMessage.java:589)
            at com.zimbra.cs.mime.ParsedMessage.analyzeMessage(ParsedMessage.java:508)
            ... 12 more
    Caused by: 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:115)
            at java.io.DataOutputStream.writeInt(DataOutputStream.java:180)
            at com.zimbra.cs.convert.TransformationClient.copyChunks(TransformationClient.java:127)
            at com.zimbra.cs.convert.TransformationClient.extract(TransformationClient.java:156)
            at com.zimbra.cs.convert.SocketTransformationStub.doExtract(SocketTransformationStub.java:68)
            ... 17 more

  2. #2
    Join Date
    Nov 2006
    Posts
    11
    Rep Power
    9

    Default Addendum

    I should mention explicitly that I see the behavior on both RHEL and CentOS. On VMs with 768Mb - 1.5Gb of ram. I've also removed all mentions of UTF-8 from /etc/sysconfig/i18n on CentOS to work around an installation problem, so it looks like this:

    LANG="en_US"
    SUPPORTED="en_US:en"
    SYSFONT="latarcyrheb-sun16"

  3. #3
    Join Date
    Aug 2005
    Posts
    1,433
    Rep Power
    12

    Default verity bug + our bug

    We use Verity to extract text from attachments for building our full-text index. When Verity bombs on an attachment, we're doing the wrong thing and rejecting the IMAP APPEND (this is bug 13250 -- please vote for it!).

    The easiest way around this would probably be for you to disable attachment indexing during the imapsync, then reenable it for normal operation. After the import, just use the admin console or command-line tools to reindex the imported mailboxes.
    Last edited by dkarp; 12-28-2006 at 02:24 PM. Reason: Forgot to suggest a subsequent reindex...
    Bugzilla - Wiki - Downloads - Before posting... Search!

  4. #4
    Join Date
    Nov 2006
    Posts
    11
    Rep Power
    9

    Default Works!

    Awesome. Works well. Thanks!

  5. #5
    Join Date
    Nov 2006
    Posts
    11
    Rep Power
    9

    Default one last question...

    Everything's working great... just wondering if receiving new mail in the account normally (not through imapsync) will trigger the bad behavior?

  6. #6
    Join Date
    Aug 2005
    Posts
    1,433
    Rep Power
    12

    Default Nope!

    The problem is a Thunderbird bug that occurs only when copying messages into Zimbra via Thunderbird. Regular message receipt will mark mail with the time it's received.
    Bugzilla - Wiki - Downloads - Before posting... Search!

Similar Threads

  1. 4.0 RC1 imapsync with admin???
    By kirme3 in forum Administrators
    Replies: 37
    Last Post: 07-19-2007, 10:52 AM
  2. problems with imapsync from cyus
    By g8se in forum Migration
    Replies: 3
    Last Post: 02-22-2007, 07:52 PM
  3. CentOS 4.4 64 bit - 4.5.0_GA install problems
    By davespigot in forum Installation
    Replies: 1
    Last Post: 01-25-2007, 08:25 PM
  4. Centos 4.4 and Zimbra 4.0.5 takes FOREVER to install
    By eaperezh in forum Installation
    Replies: 3
    Last Post: 01-17-2007, 01:23 AM
  5. Zimbra startup hangs after install CentOS 4.2
    By eger in forum Installation
    Replies: 4
    Last Post: 02-10-2006, 11:08 PM

Posting Permissions

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