Page 1 of 3 123 LastLast
Results 1 to 10 of 30

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

  1. #1
    anand is offline Zimbra Employee
    Join Date
    Sep 2005
    Posts
    274
    Rep Power
    9

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

    Today we finally tracked down why on unclean shutdown of the tomcat JVM (mailbox server process) would cause redo.log and even some other files to be owned by root:root.

    Turns out there is a bug in linux kernel circa 2.6.5 (can't find a specific bug report on it) which would cause threads created before a setuid() call to have wrong privileges. (See zimbra bug 8158 for details.)

    This was showing up on our SuSE Linux Enterprise Server v9 build box. We just upgraded the SLES box and problem is fixed in the latest kernel on SLES9.

    I know this has come up and forums a few times, specially with Debian. So be sure to check your kernel version - because to be security hygienic you really don't want those threads running root privileged.
    Bugzilla - Wiki - Downloads - Before posting... Search!

  2. #2
    Crexis's Avatar
    Crexis is offline Senior Member
    Join Date
    Feb 2006
    Posts
    54
    Rep Power
    9

    Default Vindicated!

    Ha-HA! and you guys thought I was just some kind of looney (with reference to my bugzilla report). Nice one, good to know you guys have got a bit of terrier in you (won't let go until it's dead)
    Last edited by Crexis; 06-19-2006 at 11:22 PM.

  3. #3
    jholder's Avatar
    jholder is offline Former Zimbran
    Join Date
    Oct 2005
    Location
    Thatcher, AZ
    Posts
    5,606
    Rep Power
    20

    Default

    Loony Toon j/k
    Good job

  4. #4
    PNE
    PNE is offline Loyal Member
    Join Date
    Mar 2006
    Location
    Czech Republic
    Posts
    81
    Rep Power
    9

    Default

    I do not know if this is the right place for comments, but please read this. I have noticed several times that files in opt/zimbra/amavisd/.spamassassin/ directory have incorrect permissions, in fact the same you mentioned (owned by root/root, read only). This happens quite randomly, let's say once a month. I do not think it is related with Zimbra shutdown or restart, it just happens while Zimbra is running. As an effect, bayes stops working, while other spamassassin tests work, just as DSPAM does. After I manually set permissions back to zimbra/zimbra, bayes will start working, no need to restart Zimbra. I am using Centos 4.3 with 2.6.9-34.0.1 kernel, which is much newer version than you suspect to cause the bug. Today I got notification from Centos and upgrading to 2.6.9-34.0.2. Later I will see, it this helped, but as I wrote above, problem appears to be very random.

    Does anyone here have the same problem? And is it related to the bug mentionded in this thread?

  5. #5
    claros's Avatar
    claros is offline Project Contributor
    Join Date
    Mar 2006
    Location
    L'Aquila, ITALIA
    Posts
    59
    Rep Power
    9

    Default Shutdown ?

    Quote Originally Posted by PNE
    I do not know if this is the right place for comments, but please read this. I have noticed several times that files in opt/zimbra/amavisd/.spamassassin/ directory have incorrect permissions, in fact the same you mentioned (owned by root/root, read only). This happens quite randomly, let's say once a month. I do not think it is related with Zimbra shutdown or restart, it just happens while Zimbra is running. As an effect, bayes stops working, while other spamassassin tests work, just as DSPAM does. After I manually set permissions back to zimbra/zimbra, bayes will start working, no need to restart Zimbra. I am using Centos 4.3 with 2.6.9-34.0.1 kernel, which is much newer version than you suspect to cause the bug. Today I got notification from Centos and upgrading to 2.6.9-34.0.2. Later I will see, it this helped, but as I wrote above, problem appears to be very random.

    Does anyone here have the same problem? And is it related to the bug mentionded in this thread?
    Ciao,
    I'm testing zimbra since a week, but will try to contribute...
    With the startup script included in /opt/zimbra/libexec/zimbra service will never shutdown in a clean way under RHEL and Centos.
    In this way you could loose your file permission and have a strange modification in zimbra config files.
    Seem to have solved creating a semaphore file under /var/lock/subsys. Testing with kernel 2.6.9-34.0.2smp
    My startup/shutdown script is attached, just the modified part without comments and license

    Greetings
    Claudio
    Attached Files Attached Files

  6. #6
    PNE
    PNE is offline Loyal Member
    Join Date
    Mar 2006
    Location
    Czech Republic
    Posts
    81
    Rep Power
    9

    Default

    Claros thanks for your help. And for Zimbra staff - can you please check Claros' solution and confirm the problem itself and this one solution?

    It seems to me that you consider this "mysterious problem" solved (no one posted anything after my post since almost one month ago), but for sure it is not! Just today my Zimbra instal got stuck just because permissions on amavisd/.spamassassin/ got corrupted again (see my last post for more). The result was long timeouts for content checking and subsequently overall server performance drop/overload/jam. Messages not passing through, users complaining etc... Really bad monday morning.

  7. #7
    KevinH's Avatar
    KevinH is offline Expert Member
    Join Date
    Aug 2005
    Location
    San Mateo, CA
    Posts
    4,789
    Rep Power
    18

    Default

    PNE, claros - What Distro and version are you running and what is the exact Kernel version?

    To date we've only seen this on SuSE and Debian. SuSE kernel upgrade fixes it. Debain doesn't have a patch available yet.
    Looking for new beta users -> Co-Founder of Acompli. Previously worked at Zimbra (and Yahoo! & VMware) since 2005.

  8. #8
    PNE
    PNE is offline Loyal Member
    Join Date
    Mar 2006
    Location
    Czech Republic
    Posts
    81
    Rep Power
    9

    Default

    Running 3.1.4 GA on fully patched Centos 4.3, kernel 2.6.9-34.0.2, as I wrote in one of posts above.

  9. #9
    KevinH's Avatar
    KevinH is offline Expert Member
    Join Date
    Aug 2005
    Location
    San Mateo, CA
    Posts
    4,789
    Rep Power
    18

    Default

    Quote Originally Posted by PNE
    Running 3.1.4 GA on fully patched Centos 4.3, kernel 2.6.9-34.0.2, as I wrote in one of posts above.
    Can you reproduce this everytime? I assume you installed the RedHat EL4 build on CentOS right?
    Looking for new beta users -> Co-Founder of Acompli. Previously worked at Zimbra (and Yahoo! & VMware) since 2005.

  10. #10
    PNE
    PNE is offline Loyal Member
    Join Date
    Mar 2006
    Location
    Czech Republic
    Posts
    81
    Rep Power
    9

    Default

    I don't know if the naming is right, but I've downloaded and installed CentOS 4.2 Server CD, just necessary services + GUI (X-Window + Gnome), then updated using yum to 4.3. CentOS Server distribution is described at centos.org. I think many users here use the same OS.

    No, I cannot reproduce this behaviour. I don't know next time the problem will occur. It happens occasionally let's say once or twice a month, it has happenned overnight or in daytime, without restarting Zimbra or OS.

Page 1 of 3 123 LastLast

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

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