I seem to be having the infamous "Service logger stopped/started" issue at random intervals. My logs:
[CODE]May 28 04:48:07 mail zmconfigd[1126]: Fetching All configs
May 28 04:48:07 mail zmconfigd[1126]: All configs fetched in 0.06 seconds
May 28 04:48:08 mail zmconfigd[1126]: Executed: /opt/zimbra/bin/zmloggerctl status norewrite returned 1 (30 - 13) (0.03 sec)
May 28 04:48:08 mail zmconfigd[1126]: Service status change: mail.somecompany.net logger changed from running to stopped
...
May 28 04:49:10 mail zmconfigd[1126]: Fetching All configs
May 28 04:49:10 mail zmconfigd[1126]: All configs fetched in 0.05 seconds
May 28 04:49:11 mail zmconfigd[1126]: Service status change: mail.somecompany.net logger changed from stopped to running[/CODE]
From some research, my understanding is this "issue" is caused when the logs rotate. My research seemed to indicate this issue was resolved back in 2011, as per this discussion: http://forums.zimbra.com/administrators/47127-solved-zmconfigd-warning-7-0-0-ga.html#post209426
I'm running Zimbra 8.6.0_GA_1153 (build 20141215151155) on CentOS 6.x. I've had this issue since day one of deployment, but just ignored it until now. A few years back we had a breach of the Zimbra server via an attachement upload exploit, and since then getting weird emails from the system has kept me paranoid.
Is there a work-around or fix for this issue in current versions?
