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

Thread: [SOLVED] ZCS 6.0 - zmlogger service using very high CPU

Hybrid View

  1. #1
    Join Date
    Sep 2009
    Posts
    7
    Rep Power
    6

    Default [SOLVED] ZCS 6.0 - zmlogger service using very high CPU

    I have been running Zimbra for about 2 years now and have upgraded periodically throughout the 5.x code stream. I just upgraded Zimbra from 5.0.16 to "Release 6.0.0_GA_1802.RHEL5_64_20090830141723 FOSS edition" and have read about the changes to the zmlogger process.

    My issue is that since the upgrade, the zmlogger process appears to be constantly using excessive CPU. Here is a typical output from the top command and this is pretty typical (going from 99% to 119% with each cycle):
    Mem: 2051248k total, 1964088k used, 87160k free, 23248k buffers
    Swap: 4095992k total, 0k used, 4095992k free, 630704k cached

    PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
    6894 zimbra 25 0 54976 8772 2436 R 99.9 0.4 2:21.38 zmlogger

    I have attached the output from the commands recommended by Zimbra from zmlogger troubleshooting section. Also, the /var/log/zimbra-stats.log file is growing extremely quickly and doesn't appear to be getting "logrotated".

    As much as I like the new functionality, I think I may have pulled the trigger a little early upgrading from 5.0.16 to 6.0.

    Thanks for any insight regarding this issue....

    Regards,
    Jeff (RHCE)
    Attached Files Attached Files

  2. #2
    Join Date
    Sep 2009
    Posts
    7
    Rep Power
    6

    Default

    BUMP

    Any ideas? I have gotten numerous Nagios emails about High Load. This morning my machine is practically nonresponsive and I will probably have to hard reboot.

    Thanks,
    Jeff

  3. #3
    Join Date
    Feb 2008
    Location
    Peru
    Posts
    94
    Rep Power
    7

    Default

    i noticed the same in my box, im running RHEL5 and Zimbra 6.0 (Community edition)

    zmlogger take a lot of cpu.

  4. #4
    Join Date
    Sep 2009
    Posts
    21
    Rep Power
    6

    Default

    Quote Originally Posted by gvillaran View Post
    i noticed the same in my box, im running RHEL5 and Zimbra 6.0 (Community edition)

    zmlogger take a lot of cpu.

    I was having the same problem. I found a post by Raj that did the trick for me

    su - zimbra
    zmlocalconfig -e zmmtaconfig_interval=6000
    zmprov mcf zimbraLogRawLifetime 7d
    zmprov mcf zimbraLogSummaryLifetime 30d
    /opt/zimbra/libexec/zmlogprocess

    su - zimbra
    crontab -e
    */60 * * * * /opt/zimbra/libexec/zmstatuslog

  5. #5
    Join Date
    Jan 2008
    Posts
    223
    Rep Power
    7

    Default

    Quote Originally Posted by speedy3k View Post
    I was having the same problem. I found a post by Raj that did the trick for me

    su - zimbra
    zmlocalconfig -e zmmtaconfig_interval=6000
    zmprov mcf zimbraLogRawLifetime 7d
    zmprov mcf zimbraLogSummaryLifetime 30d
    /opt/zimbra/libexec/zmlogprocess

    su - zimbra
    crontab -e
    */60 * * * * /opt/zimbra/libexec/zmstatuslog
    -----------------------------------------------------
    Ok. I had this issue & got it rectified by following above.

  6. #6
    Join Date
    Feb 2008
    Location
    Peru
    Posts
    94
    Rep Power
    7

    Default

    ok i did what u recommend me, i am looking that the logger service take cpu but not for to long now.
    can someone explain me what we just change with those commands? im pretty new at zimbra.

    thanks in advance

  7. #7
    Join Date
    Sep 2009
    Posts
    7
    Rep Power
    6

    Default

    Quote Originally Posted by speedy3k View Post
    I was having the same problem. I found a post by Raj that did the trick for me

    su - zimbra
    zmlocalconfig -e zmmtaconfig_interval=6000
    zmprov mcf zimbraLogRawLifetime 7d
    zmprov mcf zimbraLogSummaryLifetime 30d
    /opt/zimbra/libexec/zmlogprocess

    su - zimbra
    crontab -e
    */60 * * * * /opt/zimbra/libexec/zmstatuslog
    Thanks for the reply. I made the necessary changes. the zmlogger process still consumes a lot of CPU periodically but it does finally free up CPU resources when watching it under "top". My "sar" graphs now show a more normalized CPU usage across the 4 CPUs. It still does take significantly more CPU than my pre Zimbra 6.0 (5.0.16) CPU load graphs. My other services don't need to be disabled since the only server that really ever consumes CPU (other than Zimbra) is my Netapp simulator. Hopefully as Zimbra 6.x matures, the zmlogger process issues will be addressed.
    l l
    Thanks again,
    Jeff

    PS - The /var/log/zimbra-stats.log appears to still be growing very fast. From 14:32 to 15:47 and the log is already just shy of 9MB.

  8. #8
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,587
    Rep Power
    58

    Default

    Quote Originally Posted by gvillaran View Post
    i noticed the same in my box, im running RHEL5 and Zimbra 6.0 (Community edition)

    zmlogger take a lot of cpu.
    You might also want to consider disabling any unnecessary services on your server (if they're not already disabled).
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  9. #9
    Join Date
    Jan 2008
    Posts
    223
    Rep Power
    7

    Default

    Ok.

    Beginning with 6.0, the architecture of the logger service has changed
    This is as explained in release note & following wiki.So future releases should take care of this.

    Main Page - Zimbra :: Wiki
    index.php?title=Logger%28GnR%29).

  10. #10
    Join Date
    Jan 2008
    Location
    Berlin, Germany
    Posts
    203
    Rep Power
    7

    Default ZCS 6.0 Remove Logger & CPU Usage

    Same issue here: We upgraded from 5.018 NE to 6.0.0 NE. zmlogger was eating up 100% CPU of 2x6 GHz as soon as somebody did an Outlook Sync of a 500 MByte Mailbox. Also zmlogger caused 500 - 800 MHz basic CPU usage even if the server was idle.

    I disabled the logger service and removed the rpm:

    Code:
    su - zimbra
    zmprov ms `hostname` -zimbraServiceEnabled logger
    and as root user

    Code:
    /etc/init.d/zimbra stop
    rpm -e zimbra-logger-6.0.0_GA_1802.RHEL5-20090830122136
    /etc/init.d/zimbra start
    The CPU usage immediately dropped to the same level as of 5.0.18 and before and everything seemed to be o.k. again - without Server Status in the Admin Frontend, but this is hardly a show stopper for now.

    12 hours later the same high CPU Usage, the same slow server response . So I did some research: zmlogger service was up and running again!

    Code:
    find /opt/zimbra/ -type f -name zmlog*
    
    /opt/zimbra/log/zmlogswatch.out
    /opt/zimbra/log/zmlogprocess.state
    /opt/zimbra/libexec/zmlogprocess
    /opt/zimbra/libexec/zmlogger
    /opt/zimbra/conf/zmlogrotate
    /opt/zimbra/bin/zmlogswatchctl
    /opt/zimbra/bin/zmloggerctl
    /opt/zimbra/bin/zmloggerhostmap
    Wow! zmlogger is still there. Did "rpm -e" not remove the package? Daily logfile rotation left the commands enabled and did a restart (of cause). So this is the actual /etc/logrotate.d/zimbra file

    Code:
    /var/log/zimbra.log {
        daily
        missingok
        notifempty
        create 0644 zimbra zimbra
        postrotate
          killall -HUP syslogd 2> /dev/null || true
          su - zimbra -c "/opt/zimbra/bin/zmswatchctl restart" > /dev/null 2>&1 || true
        endscript
        compress
    }
    
    /var/log/zimbra-stats.log {
        daily
        missingok
        notifempty
        create 0644 zimbra zimbra
        postrotate
          killall -HUP syslogd 2> /dev/null || true
          su - zimbra -c "/opt/zimbra/bin/zmlogswatchctl restart" > /dev/null 2>&1 || true
        endscript
        rotate 0
    }
    which should have been removed by rpm -e as well as the program files itself.

    I manually disabled the restart command:

    Code:
    # su - zimbra -c "/opt/zimbra/bin/zmlogswatchctl restart" > /dev/null 2>&1
    For now we live without the logger Service and btw without any Graphs - but this is beeing discussed in another thread already.

    I hope this will be cleaned up together with the other zmlogger issues as soon as possible because this is not an improvement over 5.x at all.

    Any recommendations how to fix this high CPU usage are very welcome.

    Regards

    Andreas

Similar Threads

  1. Mail is being queued, not delivered!
    By icepick94 in forum Administrators
    Replies: 12
    Last Post: 01-22-2009, 06:03 AM
  2. Replies: 20
    Last Post: 03-18-2008, 05:37 AM
  3. Replies: 41
    Last Post: 10-29-2007, 02:36 PM
  4. 3.1 on FC4 problems
    By cohnhead in forum Installation
    Replies: 8
    Last Post: 05-26-2006, 11:16 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
  •