Help us fix Bug 14945 :)

[jholder]

Hi-
We're trying to track down a pesky bug. Some of you guys may be familiar with it. It's Bug 14945 - logger intermittently stops without warning after pruning.

Brian has developed a script that to help track this down.

I've attached the script, and for a few of those who help, I'll send you out a shirt or something.

If there's problems with the script, you should post them here.
Please don't post your logs to this thread. I want to attach them to the bug & get you some gear.

Instructions:

cd /opt/zimbra 
cp bin/zmlogswatchctl bin/zmlogswatchctl.orig 
cp libexec/zmlogprocess libexec/zmlogprocess.orig 
cp libexec/zmlogger libexec/zmlogger.orig 
tar xzvf logger-debug.tar.gz 
zmlogswatchctl restart

If the logger quits, then please send me:

/tmp/zmlogger.out 
/tmp/logprocess.out 
/tmp/logswatch.out

to jholder@zimbra.com

It would be helpful to include the following in your message:

Name:
RAM:
OS:
HD Space:
# of Users:
How often the logger quits.

Thanks for your help!!

-john

[JoshuaPrismon]

Originally Posted by jholder

Hi-
We're trying to track down a pesky bug. Some of you guys may be familiar with it. It's Bug 14945 - logger intermittently stops without warning after pruning.

Brian has developed a script that to help track this down.

I've attached the script, and for a few of those who help, I'll send you out a shirt or something.

If there's problems with the script, you should post them here.
Please don't post your logs to this thread. I want to attach them to the bug & get you some gear.

Instructions:

cd /opt/zimbra 
cp bin/zmlogswatchctl bin/zmlogswatchctl.orig 
cp libexec/zmlogprocess libexec/zmlogprocess.orig 
cp libexec/zmlogger libexec/zmlogger.orig 
tar xzvf logger-debug.tar.gz 
zmlogswatchctl restart

If the logger quits, then please send me:

/tmp/zmlogger.out 
/tmp/logprocess.out 
/tmp/logswatch.out

to jholder@zimbra.com

It would be helpful to include the following in your message:

Name:
RAM:
OS:
HD Space:
# of Users:
How often the logger quits.

Thanks for your help!!

-john

Doh. It happened to me right before I upgraded to 5.0. I will keep a look on it though.

[GCNS]

Hello,

I think the bug disappeared in release 4.5.5 - logger hasn't stopped since we upgraded. It used to fail each weekend but hasn't so far.

[LMStone]

Originally Posted by GCNS

Hello,

I think the bug disappeared in release 4.5.5 - logger hasn't stopped since we upgraded. It used to fail each weekend but hasn't so far.

Nope. Logger just died on us today, and we are on 4.5.5 NE on SuSE ES9.

FWIW, we notice when the logger dies the way we restart it is to issue a zmloggerctl stop (which cleans up the mysql pid file that is hanging around) and then zmloggerctl start.

Seems to die once every few weeks.

We'll look at the script and see if we can't help.

All the best,
Mark

[jholder]

Yeah, it seems random. We've had reports that it was solved in 4.5.4 as well.

And when it does happen, we can't always get the .out files (which get removed if you restart teh logger).

That's why we need your help.

[kirme3]

This happens to me every night. We reinstalled our logger server and since then, every night after pruning, the logger service stops. I had a support case for it, but nobody responded. I noticed this case and figured it was just pooled into that.

For the Zimbra employees out there interested, the case number is 00009744.

My server is OS X PPC(Dual G5 adn 4 GB mem).

When I try to untar the file I get the following:

tar: Read 9757 bytes from logger-debug.tar.gz
tar: This does not look like a tar archive
tar: Skipping to next header
tar: Error exit delayed from previous errors

I hope I'm not acting like a n00b here

[mmorse]

Originally Posted by kirme3

When I try to untar the file I get the following:

tar: Read 9757 bytes from logger-debug.tar.gz
tar: This does not look like a tar archive
tar: Skipping to next header
tar: Error exit delayed from previous errors

I hope I'm not acting like a n00b here

That's because it's gzipped (.gz) gotta love extensions...there's .gz & .tgz & tar.z ...

>tar xvzf logger-debug.tar.gz
OR
> gunzip logger-debug.tar.gz (The file becomes logger-debug.tar)
> tar xvf logger-debug.tar (It will create a directory called 'logger-debugger' and put the files stored in that archive in it.)
OR
> gunzip < file.tar.gz | tar xvf -
OR
> gtar xvzf file.tar.gz

on mac OS X, as part of the tar syntax, you can also use -z OR --gzip OR --gunzip
Mac OS X Manual Page For tar(1)

[kirme3]

D'oh....my bad.

Everything has been changed on my end....we'll see if it fails tonight. We're on 4.5.3.

[mmorse]

eh the mac can be tricky-most new tar programs auto see the .gz when your trying to extract

[LMStone]

OK, it's installed.

FWIW, we had to chown and chmod the extracted files to match the originals.

Also, zmlogswatchctl does not accept the "restart" argument, so we just stopped it and then started it.

I'll keep you posted; thanks for posting this--we are happy to help.