Page 1 of 4 123 ... LastLast
Results 1 to 10 of 33

Thread: Help us fix Bug 14945 :)

  1. #1
    jholder's Avatar
    jholder is offline Former Zimbran
    Join Date
    Oct 2005
    Location
    Thatcher, AZ
    Posts
    5,606
    Rep Power
    20

    Exclamation Help us fix Bug 14945 :)

    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:
    Code:
    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:
    Code:
    /tmp/zmlogger.out 
    /tmp/logprocess.out 
    /tmp/logswatch.out
    to jholder@zimbra.com

    It would be helpful to include the following in your message:
    Code:
    Name:
    RAM:
    OS:
    HD Space:
    # of Users:
    How often the logger quits.
    Thanks for your help!!

    -john
    Attached Files Attached Files

  2. #2
    JoshuaPrismon is offline Zimlet Guru & Moderator
    Join Date
    Nov 2005
    Posts
    477
    Rep Power
    9

    Default

    Quote Originally Posted by jholder View Post
    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:
    Code:
    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:
    Code:
    /tmp/zmlogger.out 
    /tmp/logprocess.out 
    /tmp/logswatch.out
    to jholder@zimbra.com

    It would be helpful to include the following in your message:
    Code:
    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.

  3. #3
    GCNS is offline Junior Member
    Join Date
    May 2007
    Location
    Glasgow, Scotland
    Posts
    6
    Rep Power
    8

    Default Bug 14945

    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.

  4. #4
    LMStone's Avatar
    LMStone is offline Moderator
    Join Date
    Sep 2006
    Location
    477 Congress Street | Portland, ME 04101
    Posts
    1,367
    Rep Power
    10

    Default

    Quote Originally Posted by GCNS View Post
    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

  5. #5
    jholder's Avatar
    jholder is offline Former Zimbran
    Join Date
    Oct 2005
    Location
    Thatcher, AZ
    Posts
    5,606
    Rep Power
    20

    Default

    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.

  6. #6
    kirme3 is offline Trained Alumni
    Join Date
    Apr 2006
    Location
    Illinois
    Posts
    194
    Rep Power
    9

    Default

    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

  7. #7
    mmorse's Avatar
    mmorse is offline Moderator
    Join Date
    May 2006
    Location
    USA
    Posts
    6,242
    Rep Power
    21

    Default

    Quote Originally Posted by kirme3 View Post
    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)
    Last edited by mmorse; 06-06-2007 at 09:04 PM.

  8. #8
    kirme3 is offline Trained Alumni
    Join Date
    Apr 2006
    Location
    Illinois
    Posts
    194
    Rep Power
    9

    Default

    D'oh....my bad.

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

  9. #9
    mmorse's Avatar
    mmorse is offline Moderator
    Join Date
    May 2006
    Location
    USA
    Posts
    6,242
    Rep Power
    21

    Default

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

  10. #10
    LMStone's Avatar
    LMStone is offline Moderator
    Join Date
    Sep 2006
    Location
    477 Congress Street | Portland, ME 04101
    Posts
    1,367
    Rep Power
    10

    Default

    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.

Page 1 of 4 123 ... LastLast

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. how to fix Bug 16285 if I use zimbra 4.5.3_Frank
    By catzilla in forum Installation
    Replies: 4
    Last Post: 07-03-2007, 12:15 AM
  2. Do I have to upgrade to fix the DST bug?
    By yang in forum Administrators
    Replies: 3
    Last Post: 03-02-2007, 01:44 PM
  3. Replies: 1
    Last Post: 10-12-2006, 10:28 PM
  4. Cannot delete accounts bug. How long for a fix?
    By jrmy in forum Administrators
    Replies: 6
    Last Post: 01-17-2006, 07:53 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •