here we go again.

the good thing this time is that the following issues are not very critical as we managed to fix them so far. but we need to know why this is happening as it is the network edition that will become our main server in the near future.

what happened this is this:

Code:
msg - system failure: indexDocument caught Exception
com.zimbra.common.service.ServiceException: system failure: indexDocument caught Exception
   at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:175)
   at com.zimbra.cs.index.MailboxIndex.indexDocument(MailboxIndex.java:2027)
   at com.zimbra.cs.mailbox.Document.reindex(Document.java:140)
   at com.zimbra.cs.mailbox.Mailbox.endTransaction(Mailbox.java:4912)
   at com.zimbra.cs.mailbox.Mailbox.createDocument(Mailbox.java:4713)
   at com.zimbra.cs.wiki.WikiPage$LocalWikiPage.create(WikiPage.java:152)
   at com.zimbra.cs.wiki.Wiki.addPage(Wiki.java:615)
   at com.zimbra.cs.service.wiki.SaveWiki.handle(SaveWiki.java:75)
   at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:262)
   at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:162)
   at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:84)
   at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:223)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
   at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:162)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
   at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
   at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
   at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
   at org.apache.catalina.core.StandardContextValve.invoke(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.invoke(StandardEngineValve.java:107)
   at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:541)
   at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
   at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
   at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:667)
   at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
   at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
   at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.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(MailboxIndex.java:996)
   at com.zimbra.cs.index.MailboxIndex.addDocument(MailboxIndex.java:357)
   at com.zimbra.cs.index.MailboxIndex.addDocument(MailboxIndex.java:340)
   at com.zimbra.cs.index.MailboxIndex.indexDocument(MailboxIndex.java:2025)
   ... 28 more
Caused by: java.io.IOException: Lock obtain timed out: Lock@/opt/zimbra/apache-tomcat-5.5.15/temp/lucene-9d1173b73d6c87e27c154f7d477042ef-write.lock
   at org.apache.lucene.store.Lock.obtain(Lock.java:58)
   at org.apache.lucene.index.IndexWriter.<init>(IndexWriter.java:223)
   at org.apache.lucene.index.IndexWriter.<init>(IndexWriter.java:173)
   at com.zimbra.cs.index.MailboxIndex.openIndexWriter(MailboxIndex.java:977)
   ... 31 more
the problem was in user rights for the above mentioned directory for the file segments. it's a simillar thing to what i had twice before on a different level... we were restarting zimbra and after the restart tomcat didn't start. the problem was the same as above. user rights on redo.log assigned to root:root... looks like somehow this user right change - mainly on restarting. is this a system thing or an zimbra issue? we are using SUSE9 and this is 4.5.1_GA_660.SuSEES9_20070201180902 SuSEES9 NETWORK edition.

should i post any other logs? which ones?

we will also install zimbra 4.5.2 tomorrow - will do this any good in order to resolve this issues?