Hi Ulrich Both the servers are set up as master as well as consumer so that sync works in both directions. So the sync setup is like "A -> B", and when A fails B is updated and the expectation is that "B -> A" should work because a multi master setup is already in place. Let me know based on the attached configuration files if my assumption is correct or not.
Also Add data works when A fails and B is updated then sync "B -> A"works fine. After Delete data sync does not work when A fails and data is deleted from B. Once A comes back both databases have data which was deleted on B. Thanks Rahul On Tue, Jun 23, 2020 at 8:11 AM Ulrich Windl < [email protected]> wrote: > >>> Quanah Gibson-Mount <[email protected]> schrieb am 22.06.2020 um 18:09 > in > Nachricht > <13855_1592842197_5EF0D7D5_13855_226_1_A497B27F9A5328340A4CDBAC@ > [192.168.1.144]> > > > > > > ‑‑On Monday, June 22, 2020 3:08 PM +0000 Kumar Rahul > > <[email protected]> wrote: > > > >> Hi Quanah > >> > >> Thank you for all the help so far. I am still seeing the original > >> issue reported. Let me know if you need fresh set of configuration > >> information. > > > > I've told you repeatedly what is necessary, you haven't provided it. > > > > To re‑iterate: > > > > Full configuration of both servers, not config snippets or LDAP modify > > change code. > > Actually (if I read the description correctly the sync setup is like "A -> > B", > and when A fails B is updated and expectation is that "B -> A" will work > automagically (which is not true IMHO). Then multi-master setup is needed. > > > > > Regards, > > Quanah > > > > > > > > ‑‑ > > > > Quanah Gibson‑Mount > > Product Architect > > Symas Corporation > > Packaged, certified, and supported LDAP solutions powered by OpenLDAP: > > <http://www.symas.com> > > > >
S2config.ldif
Description: Binary data
S1config.ldif
Description: Binary data
