We restarted all systems and now it's running perfect. So where is the problem?
Am 14.04.21 um 07:45 schrieb Ulrich Windl: >>>> Quanah Gibson-Mount <[email protected]> schrieb am 13.04.2021 um 18:35 in > Nachricht <04ACA14B0F04DF4022F94CA2@[192.168.1.156]>: > >> >> ‑‑On Sunday, April 11, 2021 3:44 PM +0200 Stefan Kania >> <stefan@kania‑online.de> wrote: >> >>> Hello, >>> >>> I just try to set up the replication for cn=config using the example >>> from the documentation: >>> https://www.openldap.org/doc/admin24/replication.html >>> >>> I have 3 Provider in an MMR with delta‑syncrpl. Delta‑syncrepl is >>> working fine I can add and change objects from all three providers. >>> >>> Then I set up the replication for cn=config. Here are the changes I made >>> on all three providers: >>> ‑‑‑‑‑‑‑‑‑‑‑ >>> olcServerID: 1 ldap://hm‑01.example.net >>> olcServerID: 2 ldap://hm‑02.example.net >>> olcServerID: 3 ldap://hm‑03.example.net >>> >>> Before setting up the replication for cn=config I checked that the >>> configuration on all three providers are the same. >> >> I've stated repeatedly on this list that cn=config replication is not safe >> with OpenLDAP 2.4 and portions of it do not work. > > As we are doing exactly that without any problem so far, could you please > repeat what is unsafe? > >> >> Additionally, you'd need to provide what the logs show when making the >> change, as far as replication is concerned, to discern why it's failing. >> It could be to one of the issues already fixed for OpenLDAP 2.5, but >> without log info, there's no knowing. >> >> Regards, >> Quanah >> >> >> ‑‑ >> >> Quanah Gibson‑Mount >> Product Architect >> Symas Corporation >> Packaged, certified, and supported LDAP solutions powered by OpenLDAP: >> <http://www.symas.com> > > > -- Stefan Kania Landweg 13 25693 St. Michaelisdonn Signieren jeder E-Mail hilft Spam zu reduzieren und schützt Ihre Privatsphäre. Ein kostenfreies Zertifikat erhalten Sie unter https://www.dgn.de/dgncert/index.html
