Results 1 to 4 of 4

Thread: one of our mailbox don't accept any new mail

  1. #1
    Join Date
    Nov 2005
    Location
    Hungary
    Posts
    38
    Rep Power
    10

    Default one of our mailbox don't accept any new mail

    hi,
    one of our mailbox can't accept new mails. old mails are ok. this's a fully updated centos 4 system i386 with zimbra 4.0.5_GA_518.RHEL4-20061218051343. the log is the following. i read other threads and this is not a debian system and i already run zmfixperms. what can i do is there any solutions?
    thanks.
    2007-02-14 22:49:39,701 INFO [LmtpServer-4] [] LmtpHandler - [192.168.1.3] 451 4.0.0 Temporary message delivery failure try again (DATA)
    2007-02-14 22:49:55,698 INFO [IndexWritersSweeper] [] MailboxIndex - open index writers sweep: before=3, closed=0, after=3 (0ms)
    2007-02-14 22:49:57,989 INFO [LmtpServer-4] [name=ihaszi@mkk.hu;] cache - Initializing folder and tag caches for mailbox 34
    2007-02-14 22:49:58,090 INFO [LmtpServer-4] [name=ihaszi@mkk.hu;] FileBlobStore - Stored size=1880 wrote=1880 path=/opt/zimbra/store/incoming/1171489202447-5.msg vol=1 digest=KHXJgoMY+9MHY4aW3,yM3
    HeFkwk=
    2007-02-14 22:49:58,091 INFO [LmtpServer-4] [name=ihaszi@mkk.hu;] FileBlobStore - Renamed id=1180 mbox=34 oldpath=/opt/zimbra/store/incoming/1171489202447-5.msg newpath=/opt/zimbra/store/0/34/msg/
    0/1180-11800.msg
    2007-02-14 22:49:58,447 INFO [LmtpServer-4] [name=ihaszi@mkk.hu;] FileBlobStore - deleting blob 1180 in mailbox 34
    2007-02-14 22:49:58,448 INFO [LmtpServer-4] [name=ihaszi@mkk.hu;] ZimbraLmtpBackend - try again for message ihaszi@mkk.hu: exception occurred
    com.zimbra.cs.service.ServiceException: system failure: indexMessage caught IOException
    at com.zimbra.cs.service.ServiceException.FAILURE(Ser viceException.java:174)
    at com.zimbra.cs.index.Indexer.indexMessage(Indexer.j ava:161)
    at com.zimbra.cs.mailbox.Message.reindex(Message.java :421)
    at com.zimbra.cs.mailbox.Mailbox.endTransaction(Mailb ox.java:4371)
    at com.zimbra.cs.mailbox.Mailbox.addMessageInternal(M ailbox.java:3318)
    at com.zimbra.cs.mailbox.Mailbox.addMessage(Mailbox.j ava:3062)
    at com.zimbra.cs.mailbox.Mailbox.addMessage(Mailbox.j ava:3046)
    at com.zimbra.cs.filter.ZimbraMailAdapter.addMessage( ZimbraMailAdapter.java:327)
    at com.zimbra.cs.filter.ZimbraMailAdapter.doDefaultFi ling(ZimbraMailAdapter.java:321)
    at com.zimbra.cs.filter.RuleManager.applyRules(RuleMa nager.java:182)
    at com.zimbra.cs.lmtpserver.ZimbraLmtpBackend.deliver MessageToLocalMailboxes(ZimbraLmtpBackend.java:308 )
    at com.zimbra.cs.lmtpserver.ZimbraLmtpBackend.deliver (ZimbraLmtpBackend.java:122)
    at com.zimbra.cs.lmtpserver.LmtpHandler.doDATA(LmtpHa ndler.java:420)
    at com.zimbra.cs.lmtpserver.LmtpHandler.processComman d(LmtpHandler.java:197)
    at com.zimbra.cs.tcpserver.ProtocolHandler.processCon nection(ProtocolHandler.java:231)
    at com.zimbra.cs.tcpserver.ProtocolHandler.run(Protoc olHandler.java:198)
    at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Wo rker.run(Unknown Source)
    at java.lang.Thread.run(Thread.java:595)
    Caused by: java.io.IOException: term out of order
    at org.apache.lucene.index.TermInfosWriter.add(TermIn fosWriter.java:93)
    at org.apache.lucene.index.SegmentMerger.mergeTermInf o(SegmentMerger.java:323)
    at org.apache.lucene.index.SegmentMerger.mergeTermInf os(SegmentMerger.java:290)
    at org.apache.lucene.index.SegmentMerger.mergeTerms(S egmentMerger.java:254)
    at org.apache.lucene.index.SegmentMerger.merge(Segmen tMerger.java:93)
    at org.apache.lucene.index.IndexWriter.mergeSegments( IndexWriter.java:487)
    at org.apache.lucene.index.IndexWriter.maybeMergeSegm ents(IndexWriter.java:458)
    at org.apache.lucene.index.IndexWriter.addDocument(In dexWriter.java:310)
    at org.apache.lucene.index.IndexWriter.addDocument(In dexWriter.java:294)
    at com.zimbra.cs.index.MailboxIndex.addDocument(Mailb oxIndex.java:367)
    at com.zimbra.cs.index.Indexer.addDocument(Indexer.ja va:354)
    at com.zimbra.cs.index.Indexer.addDocument(Indexer.ja va:324)
    at com.zimbra.cs.index.Indexer.indexMessage(Indexer.j ava:156)
    ... 16 more

  2. #2
    Join Date
    Sep 2005
    Posts
    93
    Rep Power
    10

    Default

    This is bug 12848

    Ugh, yah, we've seen this on a few very rare occasions. There's a Lucene bug about this exact issue, but the bug is very complicated and rare and it isn't clear if the issue/fix they have applies to us. We've had it happen to one account at one customer, but unfortunately we haven't been able to trace the issue.

    Can you tell me a little about your setup? In particular, tell me what your OS is, what your filesystem layout is (what's mounted where, what filesystems you're using) and anything else that might be "weird" about your setup -- for example, have you ever manually copied files into/outof the /opt/zimbra/index directory? Have you restored this account from backup (if so, what procedure did you use)? Are you using NFS? What version of Zimbra are you running?

    If you're feeling really helpful, it would probably be useful for me if you could tar up the /opt/zimbra/index/0/34/ directory (and subdirs obviously) and put it somewhere that I can download it (private message me) so I can do some forensics on the file.


    ...Once you've collected the data -- or, if you don't feel like collecting data, the correct fix is to shut down zimbra, mv the /opt/zimbra/index/0/34 directory to a backup location, restart Zimbra, and then use the admin console to Re-Index the mailbox.
    Bugzilla - Wiki - Downloads - Before posting... Search!

  3. #3
    Join Date
    Nov 2005
    Location
    Hungary
    Posts
    38
    Rep Power
    10

    Default

    Quote Originally Posted by tim brennan View Post
    This is bug 12848

    Ugh, yah, we've seen this on a few very rare occasions. There's a Lucene bug about this exact issue, but the bug is very complicated and rare and it isn't clear if the issue/fix they have applies to us. We've had it happen to one account at one customer, but unfortunately we haven't been able to trace the issue.

    Can you tell me a little about your setup? In particular, tell me what your OS is, what your filesystem layout is (what's mounted where, what filesystems you're using) and anything else that might be "weird" about your setup -- for example, have you ever manually copied files into/outof the /opt/zimbra/index directory? Have you restored this account from backup (if so, what procedure did you use)? Are you using NFS? What version of Zimbra are you running?
    - this is centos 4.4 i386 fully updated.
    - never copied, backup or anything like that (simple use it).
    - the /opt/zimbra is on a raid5 array (detaild bellow) and an ext3 fs over it.
    /dev/md2 /mnt/array ext3 defaults,acl,user_xattr,errors=remount-ro 1 1
    # mdadm --detail /dev/md2
    /dev/md2:
    Version : 00.90.01
    Creation Time : Thu Feb 1 16:35:00 2007
    Raid Level : raid5
    Array Size : 1194849792 (1139.50 GiB 1223.53 GB)
    Device Size : 199141632 (189.92 GiB 203.92 GB)
    Raid Devices : 7
    Total Devices : 8
    Preferred Minor : 2
    Persistence : Superblock is persistent

    Update Time : Thu Feb 15 11:47:38 2007
    State : clean
    Active Devices : 7
    Working Devices : 8
    Failed Devices : 0
    Spare Devices : 1

    Layout : left-symmetric
    Chunk Size : 128K

    UUID : a9f36a3d:5412873d:adb993e2:6a70633e
    Events : 0.555351

    Number Major Minor RaidDevice State
    0 8 1 0 active sync /dev/sda1
    1 8 17 1 active sync /dev/sdb1
    2 8 33 2 active sync /dev/sdc1
    3 8 49 3 active sync /dev/sdd1
    4 8 65 4 active sync /dev/sde1
    5 8 81 5 active sync /dev/sdf1
    6 8 97 6 active sync /dev/sdg1

    7 8 113 - spare /dev/sdh1

    Quote Originally Posted by tim brennan View Post
    If you're feeling really helpful, it would probably be useful for me if you could tar up the /opt/zimbra/index/0/34/ directory (and subdirs obviously) and put it somewhere that I can download it (private message me) so I can do some forensics on the file.


    ...Once you've collected the data -- or, if you don't feel like collecting data, the correct fix is to shut down zimbra, mv the /opt/zimbra/index/0/34 directory to a backup location, restart Zimbra, and then use the admin console to Re-Index the mailbox.
    i've send it to you.
    how can i manualy reindex?

  4. #4
    Join Date
    Mar 2006
    Location
    Beaucaire, France
    Posts
    2,322
    Rep Power
    13

    Default

    Quote Originally Posted by lfarkas View Post
    how can i manualy reindex?
    There's a button for it in the admin interface : select the user (go into his properties page) and the button is in the top buttons-line (on the right).

Similar Threads

  1. Problems with port 25
    By yogiman in forum Installation
    Replies: 57
    Last Post: 06-13-2011, 02:55 PM
  2. Replies: 7
    Last Post: 02-03-2011, 07:01 AM
  3. fresh install down may be due to tomcat
    By gon in forum Installation
    Replies: 10
    Last Post: 07-25-2007, 09:09 AM
  4. DynDNS and Zimbra
    By afterwego in forum Installation
    Replies: 30
    Last Post: 04-01-2007, 04:34 PM
  5. Mail not getting to mail boxes
    By ehults in forum Installation
    Replies: 5
    Last Post: 10-31-2005, 09:24 AM

Posting Permissions

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