[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: AW: AW: AW: slapcat hangs without error message

Quanah Gibson-Mount wrote

--On Tuesday, February 20, 2007 9:03 AM +0100 Voigtlaender@hansenet.com wrote:

Its a slapd 2.2.23 (debian package) with a bdb Backend on a Debian Sarge
system. Transaction Logging is enabled, I set the cachesize in DB_CONFIG
to 1 GB. I have one Master and two Slaves. On one of the Slaves the
slapcat worked until yesterday, today it is broken again. The other Slave
is ok. I see no errors in syslogs. My id2entry.bdb is 1,6 GB, in a
complete ldif-File I have 31 Mio lines. Could this be a problem ?

I'd suggest pursuing this with Debian. As a user of debian, I'm sure you are aware that they patch source code with things that are not found in the master source, and those things could always be the potential source of bugs or other types of errors. I would advise not using their package, and instead either getting a prebuilt distribution like CDS from Symas Corporation, or building it yourself.


Quanah Gibson-Mount
Principal Software Developer
ITS/Shared Application Services
Stanford University
GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html

Also a Debian user here, and I can pretty strongly recommend just building it yourself. A ./configure --help will reveal an amazing wealth of options available to you. I tried a few combinations of the packages before going ahead and building it myself, and I think it's really worth going through that process to get the OpenLDAP implementation you want.

As an added bonus, you get all of your ldap applications and libraries to be the same version. Speaking specifically of what we've got in Debian Stable right now, some packages depend on ldap libraries from OpenLDAP 2.1.17, and some depend on libraries built from 2.2.23. This should soon be fixed as packages make the move from unstable/testing into stable, but it's all no big deal if you're at least content running software labeled "unstable".

As a final note...if you do use the debian packages, be very sure to dive into the documents included with the packages (usually /usr/share/<packagename>), as debian tends to put files in unexpected places that eventually make sense but initially confuse the hell out of you.