Kolab 3.2 Freebusy

[Brady, Mike]

On 2014-02-28 06:48, Christian Hügel wrote:
> Nevermind, found it. But I get a buch of errors here:
> 
> 
> (18:45:13) findkolabfoldersjob.cpp(111):        "GetMetaData failed,
> server replied: A000111 BAD Missing arguments to Getmetadata "
> (18:45:13) findkolabfoldersjob.cpp(111):        "GetMetaData failed,
> server replied: A000112 BAD Missing arguments to Getmetadata "
> (18:45:13) findkolabfoldersjob.cpp(111):        "GetMetaData failed,
> server replied: A000113 BAD Missing arguments to Getmetadata "
> (18:45:13) findkolabfoldersjob.cpp(111):        "GetMetaData failed,
> 
> Looks like a bug: https://issues.kolab.org/show_bug.cgi?id=2027
> 
> Christian
> 
> 
> Am 27.02.2014 18:42, schrieb Christian Hügel:
>> Thank you for your reply. From which config file takes freebusyd the
>> port/server configuration?
>> 
>> 
>> Am 27.02.2014 16:50, schrieb hede:
>>> Am Thu, 27 Feb 2014 14:36:03 +0100
>>> schrieb "Hügel, Christian" <christian.huegel at stonebyte.de>:
>>> 
>>>> kolab-freebusyd(14758) KIMAP::SessionThread::reconnect: 
>>>> connectToHost
>>>> "localhost" 143
>>> 
>>> You are connecting to non-ssl imap. Is it enabled in imapd.conf?
>>> (allowplaintext: yes)
>>> _______________________________________________
>>> users mailing list
>>> users at lists.kolab.org
>>> https://lists.kolab.org/mailman/listinfo/users
>>> 
>> _______________________________________________
>> users mailing list
>> users at lists.kolab.org
>> https://lists.kolab.org/mailman/listinfo/users
> _______________________________________________
> users mailing list
> users at lists.kolab.org
> https://lists.kolab.org/mailman/listinfo/users

I experienced the same issue with 3.2 and just ended up disabling the 
freebusyd cron job. Hardly a solution I know, but this problem was 
putting so much load on my test server with a continual stream of 
failures that it was impacting my ability to do anything else.

I am assuming that is due to changes in Cyrus IMAP 2.5?