5.011 Bug - zmlogger fails to stop

[pcad]

Curious if anyone has tried the command switch I discovered listed in the Admin Guide:

zmcontrol shutdown

We are waiting for 5.0.12 so can't test this for you.

Hope that helps,
Mark

Tried this, and didn't work for me. I have all of the described symptoms posted earlier. I would rather wait for a Zimbra response to this bug. Is there anything more I can do through bugzilla to garner more attention from the powers that be? I noticed there was no place to vote on this, yet.

zmcontrol status
Host xxxxx.xxxxx.xxx
antispam Running
antivirus Running
ldap Running
logger Stopped
zmlogswatchctl is not running
mailbox Running
mta Running
snmp Running
spell Running
stats Running


ps ax |grep zmlogger
1256 ? S 0:33 /usr/bin/perl /opt/zimbra/libexec/zmlogger
2190 ? S 0:17 /usr/bin/perl /opt/zimbra/libexec/zmlogger
2608 pts/0 S+ 0:00 grep zmlogger
5851 ? S 0:09 /usr/bin/perl /opt/zimbra/libexec/zmlogger
6311 ? S 0:29 /usr/bin/perl /opt/zimbra/libexec/zmlogger
12888 ? S 0:30 /usr/bin/perl /opt/zimbra/libexec/zmlogger
27283 ? S 0:15 /usr/bin/perl /opt/zimbra/libexec/zmlogger
28739 ? S 0:38 /usr/bin/perl /opt/zimbra/libexec/zmlogger
30177 ? S 0:27 /usr/bin/perl /opt/zimbra/libexec/zmlogger
32605 ? S 0:20 /usr/bin/perl /opt/zimbra/libexec/zmlogger
32606 ? S 0:21 /usr/bin/perl /opt/zimbra/libexec/zmlogger

[mmorse]

Try the attached script.

zmcontrol stop
ps aux | grep zimbra
kill -9 pid# <of those leftover logger pid's
Replace /opt/zimbra/bin/zmlogswatchctl - permissions should be root.root 755
zmcontrol start
zmcontrol stop
ps aux | grep zimbra <shouldn't show any leftover

It's also available on both both bugs: Bug 33730 - zmlogger fails to terminate at zmcontrol stop > duped> Bug 33604 - Server Status Error
(Works on RHEL5 & Ubuntu8, might be something quirky about Ubuntu6.)

[chrisp8756]

Hello Everyone,
Working in the world of Microsoft Windows servers I've become very wise to the very general rule of the thumb "Reboot fixes most unexplained errors". Since we upgraded from 5.0.10 to 5.0.11 our Zimbra mail server has been rebooted more times due to this zmlogger error.

Yes it's true the reboot fixes the problem but it doesn't solve the problem. Today I found the post about changing the maximum connection from 10 to 20. I've done this and hope this will fix the problem until the new version comes out.

I will be happy when this bug is fixed and my server can go back to the norm of not rebooting until upgrades, etc are needed that require a restart.

Now with all that being said Zimbra mail server still is the best thing on the market

[phoenix]

I will be happy when this bug is fixed and my server can go back to the norm of not rebooting until upgrades, etc are needed that require a restart.

This bug does have a fix if you look at the bug report, there's a replacement script that will fix it now or you can wait for the next upgrade.

[SSS]

Try the attached script.

zmcontrol stop
ps aux | grep zimbra
kill -9 pid# <of those leftover logger pid's
Replace /opt/zimbra/bin/zmlogswatchctl - permissions should be root.root 755
zmcontrol start
zmcontrol stop
ps aux | grep zimbra <shouldn't show any leftover

It's also available on both both bugs: Bug 33730 - zmlogger fails to terminate at zmcontrol stop > duped> Bug 33604 - Server Status Error
(Works on RHEL5 & Ubuntu8, might be something quirky about Ubuntu6.)

Thank you very much for posting this! Solved the issue for me.
Does 5.0.12 also have this problem too?

[phoenix]

Thank you very much for posting this! Solved the issue for me.
Does 5.0.12 also have this problem too?

If you look at the bug report or the Product Portal you'll see that it was resolved in 5.0.12.