logger stopped by itself

[phoenix]

Originally Posted by celeron

No, I had installed zcs-4.5.0_GA_612.RHEL4.tgz version.

Wasn't the suggestion earlier that you upgrade to the most recent version of Zimbra then post again if you still had the problem?

[celeron]

I intend to upgrade from 4.5.0 to 4.5.3 release. Who have experiences in upgrading, please give me an advice.

Thanks.

[jholder]

Originally Posted by celeron

I intend to upgrade from 4.5.0 to 4.5.3 release. Who have experiences in upgrading, please give me an advice.

Thanks.

It's pretty straightforward.
Make sure you have a backup, and upgrade.

-john

[padraig]

Originally Posted by celeron

Hi, All
After I had started zmlogzmlogswatchctl, Zimbra logger operated normally for some days. Then, it failed again. I don't know what is reason. Please help me.
Thanks.
I'm using zcs-4.5.0_GA_612.RHEL4 version.

This is also happening in 4.5.1 NE RHEL4_x86_64
i think its caused by:
crontab -l | grep '30 2'
30 2 * * * find /opt/zimbra/log/ -type f -name \*log\* -mtime +8 -exec rm {} \; > /dev/null 2>&1
30 2 * * * find /opt/zimbra/tomcat/logs/ -type f -name \*log\* -mtime +8 -exec rm {} \; > /dev/null 2>&1

as mentioned it happens at 2.30am

the solution seems to be:
su - zimbra
zmloggerctl stop
zmloggerctl start
exit

[Splat]

I am having this problem with 4.5.0 and 4.5.2. Also had it with 4.0 and 4.1 I will post if it is still happening with 4.5.3.

[martinmuc]

Hi,

same Problem here,

this ist the first entry in /var/log/messages:

Mar 18 04:04:03 mail3 zimbramon[20801]: 20801:info: 2007-03-18 04:04:01, STATUS: mail3.domain.com: logger: Stopped

I have the latest version running. (NETWORK-4.5.2_GA_699.RHEL4_64)

How can i restart the logger?

Thx in advance,

Martin

[melody]

Hi,
I have same problem with the logger service.
I am using zcs-4.0.3_GA_406.RHEL4 version and i can't upgrade right now. So, is there a work arround to prevent this from happening?
Thanks.

[AimanA]

I seem to be having the same issue. My logger service is dying at some point. The wierd part is.. it didn't die at 2:30 in the morning.. it died at like 5 something PM.

What do you guys need from me to find the problem?

PS: I am running this on openSuSE 10.2 (updated) and Release 4.5.3_GA_733.SuSE10_20070228101815 openSUSE_10.2 FOSS edition

[rajahd]

Add me to the list. Every time I log into the management console I notice the logger is stopped. I have to remote into the server and restart the entire Zimbra suite to get it come back up (not that I've put extensive testing into trying to restart just pieces of it though).

FWIW, I can't recall the logger ever stopping until after I upgraded from 4.5.1 to 4.5.3. I haven't had any time to really investigate much but nothing obvious popped out in the logs as to why it would have stopped.

Edit: I'm running on an Ubuntu 6.10 server - ZCS 4.5.3 OS.

[phoenix]

Has anyone checked bugzilla for this problem or filed a bug report?