Migrating to OpenLDAP 2.5 and MDB I hit the default 10MB limit (when trying to import a 6.8MB LDIF). Seeking how to extend the size online, I found:
maxsize <bytes>https://manpages.debian.org/testing/slapd/slapd-mdb.5.en.html#maxsize Specify the maximum size of the database in bytes. A memory map of this size is allocated at startup time and the database will not be allowed to grow beyond this size. The default is 10485760 bytes. This setting may be changed upward if the configured limit needs to be increased.
However it's completely non-obvious that the name for cn=config is "olcDbMaxSize" (and not "olcMaxssize").
(The final MDB file size was about 23MB, including the indices)
Kind regards, Ulrich Windl
--On Friday, February 21, 2025 11:03 AM +0000 "Windl, Ulrich" u.windl@ukr.de wrote:
Migrating to OpenLDAP 2.5 and MDB I hit the default 10MB limit (when trying to import a 6.8MB LDIF).
Seeking how to extend the size online, I found:
maxsize <bytes>
Specify the maximum size of the database in bytes. A memory map of this size is allocated at startup time and the database will not be allowed to grow beyond this size. The default is 10485760 bytes. This setting may be changed upward if the configured limit needs to be increased.
However it's completely non-obvious that the name for cn=config is "olcDbMaxSize" (and not "olcMaxssize").
There's an ITS on adding cn=config information to the manual pages, patches welcome.
--Quanah
Windl, Ulrich wrote:
Migrating to OpenLDAP 2.5 and MDB I hit the default 10MB limit (when trying to import a 6.8MB LDIF).
Seeking how to extend the size online, I found:
*maxsize*/ <bytes>/ https://manpages.debian.org/testing/slapd/slapd-mdb.5.en.html#maxsize
Specify the maximum size of the database in bytes. A memory map of this size is allocated at startup time and the database will not be allowed to grow beyond this size. The default is 10485760 bytes. This setting may be changed upward if the configured limit needs to be increased.
However its completely non-obvious that the name for cn=config is olcDbMaxSize (and not olcMaxssize).
The schema is self-documenting. Just read the olcMdbConfig objectclass and the descriptions of all of its attributes.
e.g. `ldapsearch -H ldap://xxx -b cn=schema,cn=config -s base`
--On Friday, February 28, 2025 4:03 PM +0000 Howard Chu hyc@symas.com wrote:
Windl, Ulrich wrote:
Migrating to OpenLDAP 2.5 and MDB I hit the default 10MB limit (when trying to import a 6.8MB LDIF).
Seeking how to extend the size online, I found:
*maxsize*/ <bytes>/ https://manpages.debian.org/testing/slapd/slapd-mdb.5.en.html#maxsize
Specify the maximum size of the database in bytes. A memory map of this size is allocated at startup time and the database will not be allowed to grow beyond this size. The default is 10485760 bytes. This setting may be changed upward if the configured limit needs to be increased.
However it's completely non-obvious that the name for cn=config is "olcDbMaxSize" (and not "olcMaxssize").
The schema is self-documenting. Just read the olcMdbConfig objectclass and the descriptions of all of its attributes.
e.g. `ldapsearch -H ldap://xxx -b cn=schema,cn=config -s base`
I would add that *database specific* configuration options are prefixed with olcDb.. because they are DB specific and not general.
--Quanah
Howard,
You are right that one can read every thing from the schema, but given there are manual pages, it would not be too much work to put the most essential facts there. I know that developers don't like to write manual pages, and it can be a frustrating experience to realize that most users won't read them. Still I believe in manual pages 😉
Kind regards, Ulrich Windl
-----Original Message----- From: Howard Chu hyc@symas.com Sent: Friday, February 28, 2025 5:03 PM To: Windl, Ulrich u.windl@ukr.de; openldap-technical@openldap.org Subject: [EXT] Re: manual page slapd-mdb.5 and "maxsize"
Windl, Ulrich wrote:
Migrating to OpenLDAP 2.5 and MDB I hit the default 10MB limit (when
trying to import a 6.8MB LDIF).
Seeking how to extend the size online, I found:
*maxsize*/ <bytes>/ <https://manpages.debian.org/testing/slapd/slapd-
mdb.5.en.html#maxsize>
Specify the maximum size of the database in bytes. A memory map of this
size is allocated at startup time and the database will not be allowed to grow beyond
this size. The default is 10485760 bytes. This setting may be changed
upward if the configured limit needs to be increased.
However it’s completely non-obvious that the name for cn=config is
“olcDbMaxSize” (and not “olcMaxssize”).
The schema is self-documenting. Just read the olcMdbConfig objectclass and the descriptions of all of its attributes.
e.g. `ldapsearch -H ldap://xxx -b cn=schema,cn=config -s base`
-- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun BLOCKEDhighlandsun[.]com/hyc/BLOCKED Chief Architect, OpenLDAP http://www.openldap.org/project/
On Mon, Mar 03, 2025 at 10:48:48AM +0000, Windl, Ulrich wrote:
Howard,
You are right that one can read every thing from the schema, but given there are manual pages, it would not be too much work to put the most essential facts there. I know that developers don't like to write manual pages, and it can be a frustrating experience to realize that most users won't read them. Still I believe in manual pages 😉
Hi Ulrich, if you have a suggestion how this could be handled and unblock the relevant ITS[0], pick a manpage and show us please. This project relies on community to contribute and since you have opinions, it would be nice if they turned constructive at some point ;)
[0]. https://bugs.openldap.org/show_bug.cgi?id=7335
Thanks,
Windl, Ulrich wrote:
Howard,
You are right that one can read every thing from the schema, but given there are manual pages, it would not be too much work to put the most essential facts there. I know that developers don't like to write manual pages, and it can be a frustrating experience to realize that most users won't read them. Still I believe in manual pages 😉
As a developer I believe in manual pages too. I also believe in only writing what is necessary and sufficient, which is what we have done for all of the code we have written. If you want anything further, contribute it yourself. It surely doesn't take specialized developer skills to do so.
Kind regards, Ulrich Windl
-----Original Message----- From: Howard Chu hyc@symas.com Sent: Friday, February 28, 2025 5:03 PM To: Windl, Ulrich u.windl@ukr.de; openldap-technical@openldap.org Subject: [EXT] Re: manual page slapd-mdb.5 and "maxsize"
Windl, Ulrich wrote:
Migrating to OpenLDAP 2.5 and MDB I hit the default 10MB limit (when
trying to import a 6.8MB LDIF).
Seeking how to extend the size online, I found:
*maxsize*/ <bytes>/ <https://manpages.debian.org/testing/slapd/slapd-
mdb.5.en.html#maxsize>
Specify the maximum size of the database in bytes. A memory map of this
size is allocated at startup time and the database will not be allowed to grow beyond
this size. The default is 10485760 bytes. This setting may be changed
upward if the configured limit needs to be increased.
However it’s completely non-obvious that the name for cn=config is
“olcDbMaxSize” (and not “olcMaxssize”).
The schema is self-documenting. Just read the olcMdbConfig objectclass and the descriptions of all of its attributes.
e.g. `ldapsearch -H ldap://xxx -b cn=schema,cn=config -s base`
-- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun BLOCKEDhighlandsun[.]com/hyc/BLOCKED Chief Architect, OpenLDAP http://www.openldap.org/project/
openldap-technical@openldap.org
-
Howard Chu -
Ondřej Kuzník -
Quanah Gibson-Mount -
Windl, Ulrich