We have just recently moved from Red Hat's Linux Fedora Core 4 to Red
Hat's Linux Enterprise OS. In the process of moving to a new OS, we
changed from OpenLDAP version 2.2.23 to version 2.3.20. Now, every time
we start slapd, along with the standard *.dbb files, it creates an
"alock" file in the
--On Thursday, May 25, 2006 12:33 PM -0400 "Ramseyer, Ken"
<[EMAIL PROTECTED]> wrote:
We have just recently moved from Red Hat's Linux Fedora Core 4 to Red
Hat's Linux Enterprise OS. In the process of moving to a new OS, we
changed from OpenLDAP version 2.2.23 to version 2.3.20. Now, every
Ramseyer, Ken wrote:
We have just recently moved from Red Hat's Linux Fedora Core 4 to Red
Hat's Linux Enterprise OS. In the process of moving to a new OS, we
changed from OpenLDAP version 2.2.23 to version 2.3.20. Now, every time
we start slapd, along with the standard *.dbb files, it creates
On Thu, May 25, 2006 at 10:26:03AM -0700, Quanah Gibson-Mount wrote:
>
> alock is an autorecovery mechanism introduced in the OpenLDAP 2.3 release to
> assist
> with autorecovery. Given more information on the error messages coming from
> alock
> would be useful, since it is supposed to help
--On Thursday, May 25, 2006 10:15 PM +0400 Dmitriy Kirhlarov
<[EMAIL PROTECTED]> wrote:
On Thu, May 25, 2006 at 10:26:03AM -0700, Quanah Gibson-Mount wrote:
alock is an autorecovery mechanism introduced in the OpenLDAP 2.3
release to assist with autorecovery. Given more information on th
On Thu, May 25, 2006 at 01:17:47PM -0700, Quanah Gibson-Mount wrote:
>>>alock is an autorecovery mechanism introduced in the OpenLDAP 2.3
>>>release to assist with autorecovery. Given more information on the
>>>error messages coming from alock would be useful, since it is supposed
>>>to help yo
--On Thursday, May 25, 2006 1:56 PM -0700 Todd Lyons <[EMAIL PROTECTED]>
wrote:
On Thu, May 25, 2006 at 01:17:47PM -0700, Quanah Gibson-Mount wrote:
alock is an autorecovery mechanism introduced in the OpenLDAP 2.3
release to assist with autorecovery. Given more information on the
error
On Thu, May 25, 2006 at 04:13:41PM -0700, Quanah Gibson-Mount wrote:
>>Ah, that's good to know. I upgraded an old 2.1.30 production server to
>>2.3.21 with bdb 4.3 and the load went through the roof, searches were
>>blindingly slow, etc. I'm rolling back to 2.2.30 right now with db 4.2.
>>We'll
On Thu, May 25, 2006 at 01:56:22PM -0700, Todd Lyons wrote:
>>BDB 4.3 is a known problem release. The suggested BDB release is
>>4.2.52+patches, and possible BDB 4.4.20+patches. But not BDB 4.3.anything.
>Ah, that's good to know. I upgraded an old 2.1.30 production server to
>2.3.21 with bdb 4
--On Thursday, May 25, 2006 4:32 PM -0700 Todd Lyons <[EMAIL PROTECTED]>
wrote:
On Thu, May 25, 2006 at 01:56:22PM -0700, Todd Lyons wrote:
BDB 4.3 is a known problem release. The suggested BDB release is
4.2.52+patches, and possible BDB 4.4.20+patches. But not BDB
4.3.anything.
Ah, tha
I don't change these files often, so I'm not speaking from personal
experience, because I'd just slapadd the entire thing again. But...
I think you have to recreate your bdb environment after changing
DB_CONFIG. cd to /var/lib/openldap-bdb and run db_recover (do NOT do this
while OpenLDAP is using
--On Thursday, May 25, 2006 6:24 PM -0700 Quanah Gibson-Mount
<[EMAIL PROTECTED]> wrote:
Well, since you are using a version of BDB that is recommended you not
use, all bets are off. On my AMD boxes, I get some 13,000
searches/second using BDB as the backend (bdb 4.2.52+patches) on a 1
S
On Thu, May 25, 2006 at 06:24:55PM -0700, Quanah Gibson-Mount wrote:
>>No, it didn't fix the speed problem. When using the ldbm backend, the
>>machine sits at load around 0.1 and 2% or 3% cpu usage. I switch to bdb
>>backend and my load jumps to 14 or so, searches take seconds to complete
>>(of
Dmitriy Kirhlarov writes:
> BTW, I'm using openldap 2.3.21 on freebsd and linux boxes. I use it
> with bdb43. On all machines I have easy reproduceble problem -- if
> slapd killing hardly he can't start. Eat all cpu, don't answer to
> clients and can be killed only with -9 signal.
> After running d
14 matches
Mail list logo
