Free/busy lists broken - HELP!

Albrecht Dreß albrecht.dress at lios-tech.com
Thu Oct 30 10:17:14 CET 2008


Hi all,

I have a HUGE problem with free/busy lists which unfortunately occurred  
only after migrating to the new Kolab system...

The problem is that I apparently can successfully trigger fb list  
generation, but reading them always returns an empty list.  Here are  
the details (huge, sorry):

Call (as calendar user)  
"https://kolab.my-server.de/freebusy/trigger/the.user%40my-company.com/Kalender.pfb",  
which gives the following log entries in  
/kolab/var/kolab-freebusy/log/freebusy.log:

<snip>
Kolab Free/Busy [debug] [horde] Starting generation of partial  
free/busy data for folder the.user at my-company.com/Kalender [pid 8740 on  
line 52 of "/kolab/var/kolab/www/freebusy/pfb.php"]
Kolab Free/Busy [debug] [horde] Partial free/busy data of owner  
the.user at my-company.com on server srv-portal.my-server.de requested by  
user calendar at my-company.com. [pid 8740 on line 63 of  
"/kolab/var/kolab/www/freebusy/pfb.php"]
Kolab Free/Busy [debug] [horde] Creating free/busy information from  
1225321200 to 1230505200 [pid 8740 on line 317 of  
"/kolab/lib/php/Horde/Kolab/Freebusy.php"]
Kolab Free/Busy [debug] [horde] No relevance value found for  
user/the.user/Kalender [pid 8740 on line 207 of  
"/kolab/lib/php/Horde/Kolab/Freebusy.php"]
Kolab Free/Busy [debug] [horde] ACL for user/the.user/Kalender is  
a:1:{s:22:"calendar at my-company.com";s:12:"lrswipkxtecd";} [pid 8740 on  
line 241 of "/kolab/lib/php/Horde/Kolab/Freebusy.php"]
Kolab Free/Busy [debug] [horde] No extended ACL value found for  
user/the.user/Kalender [pid 8740 on line 263 of  
"/kolab/lib/php/Horde/Kolab/Freebusy.php"]
Kolab Free/Busy [debug] [horde]  
FreeBusyCache::store(file=lios-tech^com/wieland^hill/Kalender,  
relevance=admins, acl=Array, xacl= calendar at my-company.com) [pid 8740  
on line 127 of "/kolab/lib/php/Kolab/Freebusy/Cache.php"]
Kolab Free/Busy [debug] [horde] Delivering partial free/busy data  
(extended=). [pid 8740 on line 120 of  
"/kolab/var/kolab/www/freebusy/pfb.php"]
Kolab Free/Busy [debug] [horde] Partial free/busy generation complete,  
execution time was 0.16107892990112 seconds. [pid 8740 on line 128 of  
"/kolab/var/kolab/www/freebusy/pfb.php"]
</snip>

The returned data looks fine:

<snip>
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//proko2//freebusy 1.0//EN
METHOD:PUBLISH BEGIN:VFREEBUSY
ORGANIZER;cn=The User:MAILTO:the.user at my-company.com
DTSTAMP:20081030T090125Z
DTSTART:20081029T230000Z
DTEND:20081228T230000Z
FREEBUSY:20081030T140000Z/20081030T143000Z
FREEBUSY:20081030T180000Z/20081030T190000Z
FREEBUSY:20081031T090000Z/20081031T103000Z
FREEBUSY:20081101T230000Z/20081105T230000Z
FREEBUSY:20081111T090000Z/20081111T100000Z
FREEBUSY:20081113T090000Z/20081113T163000Z
FREEBUSY:20081205T180000Z/20081205T220000Z
FREEBUSY:20081219T180000Z/20081219T230000Z
END:VFREEBUSY
END:VCALENDAR
</snip>

Now I call  
"https://kolab.my-server.de/freebusy/the.user@my-company.com.ifb",  
giving the following log data:

<snip>
Kolab Free/Busy [debug] [horde] Starting generation of free/busy data  
for user the.user at my-company.com [pid 26797 on line 49 of  
"/kolab/var/kolab/www/freebusy/freebusy.php"]
Kolab Free/Busy [debug] [horde] Free/busy data of owner  
the.user at my-company.com on server srv-portal.my-server.de requested by  
user . [pid 26797 on line 60 of  
"/kolab/var/kolab/www/freebusy/freebusy.php"]
Kolab Free/Busy [debug] [horde] Free/busy generation complete,  
execution time was 0.018148899078369 seconds. [pid 26797 on line 96 of  
"/kolab/var/kolab/www/freebusy/freebusy.php"]
</snip>

but the data returned is

<snip>
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//proko2//freebusy 1.0//EN
METHOD:PUBLISH
BEGIN:VFREEBUSY
ORGANIZER;cn=The User:MAILTO:the.user at my-company.com
DTSTAMP:20081030T074609Z
URL:http://kolab.my-server.de/freebusy/the.user@my-company.com.ifb
COMMENT:This is a dummy vfreebusy that indicates an empty calendar
FREEBUSY:19700101T000000Z/19700101T000000Z
END:VFREEBUSY
END:VCALENDAR
</snip>

Any idea what goes wrong here?  The kolab server has a number of DNS  
aliases (like kolab, srv-kolab, srv-portal, ...), might this be a  
problem (shouldn't, as Apache replies, right?)?

Help - my users are killing me as their calendars don't work! ;-)

Thanks for any insight,
Albrecht.




More information about the users mailing list