AW: Kolab eating memory & CPU

[Jim Philips]

On Sunday 23 January 2005 10:19 am, you wrote:
> Hello there,
>
> i do not have these problem on my box. Even with ae p2 400mhz  not.
>
> What does ">top" say???
> Sometimes i have imapd there on second position, but only with 2% of cpu
> and only if there is someone synchronising the outlook or whatever client.
>
>
> Greetings
>
> remo
>
> -----Ursprüngliche Nachricht-----
> Von: kolab-users-bounces at kolab.org [mailto:kolab-users-bounces at kolab.org]
> Im Auftrag von Jim Philips
> Gesendet: Samstag, 22. Januar 2005 22:16
> An: kolab-users at kolab.org
> Betreff: Kolab eating memory & CPU
>
> I just installed Kolab2 Beta 2. It runs just fine, but whenever i running,
> it
> takes more than 50% CPU. This box has an AMD XP 2400+ chip and 512 megs of
> RAM. Is it typical for Kolab to be so CPU intensive?

Well, I found out a little more. Top showed that cyrman was taking up most of 
the CPU. So finaaly I looked at /kolab/var/imapd/log. The logs there are 
enormous! From master.log, I see this over and over again:

Jan 23 08:57:43 localhost <debug> master[11611]: about to 
exec /kolab/bin/imapd
Jan 23 08:57:43 localhost <debug> master[21499]: process 11611 exited, status 
75
Jan 23 08:57:43 localhost <warning> master[21499]: service imap pid 11611 in 
READY state: terminated abnormally
Jan 23 08:57:43 localhost <debug> master[11612]: about to 
exec /kolab/bin/imapd
Jan 23 08:57:43 localhost <debug> master[21499]: process 11612 exited, status 
75
Jan 23 08:57:43 localhost <warning> master[21499]: service imap pid 11612 in 
READY state: terminated abnormally
Jan 23 08:57:43 localhost <debug> master[11613]: about to 
exec /kolab/bin/imapd
Jan 23 08:57:43 localhost <debug> master[21499]: process 11613 exited, status 
75
Jan 23 08:57:43 localhost <warning> master[21499]: service imap pid 11613 in 
READY state: terminated abnormally
Jan 23 08:57:43 localhost <debug> master[11614]: about to 
exec /kolab/bin/imapd

From misc.log, I see this over and over again:

Jan 23 08:57:43 localhost <error> imap[11613]: DBERROR: 
reading /kolab/var/imapd/db/skipstamp, assuming the worst: (2) No such file 
or directory
Jan 23 08:57:43 localhost <debug> imap[11613]: executed
Jan 23 08:57:43 localhost <error> imap[11613]: Fatal error: must run as the 
Cyrus user
Jan 23 08:57:43 localhost <error> imap[11614]: DBERROR: 
reading /kolab/var/imapd/db/skipstamp, assuming the worst: (2) No such file 
or directory
Jan 23 08:57:43 localhost <debug> imap[11614]: executed
Jan 23 08:57:43 localhost <error> imap[11614]: Fatal error: must run as the 
Cyrus user

So, I'm going to start looking into the imap problems.