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

Re: (ITS#7383) slapd startup issue with mdb

On Sep 11, 2012, at 8:14 PM, hyc@symas.com wrote:

> marco@schirrmeister.net wrote:
>> Full_Name: Marco Schirrmeister
>> Version: 2.4.32
>> OS: CentOS6 x86_64
>> URL: ftp://ftp.openldap.org/incoming/
>> Submission from: (NULL) (
>> I'm testing mdb since the last versions with our dataset.
>> If I use my production config slapd does't start up.
>> The following is in the log file.
>> Sep 11 16:48:37 ds71 slapd2.4[8349]: @(#) $OpenLDAP: slapd 2.4.32 (Sep  6 2012
>> 13:50:54) $#012#011mschirrmeister@defrsl6bh2.ogilvy.com:/home/mschirrmeister/rpmbuild/BUILD/openldap-2.4.32/servers/slapd
>> Sep 11 16:48:37 ds71 slapd2.4[8349]: mdb_attr_dbs: database "dc=ogilvy,dc=com":
>> mdb_open(omgPublishDate) failed: Too many open files in system (23).
>> Sep 11 16:48:37 ds71 slapd2.4[8349]: backend_startup_one (type=mdb,
>> suffix="dc=ogilvy,dc=com"): bi_db_open failed! (23)
>> Sep 11 16:48:37 ds71 slapd2.4[8349]: slapd stopped.
>> My /etc/security/limits.conf file has already the following entries.
>> *	soft	nofile	65535
>> *	hard	nofile	65535
>> No matter what I try on the OS side, the error above comes up.
>> I have about 130 index attributes in my config. Looks to me that this is the
>> problem.
>> If I comment 8 attributes, slapd starts fine.
> There is a hardcoded limit of 128. This same limit exists in back-bdb/hdb. You
> can just edit back-mdb.h (or back-bdb.h) to raise the limit. Change the
> MDB_INDICES (or BDB_INDICES) definition.
> Congratulations, no one else has hit this limit in back-bdb in the past 12
> years. Seems likely to me that you're indexing too much, but there's not
> enough information here to judge.

Ok, thanks for that information. I will try to increase it.

But it's weird that there is no error with bdb on startup. I looked at my back-bdb.h and it has 128.
I'm definitely over this number.

You are right, some are too much and I could maybe remove a few indexes. Some defaults.
But our own schema extension is quite long and many of those attributes are used in searches from the various apps.
Normally I also only added an index where I saw the candidate message in the log.

So this is then also no bug and we can close it.
Sorry for being to fast with an ITS.