Zimbra error when sending messages

[illscientific]

msg - system failure: indexMessage caught IOException
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:3034)
at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(M ailSender.java:183)
at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(M ailSender.java:119)
at com.zimbra.cs.operation.SendMsgOperation.callback( SendMsgOperation.java:73)
at com.zimbra.cs.operation.Operation.schedule(Operati on.java:190)
at com.zimbra.cs.service.mail.SendMsg.handle(SendMsg. java:109)
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:261)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:162)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:84)
at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:223)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:709)
at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:173)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:802)
at org.apache.catalina.core.ApplicationFilterChain.in ternalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.do Filter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invo ke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invo ke(StandardContextValve.java:178)
at org.apache.catalina.core.StandardHostValve.invoke( StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke (ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invok e(StandardEngineValve.java:107)
at org.apache.catalina.valves.AccessLogValve.invoke(A ccessLogValve.java:541)
at org.apache.catalina.connector.CoyoteAdapter.servic e(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(H ttp11Processor.java:869)
at org.apache.coyote.http11.Http11BaseProtocol$Http11 ConnectionHandler.processConnection(Http11BaseProt ocol.java:667)
at org.apache.tomcat.util.net.PoolTcpEndpoint.process Socket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThr ead.runIt(LeaderFollowerWorkerThread.java:80)
at org.apache.tomcat.util.threads.ThreadPool$ControlR unnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.io.IOException: Could not create index /opt/zimbra/index/0/4/index/0 (directory already exists)
at com.zimbra.cs.index.MailboxIndex.openIndexWriter(M ailboxIndex.java:906)
at com.zimbra.cs.index.MailboxIndex.addDocument(Mailb oxIndex.java:349)
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)
... 32 more
Caused by: java.io.IOException: Lock obtain timed out: Lock@/opt/zimbra/apache-tomcat-5.5.1...2ef-write.lock
at org.apache.lucene.store.Lock.obtain(Lock.java:58)
at org.apache.lucene.index.IndexWriter.<init>(IndexWr iter.java:223)
at org.apache.lucene.index.IndexWriter.<init>(IndexWr iter.java:173)
at com.zimbra.cs.index.MailboxIndex.openIndexWriter(M ailboxIndex.java:887)
... 36 more

code - service.FAILURE
method - ZmCsfeCommand.prototype.invoke
detail - soap:Receiver

Has anyone seen this or know a way to fix this.... This happens when I try and send a mail message from inside Zimbra. This is the latest opensource version and I saw this with the last version .02.... It would happen sometimes when trying to use the wiki and contacts... only one would work. I created contacts and used the wiki this time but now messages dont seem to be accepted and definitely not sent...

Any ideas?

[illscientific]

I submitted this as Bugzilla Bug 11466. The other posts about this in the forums talk about a permissions problem. I do not think this has anything to do with this issue.

[illscientific]

Ok. Maybe I was wrong If I chown -R zimbra:zimbra index/ and restart zimbra its all good. So this has to do with a kernel issue? I build custom kernels and I am running 2.6.17-8 from kernel.org... this is a debian system though.

[papaya74]

Interesting, i also did a kernel update in Debian and have the same problem. How is this related i don't understand this exactly.

Why a kernel problem ?
Are there kernels, which produce malfunctions in Zimbra ?

I use the standard Debian Kernel 2.6.8-2-686....


Regards,

/harry

[dkarp]

This is a Debian kernel bug. It's been known for quite a while, and there's a forum thread about this that says that it's been fixed in the Debian source:

woot

it's fixed in debian's linux-source-2.6.17-8~bpo.1

[m.a.g.]

Originally Posted by illscientific

code - service.FAILURE
method - ZmCsfeCommand.prototype.invoke
detail - soap:Receiver

When I want to send an email in Webmail, I get the very same error (I used to have it for a long time, but fixing the permission after shutting down fixed it).
Starting approximatly two days ago, fixing the permissions didn't help any more. I am starting Zimbra with the right permissions for redolog & index, but I still get the error.

What could that be? About two weeks ago I upgraded Zimbra to 4.5.3 (open source edtion). Everythings seems to work ok, exept SMTPS. Is there a connection?
I'm running Debian 3.1

Thanks for your hints.

[m.a.g.]

Doesn't anybody have a solution?

This error doesn't let me use Zimbra...

Thank you.

[dkarp]

Can you post the error message and stack trace from the mailbox.log logfile?

[m.a.g.]

The errormessage in Webmail is:

msg - system failure: MessagingException
code - service.FAILURE
method - ZmCsfeCommand.prototype.invoke
detail - soap:Receiver

The mailbox.log sayed that it was unable to connect to the SMTP Server; a firewall-rule was changed by errror.

After changing this rule back to its original value, it worked again.

Thank you very much for leading me into the right direction!