some more details:
it takes about 20min from a zimbra restart until the CPU load starts to increase
top:
Code:
top - 20:56:24 up 3:46, 2 users, load average: 2.71, 1.70, 1.19
Tasks: 102 total, 2 running, 100 sleeping, 0 stopped, 0 zombie
Cpu(s): 99.3% us, 0.7% sy, 0.0% ni, 0.0% id, 0.0% wa, 0.0% hi, 0.0% si
Mem: 1034656k total, 908240k used, 126416k free, 21944k buffers
Swap: 2096376k total, 112k used, 2096264k free, 254524k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
9875 zimbra 17 0 720m 247m 13m S 99.7 24.5 4:34.57 java
14297 root 16 0 2196 1116 856 R 0.3 0.1 0:00.03 top
1 root 16 0 1468 472 412 S 0.0 0.0 0:01.11 init and this is the process:
Code:
zimbra 9875 16.7 34.0 737852 352584 ? Sl 20:18 6:45 \_ /opt/zimbra/jdk1.5.0_08/bin/java -Xms404m -Xmx404m -client -XX:NewRatio=2 -Djava.awt.headless=true -Dcatalina.base=/opt/zimbra/apache-tomcat-5.5.15 -Dcatalina.home=/opt/zimbra/apache-tomcat-5.5.15 -Djava.io.tmpdir=/opt/zimbra/apache-tomcat-5.5.15/temp -Djava.library.path=/opt/zimbra/lib -Djava.endorsed.dirs=/opt/zimbra/apache-tomcat-5.5.15/common/endorsed -classpath /opt/zimbra/apache-tomcat-5.5.15/bin/bootstrap.jar:/opt/zimbra/apache-tomcat-5.5.15/bin/commons-logging-api.jar:/opt/zimbra/lib/jars/zimbra-launcher.jar com.zimbra.cs.launcher.TomcatLauncher
and 15min later top looks like this:
Code:
top - 21:11:23 up 4:01, 2 users, load average: 8.46, 5.00, 2.96
Tasks: 104 total, 3 running, 101 sleeping, 0 stopped, 0 zombie
Cpu(s): 94.3% us, 5.7% sy, 0.0% ni, 0.0% id, 0.0% wa, 0.0% hi, 0.0% si
Mem: 1034656k total, 987752k used, 46904k free, 14460k buffers
Swap: 2096376k total, 248k used, 2096128k free, 201964k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
9875 zimbra 17 0 721m 352m 13m S 93.7 34.9 18:56.38 java
15713 zimbra 25 0 9144 5408 2140 R 2.0 0.5 0:01.31 zmgengraphs
1 root 15 0 1468 472 412 S 0.0 0.0 0:01.11 init
I am watching the logs but can't see anything unusual there 
please help.....