Kolab2 Server Troubleshooting - Free/Busy

From Kolab wiki

Jump to: navigation, search


Contents

[edit]

Problems with free/busy

The free/busy system mainly uses a few specific URL addresses. There are two systems you can check and if they both work your client should be able to access the free/busy system.

[edit]

Test fetching free/busy information from the web server

The free/busy information are provided by the web servers. The corresponding URL is https://my-domain.de/freebusy/%EMAIL%.ifb. The free/busy-List of the users John should be available at https://my-domain.de/freebusy/john@my-domain.de.ifb. The correct output should look something like this: 

BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//proko2//freebusy 1.0//EN
METHOD:PUBLISH
BEGIN:VFREEBUSY
ORGANIZER:MAILTO:john@my-domain.de
DTSTAMP:20061018T055225Z
URL:http\\://my-domain.de/freebusy/john@my-domain.de.ifb
DTSTART:20060911T220000Z
DTEND:20061215T230000Z
DTSTART:20061016T220000Z
FREEBUSY:20061018T101500Z/20061018T121500Z
FREEBUSY:20061018T130000Z/20061018T150000Z
FREEBUSY:20061018T150000Z/20061018T170000Z
FREEBUSY:20061019T061500Z/20061019T081500Z
END:VFREEBUSY
END:VCALENDAR

If you can connect without problems but get errors or warnings then the problem originates from the server. In that case you should activate the debugging settings for the free/busy system in /kolab/etc/resmgr/freebusy.conf: 

// Where are we logging to? 
$params['log'] = 'file:/var/log/kolab/freebusy/freebusy.log'; 
// What level of output should we log? Higher levels give more verbose
// output.  One of: RM_LOG_SILENT; RM_LOG_ERROR; RM_LOG_WARN;
// RM_LOG_INFO or RM_LOG_DEBUG.
$params['log_level'] = RM_LOG_DEBUG;

The debugging output will be written to the specified file.

If you somehow cannot access the free/busy url, get SSL errors or have similar connection trouble the problem probably originates from the client setup.

Distribution specific information (This information might apply if you run Kolab natively on non-OpenPKG distributions)
Gentoo
The free/busy parameter file can be found at

/etc/kolab/resmgr/freebusy.conf

[edit]

Test generation of free/busy on the web server

The free/busy information are generated on the web server. A special trigger URL (https://my-domain.de/freebusy/trigger/%EMAIL%/%FOLDER%.pfb) is necessary for this process. The free/busy list for the Calender folder of user John should be generated when triggering (fetching) https://my-domain.de/freebusy/trigger/john@my-domain.de/Kalender.pfb. The clients won't read the resulting input but it also look like a vCalender: 

BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//proko2//freebusy 1.0//EN
METHOD:PUBLISH
BEGIN:VFREEBUSY
ORGANIZER:MAILTO:john@my-domain.de
DTSTAMP:20061018T060239Z
DTSTART:20061017T220000Z
DTEND:20061216T230000Z
FREEBUSY:20061018T101500Z/20061018T121500Z
FREEBUSY:20061018T130000Z/20061018T150000Z
FREEBUSY:20061018T150000Z/20061018T170000Z
FREEBUSY:20061019T061500Z/20061019T081500Z
END:VFREEBUSY
BEGIN:VFREEBUSY
ORGANIZER:MAILTO:john@my-domain.de
DTSTAMP:20061018T060239Z
DTSTART:20061017T220000Z
DTEND:20061216T230000Z
FREEBUSY:20061018T101500Z/20061018T121500Z
FREEBUSY:20061018T130000Z/20061018T150000Z
FREEBUSY:20061018T150000Z/20061018T170000Z
FREEBUSY:20061019T061500Z/20061019T081500Z
END:VFREEBUSY
END:VCALENDAR

If this does not work you should activate the debugging settings as specified above and check the log files.

[edit]

The server seems to work fine but the client does not

[edit]

All clients

A correctly configured client should issue requests to both types of addresses given above once it needs free/busy information. Consequently you should find entries like the following in your apache logs

  • Fetching: 
my-domain.de - mike [20/May/2006:14:34:16 +0200] "GET /freebusy/john%40my-domain.de.ifb HTTP/1.1" 200 395
  • Generating 
my-domain.de - walter [20/May/2006:14:34:16 +0200] "GET /freebusy/trigger/walter%40my-domain.de/Kalender.pfb HTTP/1.1" 200 395

Use the following command to search for such entries: 

grep "\(ifb\|pfb\)" /var/log/apache2/*

If there are no such entries the client is not correctly configured and tries to fetch the information from an incorrect location.

[edit]

Kontact

Is the retrieval address (https://my-domain.de/freebusy/%EMAIL%.ifb) specified correctly in the kontact settings?

[edit]

Outlook

When fetching the free/busy information you may not receive a message about an insecure SSL certificate.

[edit]

My problem persists

None of the above hints did help you to solve your problem?

Please check your options for getting support and reporting errors.

[edit]

Back

Back to the troubleshooting index

Retrieved from "http://wiki.kolab.org/index.php/Kolab2_Server_Troubleshooting_-_Free/Busy"
Personal tools
Page Categories