[Kolab-devel] [issue3732] Logging needed for errors when creating a Kolab session object
Thomas Arendsen Hein
kolab-issues at intevation.de
Fri Jul 3 16:07:47 CEST 2009
New submission from Thomas Arendsen Hein <thomas at intevation.de>:
Kolab Server 2.2.2 contains the Horde_Auth package based on the tarball
http://pear.horde.org/get/Auth-0.1.1.tgz
I'd like to log errors when creating the session, currently they are not
visible. I hacked together this one:
diff -urN Auth-0.1.1.orig/Auth/kolab.php Auth-0.1.1/Auth/kolab.php
--- Auth-0.1.1.orig/Auth/kolab.php 2008-10-29 14:35:45.000000000 +0100
+++ Auth-0.1.1/Auth/kolab.php 2009-07-03 16:00:53.314506327 +0200
@@ -59,6 +59,7 @@
if (class_exists('Horde_Kolab_Session')) {
$session = &Horde_Kolab_Session::singleton($userId, $credentials,
true);
if (is_a($session->auth, 'PEAR_Error')) {
+ Horde::logMessage(sprintf("Error while authenticating session
for %s: %s", $userId, $session->auth->getMessage()), __FILE__, __LINE__,
PEAR_LOG_ERR);
$this->_setAuthError(AUTH_REASON_MESSAGE,
$session->auth->getMessage());
}
} else {
Now I'm able to see this in freebusy.log:
Jul 03 15:49:44 Kolab Free/Busy [error] [horde]
Error while authenticating session for user at example.com:
Search failed. Error was: Size limit exceeded
[on line 62 of "/kolab/lib/php/Horde/Auth/kolab.php"]
(I will create a separate issue for this particular error)
_setAuthError already stores the message somewhere, but it does not get printed.
Fixing this might be a better solution, but the hard coded log above would
already be helpful.
Please change this in Auth and do a backport as patch for kolab_2_2_branch.
----------
assignedto: wrobel
messages: 20746
nosy: bh, martin, thomas, wilde, wrobel
priority: urgent
status: unread
title: Logging needed for errors when creating a Kolab session object
topic: freebusy, server
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3732>
___________________________________________________
More information about the devel
mailing list