Re: [Kolab-devel] Upgrade report 3.1 to 3.2 on Debian Wheezy

On Saturday 15. February 2014 19.27.52 Tobias Brunner wrote:
> 
> I was brave enough to upgrade from 3.1 to 3.2 on Debian Wheezy. Here is
> my experience:
> 
> kolabd 100% CPU
> ---------------
> Since the upgrade the process "/usr/bin/python /usr/sbin/kolabd -l
> warning --fork --user kolab --pid-file /run/kolabd/kolabd.pid" is
> running with 100% CPU. Could not find a log giving hints on what's going
> wrong. strace does also not give any usable hints.

This sounds somewhat familiar. Since kolabd's job is to synchronise the IMAP 
and LDAP components, if I remember correctly, any failure with either of those 
may cause kolabd to "busy loop". I seem to remember this happening a few 
months ago before I managed to get the configuration sorted out.

Paul