Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 30

Thread: mystery solved: unclean shutdown causes redo.log to be owned by root:root

  1. #11
    Join Date
    Mar 2006
    Location
    Czech Republic
    Posts
    81
    Rep Power
    9

    Default

    Just today I have noticed that the problem had occured again over the weekend. File permissions on opt/zimbra/amavisd/.spamassassin/bayes_toks were reset to root/root. I am logging messages' spam scores using my own add-on, so I know that last (not blocked) message that passed through bayes was 20.8. at 8:58:52am and first (not blocked) message that passed without bayes rating was at 9:04:54. So sometime in between permissions got corrupted. I can send you logs, if you tell me which ones.

  2. #12
    langthang Guest

    Default

    is there a bug number for this kernel bug at bugzilla.kernel.org ? I am using the latest stable vanilla kernel version and still see permission root:root for /opt/zimbra/redolog/redo.log after `zmcontrol stop`

  3. #13
    Join Date
    May 2006
    Posts
    16
    Rep Power
    9

    Default

    Same problem here on debian sarge, Kernel 2.6.16-2-686, Zimbra 4.0.1

  4. #14
    Join Date
    Sep 2005
    Posts
    20
    Rep Power
    10

    Default

    ditto here, debian sarge, 2.6.8-2-k7. I am also getting another error while trying to send mails:

    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 :439)
    at com.zimbra.cs.mailbox.Mailbox.endTransaction(Mailb ox.java:4338)
    at com.zimbra.cs.mailbox.Mailbox.addMessageInternal(M ailbox.java:3297)
    at com.zimbra.cs.mailbox.Mailbox.addMessage(Mailbox.j ava:3040)
    at com.zimbra.cs.mailbox.Mailbox.addMessage(Mailbox.j ava:3012)
    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/5/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...34b-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

  5. #15
    Join Date
    Sep 2005
    Posts
    20
    Rep Power
    10

    Default

    All pendig mails in the queue get's sent when I restart zimbra, after resetting the permissions of redo.log, but the above error occurs when I try to send mails from web interface.

    raj

  6. #16
    Join Date
    Sep 2005
    Posts
    20
    Rep Power
    10

    Default

    I can trace this also to a permission problem. The directory /opt/zimbra/index/0/5/index/0 is having 3 files with wrong permission.

    # ls -l /opt/zimbra/index/0/5/index/0
    total 82672
    -rw-r----- 1 zimbra zimbra 68037419 Sep 19 15:13 _1mh5.cfs
    -rw-r----- 1 zimbra zimbra 5656762 Sep 19 15:21 _1sz3.cfs
    -rw-r----- 1 zimbra zimbra 8616620 Sep 19 15:30 _1zh2.cfs
    -rw-r----- 1 zimbra zimbra 1820393 Sep 19 15:32 _21n2.cfs
    -rw-r----- 1 zimbra zimbra 245020 Sep 19 15:33 _21vp.cfs
    -rw-r----- 1 zimbra zimbra 64064 Sep 19 15:33 _21yl.cfs
    -rw-r----- 1 zimbra zimbra 32621 Sep 19 15:33 _21zj.cfs
    -rw-r----- 1 zimbra zimbra 27128 Sep 19 15:33 _220h.cfs
    -rw-r----- 1 zimbra zimbra 8257 Sep 19 15:43 _220p.cfs
    -rw-r----- 1 zimbra zimbra 1444 Sep 20 00:27 _220u.cfs
    -rw-r----- 1 root root 1424 Sep 20 00:29 _220z.cfs
    -rw-r----- 1 root root 4 Sep 20 00:29 deletable
    -rw-r----- 1 root root 130 Sep 20 00:29 segments
    Did a
    Code:
    chown -R zimbra:zimbra /opt/zimbra/index/0/5/index/0
    along with fixing the permission of redo.log after shutting down and then restarting seems to have fixed the problem, but another issue is which other files are having permission problem?

    raj
    Last edited by raj2569; 09-19-2006 at 10:16 PM.

  7. #17
    Join Date
    Jan 2006
    Posts
    83
    Rep Power
    9

    Default

    i just started to have this problem with debian kernel version:
    linux-source-2.6.16-18~bpo.1

  8. #18
    Join Date
    Jan 2006
    Posts
    83
    Rep Power
    9

    Default

    Quote Originally Posted by robbyt
    i just started to have this problem with debian kernel version:
    linux-source-2.6.16-18~bpo.1
    woot

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

  9. #19
    Join Date
    Sep 2006
    Posts
    13
    Rep Power
    9

    Default

    Quote Originally Posted by raj2569
    I can trace this also to a permission problem. The directory /opt/zimbra/index/0/5/index/0 is having 3 files with wrong permission.



    Did a
    Code:
    chown -R zimbra:zimbra /opt/zimbra/index/0/5/index/0
    along with fixing the permission of redo.log after shutting down and then restarting seems to have fixed the problem, but another issue is which other files are having permission problem?

    raj
    Yes, do we know what other directory trees are often having this problem, and that it's safe to do a chown -R to?

  10. #20
    Join Date
    Oct 2006
    Posts
    12
    Rep Power
    9

    Default

    I do a chown on the store folder as well.

    Thinking on adding this up to the zmcontrol script, so when the start process is started the permission are changed as the first thing.

    That would be a working quick-n-diiirty hack to solve the issue

Posting Permissions

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