bh: doc/raw-howtos freebusy-troubleshooting.txt,NONE,1.1

[cvs at intevation.de]

Author: bh

Update of /kolabrepository/doc/raw-howtos
In directory doto:/tmp/cvs-serv10435

Added Files:
	freebusy-troubleshooting.txt 
Log Message:
new file with some information about troubleshooting free/busy lists


--- NEW FILE: freebusy-troubleshooting.txt ---
Troble Shooting Free/Busy lists in Kolab
========================================
$Id: freebusy-troubleshooting.txt,v 1.1 2005/05/20 13:57:26 bh Exp $


What to do when free/busy lists don't work with Kolab 2.0 and Kontact.
For background information on how the free/busy lists work in Kolab 2,
see [1]

Note: The free/busy lists are generated by the server, so any changes to
a calendar have to be synced to the server before they can be visible in
the free/busy lists.  So, don't forget to sync whenever you make a
change in the client.


Check Kontact Configuration
---------------------------

The relevant settings are in the configure dialog you get via
Settings|Configure Contact... in the part Organizer|Free/busy on the tab
Retrieve.

Server URL: https://kolabserver.domain/freebusy/%25EMAIL%25.ifb
Check "Use full email address for retrieval"
Check "Retrieve other people's free/busy information automatically"

Make sure the right username/password is being used to retrieve the
free/busy list.  Use the same as for imap.

If you configure kontact with the kolabwizard, the settings should be
OK.


Check the server
----------------

Check the apache access log, /kolab/var/apache/log/apache-access.log A
successfull free/busy retrieval looks like this (one line, with values
for client.domain, user1, etc. matching your setup.).

  client.domain - user1 [20/May/2005:12:58:56 +0200] "GET /freebusy/user2%40kolabserver.ifb HTTP/1.1" 200 395

You should also see the triggering of the free/busy list generation.
The triggering is done with http requests to a certain URL and looks
like this in the log:

  client.domain - user2 [20/May/2005:14:20:28 +0200] "GET /freebusy/trigger/user2/Calendar.pfb HTTP/1.1" 200 519


If the retrieval or the trigger isn't successful, check the logs of the
resource manager.  The freebusy part is configured in
/kolab/etc/resmgr/freebusy.conf.  look for the settings $params['log']
and $params['log_level'].  Useful settings for debugging are:


  // Where are we logging to? 
  $params['log'] = 'file:/kolab/var/resmgr/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; 


If you need to change anything, make the change in
/kolab/etc/kolab/templates/freebusy.conf.template and run
/kolab/sbin/kolabconf to regenerate the version under /kolab/etc/resmgr/

Then, check the logfile for errors.  if you just switched debugging on,
you need to retry to get the free/busy list.


[TODO: describe possible errors seen in the logs]


You may also want to have a look at the partial free/busy lists (pfbs)
from which the final lists are assembled.  The pfbs can be found under
/kolab/var/kolab/www/freebusy/cache/






References:

[1] How to handle freebusy lists for Kolab2
http://kolab.org/cgi-bin/viewcvs-kolab.cgi/doc/architecture/freebusy.txt?rev=HEAD