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

Discuss your pilot or production implementation with other Zimbra admins or our engineers.
PNE
Advanced member
Advanced member
Posts: 80
Joined: Fri Sep 12, 2014 10:06 pm

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

Postby PNE » Mon Aug 21, 2006 5:31 am

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.


Service
Elite member
Elite member
Posts: 1023
Joined: Tue Apr 14, 2009 2:44 pm

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

Postby Service » Sun Sep 10, 2006 6:20 pm

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`
MarcTwain
Posts: 16
Joined: Fri Sep 12, 2014 10:11 pm

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

Postby MarcTwain » Sun Sep 17, 2006 8:28 am

Same problem here on debian sarge, Kernel 2.6.16-2-686, Zimbra 4.0.1
raj2569
Posts: 20
Joined: Fri Sep 12, 2014 9:55 pm

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

Postby raj2569 » Tue Sep 19, 2006 10:40 pm

ditto here, debian sarge, 2.6.8-2-k7. I am also getting another error while trying to send mails:
[QUOTE]msg - system failure: indexMessage caught IOException

com.zimbra.cs.service.ServiceException: system failure: indexMessage caught IOException

at com.zimbra.cs.service.ServiceException.FAILURE(ServiceException.java:174)

at com.zimbra.cs.index.Indexer.indexMessage(Indexer.java:161)

at com.zimbra.cs.mailbox.Message.reindex(Message.java:439)

at com.zimbra.cs.mailbox.Mailbox.endTransaction(Mailbox.java:4338)

at com.zimbra.cs.mailbox.Mailbox.addMessageInternal(Mailbox.java:3297)

at com.zimbra.cs.mailbox.Mailbox.addMessage(Mailbox.java:3040)

at com.zimbra.cs.mailbox.Mailbox.addMessage(Mailbox.java:3012)

at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(MailSender.java:183)

at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(MailSender.java:119)

at com.zimbra.cs.operation.SendMsgOperation.callback(SendMsgOperation.java:73)

at com.zimbra.cs.operation.Operation.schedule(Operation.java:190)

at com.zimbra.cs.service.mail.SendMsg.handle(SendMsg.java:109)

at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:261)

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:173)

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/5/index/0 (directory already exists)

at com.zimbra.cs.index.MailboxIndex.openIndexWriter(MailboxIndex.java:906)

at com.zimbra.cs.index.MailboxIndex.addDocument(MailboxIndex.java:349)

at com.zimbra.cs.index.Indexer.addDocument(Indexer.java:354)

at com.zimbra.cs.index.Indexer.addDocument(Indexer.java:324)

at com.zimbra.cs.index.Indexer.indexMessage(Indexer.java:156)

... 32 more

Caused by: java.io.IOException: Lock obtain timed out: Lock@/opt/zimbra/apache-tomcat-5.5.15/temp/lucene-a21e7546ec34a467d2543e8b64fa734b-write.lock

at org.apache.lucene.store.Lock.obtain(Lock.java:58)

at org.apache.lucene.index.IndexWriter.(IndexWriter.java:223)

at org.apache.lucene.index.IndexWriter.(IndexWriter.java:173)

at com.zimbra.cs.index.MailboxIndex.openIndexWriter(MailboxIndex.java:887)

... 36 more
code - service.FAILURE

method - ZmCsfeCommand.prototype.invoke

detail - soap:Receiver[/QUOTE]
raj2569
Posts: 20
Joined: Fri Sep 12, 2014 9:55 pm

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

Postby raj2569 » Tue Sep 19, 2006 10:54 pm

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
raj2569
Posts: 20
Joined: Fri Sep 12, 2014 9:55 pm

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

Postby raj2569 » Tue Sep 19, 2006 11:14 pm

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.
[QUOTE]# 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

[/QUOTE]
Did a
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
robbyt
Advanced member
Advanced member
Posts: 81
Joined: Fri Sep 12, 2014 10:02 pm

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

Postby robbyt » Thu Sep 21, 2006 12:19 pm

i just started to have this problem with debian kernel version:

linux-source-2.6.16-18~bpo.1
robbyt
Advanced member
Advanced member
Posts: 81
Joined: Fri Sep 12, 2014 10:02 pm

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

Postby robbyt » Mon Sep 25, 2006 11:32 am

[quote user="robbyt"]i just started to have this problem with debian kernel version:

linux-source-2.6.16-18~bpo.1[/QUOTE]
woot
it's fixed in debian's linux-source-2.6.17-8~bpo.1
jammy
Posts: 13
Joined: Fri Sep 12, 2014 10:15 pm

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

Postby jammy » Wed Oct 18, 2006 7:19 am

[quote user="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
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[/QUOTE]
Yes, do we know what other directory trees are often having this problem, and that it's safe to do a chown -R to?
kolan
Posts: 11
Joined: Fri Sep 12, 2014 10:18 pm

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

Postby kolan » Wed Oct 18, 2006 9:39 am

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 :rolleyes:

Return to “Administrators”

Who is online

Users browsing this forum: Bing [Bot] and 17 guests