Mailbox stopped, redo.log permissons problem

[Crexis]

Can you verify that it's being run, and that zimbra is shutting down on a reboot?

Ah, I would dearly love to do that haven't got a clue how to though. Would there be a log file I can check or is it a case of sitting in front of machine during shutdown/startup? Funny thing is, I just rebooted my server again (due to changes under global in the Admin console) and I thought to check the file permissions after doing a zmcontrol stop, before restarting the box. It had changed to root:root. I did a chown+chmod to fix it, rebooted the box did a zmcontrol start and it worked first time. I'm guessing that this means the zmcontrol script is creating/modifying this file as root user during a zmcontrol stop? Any pointers greatly appreciated.

[KevinH]

/opt/zimbra/log/zimbra.log

[Crexis]

/opt/zimbra/log/zimbra.log

mail:~ # ls -l /opt/zimbra/redolog/redo.log
-rw-rw----  1 root zimbra 1024 Mar 14 17:01 /opt/zimbra/redolog/redo.log
mail:~ # su - zimbra
zimbra@mail:~> zmcontrol stop
Host mail.yellodot.co.za
        Stopping antispam...Done
        Stopping antivirus...Done
        Stopping ldap...Done
        Stopping logger...Done
        Stopping mailbox...Done
        Stopping mta...FAILED
/opt/zimbra/cyrus-sasl-2.1.21.ZIMBRA/sbin/saslauthd: no process killed


        Stopping snmp...Done
        Stopping spell...Done
zimbra@mail:~> logout
mail:~ # ls -l /opt/zimbra/redolog/redo.log
-rw-r-----  1 root root 512 Mar 14 17:46 /opt/zimbra/redolog/redo.log
mail:~ #

Output to /opt/zimbra/log/zimbra.log from "zmcontrol stop"

2006-03-14 17:46:52,221 INFO  [Thread-261] [] StatsImageServlet - Servlet StatsImageServlet shutting down
2006-03-14 17:46:52,222 INFO  [Thread-261] [] soap - Servlet AdminServlet shutting down
2006-03-14 17:46:52,222 INFO  [Thread-261] [] TcpServer/7025 - LmtpServer initiating shutdown
2006-03-14 17:46:52,223 INFO  [LmtpServer] [] TcpServer/7025 - finished accept loop
2006-03-14 17:46:52,230 INFO  [Thread-261] [] TcpServer/7025 - LmtpServer shutting down idle thread pool
2006-03-14 17:46:52,231 INFO  [Thread-261] [] TcpServer/110 - Pop3Server initiating shutdown
2006-03-14 17:46:52,231 INFO  [Pop3Server] [] TcpServer/110 - finished accept loop
2006-03-14 17:46:52,231 INFO  [Thread-261] [] TcpServer/110 - Pop3Server shutting down idle thread pool
2006-03-14 17:46:52,231 INFO  [Thread-261] [] TcpServer/995 - Pop3Server initiating shutdown
2006-03-14 17:46:52,232 INFO  [Pop3Server] [] TcpServer/995 - finished accept loop
2006-03-14 17:46:52,232 INFO  [Thread-261] [] TcpServer/995 - Pop3Server shutting down idle thread pool
2006-03-14 17:46:52,232 INFO  [Thread-261] [] TcpServer/143 - ImapServer initiating shutdown
2006-03-14 17:46:52,232 INFO  [ImapServer] [] TcpServer/143 - finished accept loop
2006-03-14 17:46:52,232 INFO  [Thread-261] [] TcpServer/143 - ImapServer shutting down idle thread pool
2006-03-14 17:46:52,232 INFO  [Thread-261] [] TcpServer/993 - ImapSSLServer initiating shutdown
2006-03-14 17:46:52,232 INFO  [ImapSSLServer] [] TcpServer/993 - finished accept loop
2006-03-14 17:46:52,233 INFO  [Thread-261] [] TcpServer/993 - ImapSSLServer shutting down idle thread pool
2006-03-14 17:46:52,233 INFO  [Thread-261] [] SessionCache - shutdown: clearing SessionCache
2006-03-14 17:46:52,233 INFO  [IndexWritersSweeper] [] MailboxIndex - IndexWritersSweeper thread exiting
2006-03-14 17:46:52,233 INFO  [Thread-261] [] MailboxIndex - Flushing all open index writers
2006-03-14 17:46:52,235 INFO  [Thread-263] [] im - Executing IMEvent: com.zimbra.cs.im.IMNullEvent@73bc22
2006-03-14 17:46:52,352 INFO  [Thread-261] [] RedoLogManager - Logged: 8 items, 2.0ms/item
2006-03-14 17:46:52,353 INFO  [IncomingDirectorySweeper] [] FileBlobStore - IncomingDirectorySweeper thread exiting
2006-03-14 17:46:52,353 INFO  [Thread-261] [] extensions - Destroying extensions
2006-03-14 17:46:52,376 INFO  [Thread-261] [] extensions - Destroyed extension clamscanner: com.zimbra.clam.ClamScanner@com.zimbra.cs.extension.ZimbraExtensionClassLoader@68cd79
2006-03-14 17:46:52,377 INFO  [Thread-261] [] ContentServlet - Servlet ContentServlet shutting down
2006-03-14 17:46:52,377 INFO  [Thread-261] [] PublicICalServlet - Servlet PublicICalServlet shutting down
2006-03-14 17:46:52,379 INFO  [Thread-261] [] soap - Servlet SoapServlet shutting down
2006-03-14 17:46:52,379 INFO  [Thread-261] [] account - Servlet PreAuthServlet shutting down
2006-03-14 17:46:52,380 INFO  [Thread-261] [] mailbox - Servlet UserServlet shutting down
2006-03-14 17:46:52,380 INFO  [Thread-261] [] FileUploadServlet - Servlet FileUploadServlet shutting down

Can see the reference to redolog but don't see an error (not that I really know what I'm looking at/for). As you can see from the excerpt at the top the rights on the redo.log file change after the stop command.

[Crexis]

Hello, just wondering if you've thrown your hands up on this one or are deep in thought? Let me know if I can provide more info/logs from the box. Thanks.

[KevinH]

Are you always using the zimbra user to stop/start?

[Crexis]

Are you always using the zimbra user to stop/start?

That would be a definate yes. When I manually stop/start, I do it after an "su - zimbra"

[KevinH]

Hard to say what's going on then. Doesn't seem like anyone else is having this problem.

[Crexis]

Ok, I appreciate that it's not really worth your while to devote time to a problem that only one person is having. Especially when there's so much else going on

Please could you provide a little more help on this issue? I have an idea for a workaround but I'm not sure how viable it is.

Could I stick a chown & chmod command at the end of the zmcontrol stop script? I think it would need to run under some kind of sudo type thing as it would need root rights to execute. I have absolutely no clue as to what the syntax for that would be. Only other issue that occurs to me is that if I do an upgrade the zmcontrol script may be overwritten meaning I would have to re-insert those commands. Would you be able to help me with the syntax for those commands or at least confirm it's efficacy?

TIA

[KevinH]

Since we have no idea why your permissions keep changing it's hard to say if adding a chmod will even fix it. It's worth a shot so feel free to try it.

[phalen]

I am having this issue on a SLES9 server (OSS version). The box is at work so I will check the logs tomorrow to see if I can see anything in the logs.

phalen