OOO for a user doesn't work, with a lucene exception
OOO for a user doesn't work, with a lucene exception
- This article is a Work in Progress, and may be unfinished or missing sections.
Purpose
A user's out-of-office doesn't work, and the following exception comes up in the logs:
2014-12-03 05:52:35,446 WARN [LmtpServer-607] [name=user@example.com;mid=158;ip=192.1.1.1;] mailbox - Unable to send out-of-office reply com.zimbra.common.service.ServiceException: system failure: Unable to send message ExceptionId:LmtpServer-607:1417582342246:87f570d47f244b5c Code:service.FAILURE at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:258) at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(MailSender.java:690) at com.zimbra.cs.mailbox.Notification.outOfOfficeIfNecessary(Notification.java:338) at com.zimbra.cs.mailbox.Notification.outOfOfficeIfNecessary(Notification.java:154) at com.zimbra.cs.mailbox.Notification.afterDelivery(Notification.java:113) at com.zimbra.cs.lmtpserver.ZimbraLmtpBackend.deliverMessageToLocalMailboxes(ZimbraLmtpBackend.java:639) at com.zimbra.cs.lmtpserver.ZimbraLmtpBackend.deliver(ZimbraLmtpBackend.java:382) at com.zimbra.cs.lmtpserver.LmtpHandler.processMessageData(LmtpHandler.java:376) at com.zimbra.cs.lmtpserver.TcpLmtpHandler.continueDATA(TcpLmtpHandler.java:73) at com.zimbra.cs.lmtpserver.LmtpHandler.doDATA(LmtpHandler.java:365) at com.zimbra.cs.lmtpserver.LmtpHandler.processCommand(LmtpHandler.java:181) at com.zimbra.cs.lmtpserver.TcpLmtpHandler.processCommand(TcpLmtpHandler.java:66) at com.zimbra.cs.server.ProtocolHandler.processConnection(ProtocolHandler.java:188) at com.zimbra.cs.server.ProtocolHandler.run(ProtocolHandler.java:127) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Caused by: java.io.IOException: read past EOF at org.apache.lucene.store.BufferedIndexInput.refill(BufferedIndexInput.java:223) at org.apache.lucene.store.BufferedIndexInput.readByte(BufferedIndexInput.java:39) at org.apache.lucene.store.DataInput.readInt(DataInput.java:84) at org.apache.lucene.store.BufferedIndexInput.readInt(BufferedIndexInput.java:169) at org.apache.lucene.index.FieldsReader.detectCodeVersion(FieldsReader.java:91) at org.apache.lucene.index.SegmentInfos.read(SegmentInfos.java:303) at org.apache.lucene.index.DirectoryReader$1.doBody(DirectoryReader.java:79) at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:754) at org.apache.lucene.index.DirectoryReader.open(DirectoryReader.java:75) at org.apache.lucene.index.IndexReader.open(IndexReader.java:462) at org.apache.lucene.index.IndexReader.open(IndexReader.java:405) at com.zimbra.cs.index.LuceneIndex.openIndexReader(LuceneIndex.java:300) at com.zimbra.cs.index.LuceneIndex.openSearcher(LuceneIndex.java:401) at com.zimbra.cs.mailbox.MailboxIndex.existsInContacts(MailboxIndex.java:272) at com.zimbra.cs.mailbox.Mailbox.newContactAddrs(Mailbox.java:7069) at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(MailSender.java:534) ... 15 more
Resolution
This is an error with Lucene, reindexing fixes it:
zmprov rim user@example.com start
Reindexing can take time, and you can see the status by running:
zmprov rim user@example.com status
Additional Content
- You can check the next Wiki provided by our Engineers about Lucene Topics.