CPU High Spikes around every 2 minutes ZSC 7.1.4

mrcoffee11 · Post by **mrcoffee11** » Tue Jun 19, 2012 2:36 am

Great idea.
1957 zimbra 20 0 974m 65m 11m S 91.1 4.2 0:02.74 /opt/zimbra/java/bin/java -XX:ErrorFile=/opt/zimbra/log -client -Xmx256m -Dzimbra.home=/opt/zimbra -Djava.library.path=/opt/zimbra/lib -Djava.ext.dirs=/opt/zimbra/java/jre/lib/e ....

3548 zimbra 20 0 36396 7096 2100 R 2.7 0.4 0:00.08 /usr/bin/perl /opt/zimbra/bin/ldapHelper.pl true KIPgdjmOn ldap_db_cachesize 10000
Does this mean anything to anyone?

diallo0024 · Post by **diallo0024** » Wed Jun 20, 2012 8:25 am

Hello sir! I can't really say what your processes/logs above mean, but one last suggestion (if I may). I typically run the following commands on each upgrade to maintain minimal cpu spikes/usage:
{most of these I believe you've already done. I'm just stating the "exact" steps that work 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
I stopped the logging process:
$ su - zimbra

$ zmprov ms fill_in_your_hostname -zimbraServiceEnabled logger

Then as the root user I edit /etc/logrotate.d/zimbra and comment out all logger related start / reload commands e.g.
# su - zimbra -c "/opt/zimbra/bin/zmswatchctl restart" > /dev/null 2>&1 || true

# su - zimbra -c "/opt/zimbra/bin/zmlogswatchctl start"
Not sure if this was of any help, but best of luck in your search for a solution!

mrcoffee11 · Post by **mrcoffee11** » Wed Jun 20, 2012 8:54 am

Thnx for your reply. This is what I did in versions before 7.1.4 with success. From 7.1.4 this does not work (for me). Fresh install. Got no clue. Help is very much apppreciated.

Roderick

mrcoffee11 · Post by **mrcoffee11** » Wed Jun 20, 2012 9:46 am

I got it to stop!
# su - zimbra

# zmconfigdctl stop

# zmlocalconfig -x | grep zmmtaconfig

# zmmtaconfig_enable_config_restarts = true

zmmtaconfig_interval = 6000

zmmtaconfig_listen_port = 7171

zmmtaconfig_log_level = 3

zmmtaconfig_watchdog = FALSE
The question is: is it a problem to to stop zmconfigd? What does it do?

ccelis5215 · Post by **ccelis5215** » Wed Jun 20, 2012 7:23 pm

[QUOTE]

The question is: is it a problem to to stop zmconfigd? What does it do?[/QUOTE]
Take a look Zmconfigd - Zimbra :: Wiki
ccelis

mrcoffee11 · Post by **mrcoffee11** » Thu Jun 21, 2012 4:45 am

Ok, Zmconfigd takes care of activating configuration changes.

The zmmtaconfig_interval is normally set to 60 seconds. I changed it to 6000. Still I get these 140 seconds interval high cpu peaks of this process. Could anyone expand on this? Is this a bug?

mrcoffee11 · Post by **mrcoffee11** » Sun Jun 24, 2012 2:05 pm

Fedora 11 is depricated so I did an installationl and migration to Centos 6.2 (very very minimal install): performance is really excellent! (and I don't need the zmconfigdctl stop command)

toppse · Post by **toppse** » Mon Sep 10, 2012 8:57 am

[quote user="mrcoffee11"]I got it to stop!
# su - zimbra

# zmconfigdctl stop

# zmlocalconfig -x | grep zmmtaconfig

# zmmtaconfig_enable_config_restarts = true

zmmtaconfig_interval = 6000

zmmtaconfig_listen_port = 7171

zmmtaconfig_log_level = 3

zmmtaconfig_watchdog = FALSE
The question is: is it a problem to to stop zmconfigd? What does it do?[/QUOTE]
Hi ,
we have the same problem with RedHat 5.7 and Zimbra 7.2 -> high CPU Peaks

I saw that the CPU Load increase if someone do an upload of an attachment of 10MB..(that is not really much)
Did this settings help?
Kind Regards,

toppse