Description of problem: In certain IPA envs, we can see ipa-replica-install failing because of on line init failing due to entries bigger than 2Mb. Version-Release number of selected component (if applicable): observed in 389-ds-base-1.2.11.15-50 But in master and 1.3 versions, default is still to 2Mb: git branch 389-ds-base-1.2.11 * master grep DEFAULT_MAXBERSIZE ./ldap/servers/slapd/libglobs.c #define DEFAULT_MAXBERSIZE 2097152 The biggest issue with this bug is that we cannot set the maxbersize to continue since the ipa-replica-install is creating instance from scratch + re-init. Workaround: Edit file /usr/share/dirsrv/data/template-dse.ldif before replica install and a line nsslapd-maxbersize: <new size> under cn-config. Like: dn: cn=config nsslapd-maxbersize: <new size> cn: config
Comment by Ludwig: if limit can be raised or ignored under specidfic conditions, eg in replication.
Ack, one minor thing. If this is only for openldap, you could put that entire code block inside the #if/#endif
Replying to [comment:3 mreynolds]:
That's true. Thanks, Mark! I'm modifying the patch as you suggested...
git patch file (master) -- revised based on the comments by Mark (Thanks!!) 0001-Ticket-48326-RFE-it-could-be-nice-to-have-nsslapd-ma.patch
git patch file (master) -- CI test 0001-Ticket-48326-CI-test-added-test-cases-for-ticket-483.patch
attachment 0001-Ticket-48326-Move-CI-test-to-config-test-suite-and-r.patch
A good idea! Thanks, Simon!
To ssh://git.fedorahosted.org/git/389/ds.git e218a18..db116a4 master -> master
commit db116a4 Author: Simon Pichugin spichugi@redhat.com Date: Fri Jul 3 15:52:23 2015 +0200
Metadata Update from @nhosoi: - Issue assigned to nhosoi - Issue set to the milestone: 1.3.5.0
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/1657
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Fixed)
Log in to comment on this ticket.