[horde] hang on login

[Philip Goisman]

	   3. hang on login (Philip Goisman)
	   6. Re: hang on login (Jan Schneider)

	------------------------------

	Message: 6
	Date: Mon, 24 Apr 2006 11:08:51 +0200
	From: Jan Schneider <jan at horde.org>
	Subject: Re: [horde] hang on login
	To: horde at lists.horde.org
	Message-ID: <20060424110851.2rejf7mtn4804kk4 at neo.wg.de>
	Content-Type: text/plain; charset=ISO-8859-15; DelSp="Yes";
		format="flowed"

	Zitat von Philip Goisman <goisman at physics.arizona.edu>:

	> I installed Horde: 3.2-cvs, Imp: H3 (4.2-cvs), Ingo: H3 (1.2-cvs), and
	> Turba: H3 (2.2-cvs) on a redhat EL4 system.  Without Turba, login is
	> fast and smooth and all works as one would expect.  With Turba there
	> is a very long delay until connection.  With turba, the logs always
	> show the following:

	Read the instructions in docs/INSTALL and config/sources.php.

	> Apr 23 22:02:49 HORDE [debug] [turba] Hook _horde_hook_share_init in  
	>  application horde
	> not called. [on line 1448 of "/usr/share/pear/Horde.php"].
	>
	> Since it's been over 10 months since someone last asked about this   
	> error; and,
	> since noone responded to the question, I figure the problem is mine.
	> However, I'm clueless here.  I did see some recent messages on   
	> use_shares, but
	> apparently noone experiences the long hang until connection with Turba.

	This is not an error, it's a debug message.

	Jan.

	-- 
	Do you need professional PHP or Horde consulting?
	http://horde.org/consulting/

Firstly, thank you for the reply.  My mistake and apology for referring to the
debug message as an error.  

The problem is now resolved thanks to an online email in gmane.comp.horde.turba
dated 2.15.2006 from impuser <at> bitrealm.com in an email reply to
mike <at> theupstairsroom.com.  The solution is to delete the entries for ldap
in ../turba/config/sources.php.  For the version I'm using - Turba: H3 (2.2-cvs) -
it's lines 166 through 404.  

166 if (Util::extensionExists('ldap')) {

403 // End LDAP check.
404 }

I'm not sure what was happening with ldap, but since I don't use it, it seemed 
like an easy fix.

Philip