Page 1 of 2 12 LastLast
Results 1 to 10 of 20

Thread: Logger stops by itself after 5.0.15 upgrade

  1. #1
    nufan is offline Senior Member
    Join Date
    Jun 2008
    Posts
    59
    Rep Power
    7

    Default Logger stops by itself after 5.0.15 upgrade

    Just upgraded to latest version over the weekend, now I see the "logger" service stopping by itself in the web admin console. A "zmcontrol status" also shows the logger service stopped. I can start it again by typing zmloggerctl start in the console. I have not experienced this occuring up until this recent upgrade.

    Is there anything I can do to keep the logger from stopping by itself? Thanks for any input

  2. #2
    uxbod's Avatar
    uxbod is offline Moderator
    Join Date
    Nov 2006
    Location
    UK
    Posts
    8,017
    Rep Power
    24

    Default

    Anything reported in your logfiles at all ? Need a little bit more information please

  3. #3
    nufan is offline Senior Member
    Join Date
    Jun 2008
    Posts
    59
    Rep Power
    7

    Default

    thanks for the reply ! Would you be so kind as to point me in the right direction as to what log files you would like to see? Also the easiest way for me to read them? I find when i just cat them in terminal it can only show so much.

    Thanks !

  4. #4
    uxbod's Avatar
    uxbod is offline Moderator
    Join Date
    Nov 2006
    Location
    UK
    Posts
    8,017
    Rep Power
    24

    Default

    /var/log/zimbra.log you can also check /opt/zimbra/log/mysql_error.log aswell.

  5. #5
    nufan is offline Senior Member
    Join Date
    Jun 2008
    Posts
    59
    Rep Power
    7

    Default

    thanks for that, the mysql_error.log didn't have much in it, just a few entries from when I updated over the weekend. The last time I noticed the logger was down was first thing this morning so its possible it happened over night, unfortunately in terminal I can only go back about half an hour since there is so many entries, so I'm thinking I will need to search those logs (zimbra.log) pretty close to the next time it goes down, will paste results when it occurs.

  6. #6
    shibu's Avatar
    shibu is offline Junior Member
    Join Date
    Jul 2006
    Posts
    7
    Rep Power
    9

    Default

    Please check Logger - Zimbra :: Wiki

    it has docs on how to determine why logger isn't working

  7. #7
    Bill Brock is offline Outstanding Member
    Join Date
    May 2007
    Location
    Oklahoma
    Posts
    703
    Rep Power
    9

    Default Twice....

    yesterday I received Admin e-mails telling me my logger had stopped. Looking at the status, both GUI and CLI showed it to be working. Not sure why it would stop or better yet why it would start back on its own. Since it was running when I checked I didn't go to the logs for further details. If it happens again I guess I will do some more digging.

  8. #8
    nufan is offline Senior Member
    Join Date
    Jun 2008
    Posts
    59
    Rep Power
    7

    Default

    Thanks for the replies, I am still trying to work this out. Again this morning I came in and the logger is not working. I checked my admin account and noticed the following:

    Since the upgrade to 5.15 on March 14th, the logger has gone down on the following dates and times with the following messages:

    Code:
    Mar 15 03:16:07 xsrv1 zimbramon[12701]: 12701:err: Service status change: xsrv1.intranet.brandonsun.com logger changed from running to stopped\n
    Mar 16 17:01:49 xsrv1 zimbramon[12701]: 12701:err: Service status change: xsrv1.intranet.brandonsun.com logger changed from stopped to running\n
    Mar 17 03:15:54 xsrv1 zimbramon[12701]: 12701:err: Service status change: xsrv1.intranet.brandonsun.com logger changed from running to stopped\n
    Mar 17 03:39:21 xsrv1 zimbramon[12701]: 12701:err: Service status change: xsrv1.intranet.brandonsun.com logger changed from stopped to running\n
    Mar 17 03:40:35 xsrv1 zimbramon[12701]: 12701:err: Service status change: xsrv1.intranet.brandonsun.com logger changed from running to stopped\n
    Mar 17 03:15:54 xsrv1 zimbramon[12701]: 12701:err: Service status change: xsrv1.intranet.brandonsun.com logger changed from running to stopped\n
    Mar 17 03:39:21 xsrv1 zimbramon[12701]: 12701:err: Service status change: xsrv1.intranet.brandonsun.com logger changed from stopped to running\n
    Mar 17 03:40:35 xsrv1 zimbramon[12701]: 12701:err: Service status change: xsrv1.intranet.brandonsun.com logger changed from running to stopped\n
    Mar 17 13:15:10 xsrv1 zimbramon[12701]: 12701:err: Service status change: xsrv1.intranet.brandonsun.com logger changed from stopped to running\n
    I have followed that link for logger problems without much luck. When I am doing zmcontrol status I am getting that the logger is stopped and zmlogswatchctl is not running.

    As per the links directions it says:

    2. If "zmlogswatchctl is not running", verify whether A) the file /opt/zimbra/log/logswatch.pid exists, and B) there is a single /opt/zimbra/libexec/logswatch process.

    Code:
    cat /opt/zimbra/log/logswatch.pid
    ps aux | grep logswatch
    I ran both those commands and got the following output:

    Code:
    xsrv1:/Users/systemsadministrator zimbra$ cat /opt/zimbra/log/logswatch.pid
    26388
    xsrv1:/Users/systemsadministrator zimbra$ ps aux | grep logswatch
    zimbra   28055   0.0 -0.0    18060    196  p1  R+    8:47AM   0:00.00 grep logswatch
    Unfortunately the article doesn't say what to do after those commands.

    Appreciate any further comments, thanks !

  9. #9
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,506
    Rep Power
    57

    Default

    That would indicate that it's not running as you should get an output like your entry above plus the running one like this:

    Code:
    zimbra   12282  0.0  0.3   6736  4880 ?        S    04:03   0:00 /usr/bin/perl /opt/zimbra/libexec/logswatch --config-file=/opt/zimbra/conf/logswatchrc --use-cpan-file-tail --pid-file=/opt/zimbra/log/logswatch.pid --script-dir=/tmp -t /var/log/zimbra.log
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  10. #10
    nufan is offline Senior Member
    Join Date
    Jun 2008
    Posts
    59
    Rep Power
    7

    Default

    Quote Originally Posted by phoenix View Post
    That would indicate that it's not running as you should get an output like your entry above plus the running one like this:

    Code:
    zimbra   12282  0.0  0.3   6736  4880 ?        S    04:03   0:00 /usr/bin/perl /opt/zimbra/libexec/logswatch --config-file=/opt/zimbra/conf/logswatchrc --use-cpan-file-tail --pid-file=/opt/zimbra/log/logswatch.pid --script-dir=/tmp -t /var/log/zimbra.log
    ok fair enough, and I can start the logger fine, so I'm still curious why its stopping by itself though, any suggestions ? :|

Page 1 of 2 12 LastLast

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. Replies: 10
    Last Post: 03-23-2009, 08:29 AM
  2. Logger Stops
    By bcurve in forum Administrators
    Replies: 7
    Last Post: 01-13-2009, 07:28 PM
  3. Zimbra logger stops periodically
    By Miklos Kalman in forum Administrators
    Replies: 2
    Last Post: 01-11-2009, 07:37 AM
  4. [SOLVED] 5.0.4 Upgrade Issues - Logger, Shared Spam
    By Cryophallion in forum Administrators
    Replies: 13
    Last Post: 04-21-2008, 12:37 PM
  5. High iowait from logger after upgrade to 4.5.9
    By pi13137 in forum Installation
    Replies: 9
    Last Post: 11-09-2007, 05:29 AM

Posting Permissions

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