[Kolab-devel] Freebusy data not provided (native openSUSE)

[Gunnar Wrobel]

Hi Richard,

Quoting Richard <richard at radoeka.nl>:

> Hi,
>
> when visiting this link
> https://kolab2.radoeka.nl/freebusy/richard@radoeka.nl.ifb
> I get the following response (with debugging enabled):
> Debug: [horde] Starting generation of free/busy data for user
> richard at radoeka.nl [on line 190 of
> "/usr/share/php5/PEAR/Horde/Kolab/FreeBusy.php"]
>
> Debug: [horde] Free/busy data of owner richard at radoeka.nl on server
> https://kolab2.radoeka.nl/freebusy requested by user richard at radoeka.nl.
> [on line 203 of "/usr/share/php5/PEAR/Horde/Kolab/FreeBusy.php"]
>
> Debug: [horde] Debug 1 [on line 216 of
> "/usr/share/php5/PEAR/Horde/Kolab/FreeBusy.php"]
>
>
> The last line was added by me, to Horde/Kolab/FreeBusy.php
>
> This is with kolab-freebusy-0.1.3 (but 0.1.2 showed the same problem).
>
> The code is:
> 215         $this->_initCache();
> 216         Horde::logMessage("Debug 1", __FILE__, __LINE__, PEAR_LOG_DEBUG);
> 217
> 218         $result = $this->_cache->load($access, $req_extended);
> 219         Horde::logMessage("Debug 2", __FILE__, __LINE__, PEAR_LOG_DEBUG);
> 220         if (is_a($result, 'PEAR_Error')) {
> 221             $error = array('type' => FREEBUSY_ERROR_NOTFOUND, 'error' =>
> $result);
> 222             $view = new Horde_Kolab_FreeBusy_View_error($error);
> 223             return $view;
> 224         }
>
> line 216 is executed, and I think 218 as well.
> 219 is never executed :(
>
> When I uncomment the line (216), the script continues, but fails with another
> error (of course) later on).
>
> What could be the reason that  $result = $this->_cache->load($access,
> $req_extended);
> fails?  Can the cause be in wrong directory names, of permissions?

Yes, I believe so.

>
> For now I have this:
> # grep cache *
> config.php:/* Location of the cache files */
> config.php:$conf['fb']['cache_dir']    = '/var/cache/freebusy';
>
> drwxrwxrwx 2 root root 4096 2009-03-05 21:57 /var/cache/freebusy/

While this sounds unsafe :) the script should definitely have write access.

>
> # find /var/cache/freebusy
> /var/cache/freebusy
>
> Is it possible to print the values of $access and $req_extended?
>
> Hopefully, you have a clue what is wrong over here and can help me to
> solve it!

Before going into the code, I'd rather like to have a look at the log  
files. On a standard Kolab server the free/busy system will generate  
two log files within /kolab/var/kolab-freebusy/log/. One is named  
"freebusy.log" and the other "php-error.log". I'd be especially  
interested in the second one. The fact that you don't see any further  
output from the script indicates that a fatal error occured. In that  
case PHP should log an error in the current PHP error log file. You  
can also output the location of that file by adding a line like this  
into the script:

  var_dump(ini_get('error_log'));

If this shows

  bool(false)

no errors get logged and you should fix your PHP configuration.

Another important setting is

  php -r "var_dump(ini_get('log_errors'));"

'log_errors' also needs to be turned on to get log entries in the error log.

You can also set 'display_errors' to be 'On'. In that case PHP errors  
should be dumped to the browser.

Cheers,

Gunnar


>
>
> --
> Richard
>
> _______________________________________________
> Kolab-devel mailing list
> Kolab-devel at kolab.org
> https://kolab.org/mailman/listinfo/kolab-devel
>



-- 
______ http://kdab.com _______________ http://kolab-konsortium.com _

p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium

____ http://www.pardus.de _________________ http://gunnarwrobel.de _
E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
Tel.   : +49 700 6245 0000                          Bundesstrasse 29
Fax    : +49 721 1513 52322                          D-20146 Hamburg
--------------------------------------------------------------------
    >> Mail at ease - Rent a kolab groupware server at p at rdus <<
--------------------------------------------------------------------


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digitale PGP-Unterschrift
URL: <http://lists.kolab.org/pipermail/devel/attachments/20090307/ba9ab4ca/attachment.sig>