[turba] LDAP problems

[E. Stuart Hicks]

The versions are:

Turba 1.2.1
Horde 2.2.4
OpenLDAP 2.2.5
PHP 4.3.5RC2-dev

I've linked Horde's LDAP schema into the schema directory and added in
include for it into the slapd.conf file.

Like I said, though, I'm a total newbie to LDAP so 'trivial' is hardly the
word I'd use.  LDAP is proving to be rather convoluted and counterintuitive.
Honestly, I only put it on here because I wanted an address book system that
I could use the same way you use an IMAP server - one central location that
mail clients can connect to wherever they are on the Internet.  I was hoping
that I wouldn't have to learn LDAP inside out to do so, either, because the
documentation I found on openldap.org is rather "lacking" at best and
doesn't tell me how to test anything or use half of the tools included.  I
suppose I shouldn't expect too much out of Michigan, though...them being
able to find their 'on' switches amazes me enough. :)

Regardless of everything else, I still would think that the public LDAP
servers should work just fine; however, they're still managing to lock up my
server for anything Horde-related.  That's the error that worried me the
most because it's got nothing to do with my local LDAP server.  PHP should
be talking to a known-working LDAP server across the net and getting results
back.  Instead, the page locks up, the rest of Horde locks up, and the
server needs restarting.  (Just Horde, though - the rest of the website
doesn't miss a beat.  It's very odd.)

Stu


----- Original Message ----- 
From: "Edwin Culp" <eculp at viviendaatualcance.com.mx>
To: "E. Stuart Hicks" <ehicks at binarymagi.com>
Cc: <turba at lists.horde.org>
Sent: Sunday, February 08, 2004 6:36 PM
Subject: Re: [turba] LDAP problems


> Quoting "E. Stuart Hicks" <ehicks at binarymagi.com>:
>
> First it would be a good idea to let folks know which versions of
everything you
> are trying to use, what errors you are seeing in the browser and those
that are
> found in your horde.log, messages, slapd.log, httpd-error.log, etc.  As
far as
> the schema is concerned, I would recommend that you not modify
core.schema.
> There should be a horde.schema in horde/scripts/ldap.  I usually just do a
>
> ln -s /usr/local/www/data/horde/scripts/ldap/horde.schema \
> /usr/local/etc/openldap/schema
>
> The above is all on one line and they are my paths, yours will probably be
> different.  Then just kill slapd a restart.
>
> Then I would recommend that you assure that you have a working ldap
> configuration by using the command line interface, adding a few users and
> searching to see if it is working as you expect.  After that the
configuration
> should be trivial because it is mostly the same that you tested with the
> command interface.
>
> If you continue to have problems you should probably send the items
mentioned
> above and your specific configuration.
>
> Good luck.  You have some work to do, I'm afraid.
>
> ed
> >
> > A very strange problem also happens when I try accessing public email
repos
> > like Bigfoot or Verisign.  Everytime I try searching one the entire
Horde
> > system stops functioning until I restart Apache.  The rest of the site,
even
> > the PHP-based sections, still work fine - it's just Horde that dies.
The
> > only difference I can think of is that Horde runs under a vhost
'webmail'
> > while everything else runs under 'www'.  They are the same server,
though.
> >
> > If anyone can help, I'd greatly appreciate it.  TIA
> >
> > Stu
> >
> >
> > --
> > Turba mailing list - Join the hunt: http://horde.org/bounties/#turba
> > Frequently Asked Questions: http://horde.org/faq/
> > To unsubscribe, mail: turba-unsubscribe at lists.horde.org
>
>