[SOLVED] Zimbra logger service auto stops at specific time

[secnix]

Hi All,

I'm using ZCS Release 6.0.6_GA_2324.RHEL5_64_20100406150533 CentOS5_64 FOSS edition on CentOS 5.3 64bit

Recently, I receive mail notifications about logger service stop every one or two days at a specific time.

Here are the messages:

Jun  2 04:04:48 mail zimbramon[4893]: 4893:err: Service status change: mail.domain.com logger changed from running to stopped

May 31 04:04:45 mail zimbramon[14201]: 14201:err: Service status change: mail.domain.com logger changed from running to stopped

May 29 04:04:11 mail zimbramon[6923]: 6923:err: Service status change: mail.domain.com logger changed from running to stopped

I've tried searching in forums but got no clues. Is there any suggestion?

Thanks a lot.

Regards,
N.A

[secnix]

Please help me!!!

[ewilen]

Sounds like an old bug that was fixed years ago. https://bugzilla.zimbra.com/show_bug.cgi?id=5824

I doubt it's the same exact issue but the similarity in timing is interesting.

[ewilen]

Hm, actually I'm getting the same message occasionally, always at 4:02 AM. But both the admin console and zmcontrol status show logger as running. I hadn't gotten one since July of last year, then starting March 31 I've gotten 7 of them. We upgraded to ZCS 6 in late March so I doubt it's a coincidence.

Timing seems to correlate with daily event in the system crontab:


# cat /etc/crontab
SHELL=/bin/bash
PATH=/sbin:/bin:/usr/sbin:/usr/bin
MAILTO=root
HOME=/

# run-parts
01 * * * * root run-parts /etc/cron.hourly
02 4 * * * root run-parts /etc/cron.daily
22 4 * * 0 root run-parts /etc/cron.weekly
42 4 1 * * root run-parts /etc/cron.monthly

[secnix]

I also got this error about a few days after I upgrade my Zimbra from version 5.0.9 to 6.0.6.

From the bug 5824, will the error stop if I run those command:

Method of hupping swatch on logrotate is updated to:

 kill -HUP `cat /opt/zimbra/log/swatch.pid`
 kill -HUP `cat /opt/zimbra/log/logswatch.pid`

Thanks,
NA

[ewilen]

No, I wouldn't do that. Those are quite old notes referring to ZCS 3, and they have to do with how a nightly cron job is run (which may have changed since then), not something you'd do manually.

If your system is otherwise working, I wouldn't worry about this but you could make an entry in bugzilla (I'd rate it as a minor bug, but it's your call). If you do, please post the bug # here so others can track it.

[secnix]

Originally Posted by ewilen

No, I wouldn't do that. Those are quite old notes referring to ZCS 3, and they have to do with how a nightly cron job is run (which may have changed since then), not something you'd do manually.

If your system is otherwise working, I wouldn't worry about this but you could make an entry in bugzilla (I'd rate it as a minor bug, but it's your call). If you do, please post the bug # here so others can track it.

Thanks for your reply. This error has not shown up for the last 5 days. I'll wait for some more days before making an entry in bugzilla.

Btw, my system is still working properly.

Regards,
N.A

[secnix]

Jun 27 04:04:35 mail zimbramon[26520]: 26520:err: Service status change: example.com logger changed from running to stopped

It happened again :-<

[ewilen]

Yes, it's happened again on my system as well, on June 18 and June 22. But I see absolutely no other problems.

For more info on the logger service see http://wiki.zimbra.com/wiki/Logger_(ZCS_6.0.x_and_later)

[secnix]

Thanks for your notice.