Hello
My slapd server suddenly refuse to generate an LDIF file though th slapcat command.
It is asking to increase the size of the id2entry.bdb database.
I restart slapd and it works fine again but I would like to know what happened.
Is there any configurable parameter that I would be able to write down into DB_CONFIG file to increase the size of this database ? I haven't found any precise documentation about this when googling about this.
Or is it totally anything else ?
see below the actual result of the db_stat command applied to this base :
ldap# db_stat-4.6 -d id2entry.bdb Wed Jul 4 09:23:56 2012 Local time 53162 Btree magic number 9 Btree version number Little-endian Byte order Flags 2 Minimum keys per-page 16384 Underlying database page size 4079 Overflow key/data size 3 Number of levels in the tree 18735 Number of unique keys in the tree 18735 Number of data items in the tree 4 Number of tree internal pages 28130 Number of bytes free in tree internal pages (57% ff) 1694 Number of tree leaf pages 3940820 Number of bytes free in tree leaf pages (85% ff) 0 Number of tree duplicate pages 0 Number of bytes free in tree duplicate pages (0% ff) 7 Number of tree overflow pages 67789 Number of bytes free in tree overflow pages (40% ff) 0 Number of empty pages 0 Number of pages on the free list
Thank you very much
--On Wednesday, July 04, 2012 9:28 AM +0200 Frank Bonnet f.bonnet@esiee.fr wrote:
Hello
My slapd server suddenly refuse to generate an LDIF file though th slapcat command.
It is asking to increase the size of the id2entry.bdb database.
I restart slapd and it works fine again but I would like to know what happened.
Is there any configurable parameter that I would be able to write down into DB_CONFIG file to increase the size of this database ? I haven't found any precise documentation about this when googling about this.
It is unfortunate you didn't supply the actual error you encountered, because what you've written makes no sense. BDB does not ask you to increase the size of BDB files, it does that itself automatically. The only thing you generally configure is the size of the database *cache* for BDB, but that doesn't limit the total size of the DB. The only thing that does that is actual available disk space.
--Quanah
--
Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration
On 07/04/2012 10:00 AM, Quanah Gibson-Mount wrote:
--On Wednesday, July 04, 2012 9:28 AM +0200 Frank Bonnet f.bonnet@esiee.fr wrote:
Hello
My slapd server suddenly refuse to generate an LDIF file though th slapcat command.
It is asking to increase the size of the id2entry.bdb database.
I restart slapd and it works fine again but I would like to know what happened.
Is there any configurable parameter that I would be able to write down into DB_CONFIG file to increase the size of this database ? I haven't found any precise documentation about this when googling about this.
It is unfortunate you didn't supply the actual error you encountered, because what you've written makes no sense. BDB does not ask you to increase the size of BDB files, it does that itself automatically. The only thing you generally configure is the size of the database *cache* for BDB, but that doesn't limit the total size of the DB. The only thing that does that is actual available disk space.
--Quanah
--
Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc.
Zimbra :: the leader in open source messaging and collaboration
the message contains the following
Logging region out of memory; you may need to increase its size
On Wed, Jul 04, 2012 at 11:27:44AM +0200, Frank Bonnet wrote:
It is asking to increase the size of the id2entry.bdb database.
the message contains the following
Logging region out of memory; you may need to increase its size
So why did you ask about id2entry.bdb size? Is there more to this message that you have not posted? You will get more help from the list if you provide full information.
What is in your DB_CONFIG file? Please post the whole file. Do you have unusually large entries or attributes?
Which backend database are you using? It would be useful to post the slapd configuration (less any passwords of course).
What version of OpenLDAP are you using? You appear to be using version 4.6 of the Berkeley Database libraries.
Andrew
--On Wednesday, July 04, 2012 11:27 AM +0200 Frank Bonnet f.bonnet@esiee.fr wrote:
the message contains the following
Logging region out of memory; you may need to increase its size
So clearly this says nothing about id2entry.bdb. I'm not sure how you came to the conclusion then that you need to change anything in relation to that file. Clearly, the issue is with the logging subsystem.
Have you configured the BDB logging system in DB_CONFIG? Generally the following has always worked for me:
set_lg_regionmax 262144 set_lg_max 10485760 set_lg_bsize 2097152
--Quanah
--
Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration
On 07/05/2012 10:09 PM, Quanah Gibson-Mount wrote:
--On Wednesday, July 04, 2012 11:27 AM +0200 Frank Bonnet f.bonnet@esiee.fr wrote:
the message contains the following
Logging region out of memory; you may need to increase its size
So clearly this says nothing about id2entry.bdb. I'm not sure how you came to the conclusion then that you need to change anything in relation to that file. Clearly, the issue is with the logging subsystem.
Have you configured the BDB logging system in DB_CONFIG? Generally the following has always worked for me:
set_lg_regionmax 262144 set_lg_max 10485760 set_lg_bsize 2097152
--Quanah
--
Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc.
Zimbra :: the leader in open source messaging and collaboration
OK I'm going to try this thanks a lot !
On 07/05/2012 10:09 PM, Quanah Gibson-Mount wrote:
--On Wednesday, July 04, 2012 11:27 AM +0200 Frank Bonnet f.bonnet@esiee.fr wrote:
the message contains the following
Logging region out of memory; you may need to increase its size
So clearly this says nothing about id2entry.bdb. I'm not sure how you came to the conclusion then that you need to change anything in relation to that file. Clearly, the issue is with the logging subsystem.
Have you configured the BDB logging system in DB_CONFIG? Generally the following has always worked for me:
set_lg_regionmax 262144 set_lg_max 10485760 set_lg_bsize 2097152
fortunately I have a test server where I can check any modification before applying on the production server.
When I restart slapd I have this in debug.log file
Jul 6 09:49:44 ldap3 slapd[95890]: bdb_db_open: DB_CONFIG for suffix "dc=esiee,dc=fr" has changed. Jul 6 09:49:44 ldap3 slapd[95890]: Performing database recovery to activate new settings. Jul 6 09:49:45 ldap3 slapd[95890]: slapd starting
--On Friday, July 06, 2012 10:24 AM +0200 Frank Bonnet f.bonnet@esiee.fr wrote:
Jul 6 09:49:44 ldap3 slapd[95890]: bdb_db_open: DB_CONFIG for suffix "dc=esiee,dc=fr" has changed. Jul 6 09:49:44 ldap3 slapd[95890]: Performing database recovery to activate new settings. Jul 6 09:49:45 ldap3 slapd[95890]: slapd starting
That is exactly what you want to see. Slapd noticed that DB_CONFIG changed, so it is running database recovery to apply the new changes.
--Quanah
--
Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration
CYBERDROID Inc. Le 06/07/2012 16:45, Quanah Gibson-Mount a écrit :
--On Friday, July 06, 2012 10:24 AM +0200 Frank Bonnet f.bonnet@esiee.fr wrote:
Jul 6 09:49:44 ldap3 slapd[95890]: bdb_db_open: DB_CONFIG for suffix "dc=esiee,dc=fr" has changed. Jul 6 09:49:44 ldap3 slapd[95890]: Performing database recovery to activate new settings. Jul 6 09:49:45 ldap3 slapd[95890]: slapd starting
That is exactly what you want to see. Slapd noticed that DB_CONFIG changed, so it is running database recovery to apply the new changes.
--Quanah
--
Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc.
Zimbra :: the leader in open source messaging and collaboration
ok thank you !
Le 06/07/2012 16:45, Quanah Gibson-Mount a écrit :
Jul 6 09:49:44 ldap3 slapd[95890]: bdb_db_open: DB_CONFIG for suffix "dc=esiee,dc=fr" has changed. Jul 6 09:49:44 ldap3 slapd[95890]: Performing database recovery to activate new settings. Jul 6 09:49:45 ldap3 slapd[95890]: slapd starting
That is exactly what you want to see. Slapd noticed that DB_CONFIG changed, so it is running database recovery to apply the new changes.
I was convinced than DB_CONFIG settings could not get changed after the initial database creation. Did that change at some point ? Also, is it true for all settings, or only a subset of available ones ?
Guillaume Rousse wrote:
Le 06/07/2012 16:45, Quanah Gibson-Mount a écrit :
Jul 6 09:49:44 ldap3 slapd[95890]: bdb_db_open: DB_CONFIG for suffix "dc=esiee,dc=fr" has changed. Jul 6 09:49:44 ldap3 slapd[95890]: Performing database recovery to activate new settings. Jul 6 09:49:45 ldap3 slapd[95890]: slapd starting
That is exactly what you want to see. Slapd noticed that DB_CONFIG changed, so it is running database recovery to apply the new changes.
I was convinced than DB_CONFIG settings could not get changed after the initial database creation.
Wrong.
Did that change at some point ? Also, is it true for all settings, or only a subset of available ones ?
All settings can be changed; that has always been the case. In the past you needed to manually run db_recover to make the changes take effect. In 2.4 back-bdb/hdb detects the change and does the recovery automatically.
--On Saturday, July 07, 2012 5:14 AM -0700 Howard Chu hyc@symas.com wrote:
Guillaume Rousse wrote:
Le 06/07/2012 16:45, Quanah Gibson-Mount a écrit :
Jul 6 09:49:44 ldap3 slapd[95890]: bdb_db_open: DB_CONFIG for suffix "dc=esiee,dc=fr" has changed. Jul 6 09:49:44 ldap3 slapd[95890]: Performing database recovery to activate new settings. Jul 6 09:49:45 ldap3 slapd[95890]: slapd starting
That is exactly what you want to see. Slapd noticed that DB_CONFIG changed, so it is running database recovery to apply the new changes.
I was convinced than DB_CONFIG settings could not get changed after the initial database creation.
Wrong.
Did that change at some point ? Also, is it true for all settings, or only a subset of available ones ?
All settings can be changed; that has always been the case. In the past you needed to manually run db_recover to make the changes take effect. In 2.4 back-bdb/hdb detects the change and does the recovery automatically.
This has been the case since OpenLDAP 2.3, IIRC ;)
--Quanah
--
Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration
openldap-technical@openldap.org
-
Andrew Findlay -
Frank Bonnet -
Guillaume Rousse -
Howard Chu -
Quanah Gibson-Mount