zmlogger not stopping on zimbra stop

[holunde]

I have ZCS 4.5.10 running fine on a Debian Etch machine.
One thing have puzzled me though, the Zimbra logger process doesn't stop, when I do a '/etc/init.d/zimbra stop'.
I mostly do this to do a remote rsync of /opt/zimbra at late night, and it's not a big problem. But isn't it supposed to stop? The log below seems to show, that it shuts down, but if I do a 'top' afterwords, zmlogger is still running..

Below is en extract of the log

Dec 17 20:35:02 ns2 su[701]: (pam_unix) session opened for user zimbra by (uid=0)
Dec 17 20:35:03 ns2 zimbramon[707]: 707:info: Stopping services
Dec 17 20:35:03 ns2 zimbramon[707]: 707:info: Stopping stats
Dec 17 20:35:03 ns2 zimbramon[707]: 707:info: Stopping mta
Dec 17 20:35:03 ns2 postfix/postfix-script: stopping the Postfix mail system
Dec 17 20:35:03 ns2 postfix/master[31162]: terminating on signal 15
Dec 17 20:35:03 ns2 saslauthd[31179]: server_exit : master exited: 31179
Dec 17 20:35:03 ns2 zimbramon[707]: 707:info: Stopping spell
Dec 17 20:35:03 ns2 zimbramon[707]: 707:info: Stopping snmp
Dec 17 20:35:03 ns2 zimbramon[707]: 707:info: Stopping antivirus
Dec 17 20:35:03 ns2 zimbramon[707]: 707:info: Stopping antispam
Dec 17 20:35:03 ns2 amavis[30785]: Net::Server: 2007/12/17-20:35:03 Server closing!
Dec 17 20:35:03 ns2 clamd[31041]: Pid file removed.
Dec 17 20:35:03 ns2 clamd[31041]: --- Stopped at Mon Dec 17 20:35:03 2007
Dec 17 20:35:08 ns2 zimbramon[707]: 707:info: Stopping imapproxy
Dec 17 20:35:09 ns2 zimbramon[707]: 707:info: Stopping mailbox
Dec 17 20:35:09 ns2 zmtomcatmgr[910]: threaddump requested
Dec 17 20:35:09 ns2 zmtomcatmgr[30747]: sending SIQUIT to tomcat/JVM process 30748
Dec 17 20:35:11 ns2 zmtomcatmgr[917]: stop requested
Dec 17 20:35:11 ns2 zmtomcatmgr[30747]: shutdown requested, sending TERM signal to 30748
Dec 17 20:35:11 ns2 zmtomcatmgr[917]: waiting for manager process 30747 to die
Dec 17 20:35:13 ns2 zmtomcatmgr[30747]: tomcat/JVM process exited (waitpid expected 30748 got 30748)
Dec 17 20:35:13 ns2 zmtomcatmgr[30747]: manager woke up from wait on tomcat/JVM with pid 30748
Dec 17 20:35:13 ns2 zmtomcatmgr[917]: manager process 30747 died, shutdown completed
Dec 17 20:35:18 ns2 zmtomcatmgr[922]: status requested
Dec 17 20:35:18 ns2 zmtomcatmgr[922]: file /opt/zimbra/log/zmtomcatmgr.pid does not exist
Dec 17 20:35:18 ns2 zmtomcatmgr[922]: assuming no other instance is running
Dec 17 20:35:18 ns2 zmtomcatmgr[922]: no manager process is running
Dec 17 20:35:18 ns2 zmtomcatmgr[923]: status requested
Dec 17 20:35:18 ns2 zmtomcatmgr[923]: file /opt/zimbra/log/zmtomcatmgr.pid does not exist
Dec 17 20:35:18 ns2 zmtomcatmgr[923]: assuming no other instance is running
Dec 17 20:35:18 ns2 zmtomcatmgr[923]: no manager process is running
Dec 17 20:35:22 ns2 zimbramon[707]: 707:info: Stopping logger
Dec 17 20:35:27 ns2 zimbramon[707]: 707:info: Stopping ldap
Dec 17 20:35:32 ns2 su[701]: (pam_unix) session closed for user zimbra
Dec 17 20:36:01 ns2 CRON[1018]: (pam_unix) session opened for user zimbra by (uid=0)
Dec 17 20:36:01 ns2 zmtomcatmgr[1115]: status requested
Dec 17 20:36:01 ns2 zmtomcatmgr[1115]: file /opt/zimbra/log/zmtomcatmgr.pid does not exist
Dec 17 20:36:01 ns2 zmtomcatmgr[1115]: assuming no other instance is running
Dec 17 20:36:01 ns2 zmtomcatmgr[1115]: no manager process is running
Dec 17 20:36:02 ns2 zimbramon[1019]: 1019:info: 2007-12-17 20:36:01, STATUS: ns2.egmont-hs.dk: antispam: Stopped
Dec 17 20:36:02 ns2 zimbramon[1019]: 1019:info: 2007-12-17 20:36:01, STATUS: ns2.egmont-hs.dk: antivirus: Stopped
Dec 17 20:36:02 ns2 zimbramon[1019]: 1019:info: 2007-12-17 20:36:01, STATUS: ns2.egmont-hs.dk: ldap: Stopped
Dec 17 20:36:02 ns2 zimbramon[1019]: 1019:info: 2007-12-17 20:36:01, STATUS: ns2.egmont-hs.dk: logger: Stopped
Dec 17 20:36:02 ns2 zimbramon[1019]: 1019:info: 2007-12-17 20:36:01, STATUS: ns2.egmont-hs.dk: mailbox: Stopped
Dec 17 20:36:02 ns2 zimbramon[1019]: 1019:info: 2007-12-17 20:36:01, STATUS: ns2.egmont-hs.dk: mta: Stopped
Dec 17 20:36:02 ns2 zimbramon[1019]: 1019:info: 2007-12-17 20:36:01, STATUS: ns2.egmont-hs.dk: snmp: Stopped
Dec 17 20:36:02 ns2 zimbramon[1019]: 1019:info: 2007-12-17 20:36:01, STATUS: ns2.egmont-hs.dk: spell: Stopped
Dec 17 20:36:02 ns2 zimbramon[1019]: 1019:info: 2007-12-17 20:36:01, STATUS: ns2.egmont-hs.dk: stats: Stopped

[jholder]

I think you're seeing this:
Bug 18653 - zmlogger orphaned on shutdown

Once you complete a total shutdown for your backup, you may want to put this little string in there to ensure everything is stopped:

kill -9 `ps -u zimbra -o "pid="`

[holunde]

Yes, this bugtrack is what I'm seeing. I've been script-killing this process like you suggest until now, and I'll keep doing it until it gets resolved, since it seems harmless to do so. Maybe in 5.0 it'll be fixed.
Thanks for the quick reply - and a GREAT product!