Hello,

Thank you for the quick response!

"cn=config is deterministic” what does it mean? Could you please explain us the benefits in this case.

About this:
4. You never tried:

database section
rwm overlay
refint overlay

I’ve tried and it does not work. 

---------
Maksim Saroka
DevOps/System Administrator

On Oct 10, 2023, at 10:48 PM, Quanah Gibson-Mount <quanah@fast-mail.org> wrote:



--On Tuesday, October 10, 2023 4:43 PM +0200 Maksim Saroka <msaroka@exadel.com> wrote:



Hello,

We have a strange situation with refint and rwm overlays on ldap
replica. Looks like those overlays depend on each other and on position
in the slapd.conf file regarding database section. However refint
overlay is working in any position if rwm overlay is not specified. Here
are the examples with positions in the file:

Refint overlay work if:
1.  
   rwm overlay section   
   database section   
   refint overlay section

Refint overlay does not work if:
1. 
   database section
   refint overlay section
   rwm overlay section
2. 
   rwm overlay section   
   refint overlay section
   database section

Could you please explain to us the root cause of that as I can't find any
explanation in the docs.


Hi,

A couple notes:

1. You really should use cn=config and not slapd.conf, as cn=config is deterministic.
2. In the first case above, "rwm" is probably ending up as a global overlay
3. In the third case above, "rwm" and "refint" are probably both ending up as global overlays
4. You never tried:

database section
rwm overlay
refint overlay

Finally, module load order can matter in certain circumstances, particularly with overlays that interact with one another.  One reason why syncprov (in a replicated environment) should always be the first overlay in a database section.

--Quanah





CONFIDENTIALITY NOTICE: This email and files attached to it are confidential. If you are not the intended recipient you are hereby notified that using, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error please notify the sender and delete this email.