Why do you have two csn from 2019 and one from 2023?

Am 27.04.23 um 19:12 schrieb Benjamin Renard:
Hello,

Le 25/04/2023 à 18:48, Quanah Gibson-Mount a écrit :


--On Tuesday, April 25, 2023 7:40 PM +0200 Benjamin Renard <bren...@easter-eggs.com> wrote:
OK, thanks for your advice. I will try to update it on the preprod to be
sure I will be able to manage any upgrade issue.

You may find this helpful as well:

<https://repo.symas.com/soldap2.5/upgrading/>

One of the largest changes that will impact you initially is the removal of the ppolicy schema from the schema tree (it's now built into the ppolicy overlay directly).

--Quanah

After successfully upgrade the preprod in 2.5, I try this upgrade in the same way on prod master and slave hosts. I had to fallback in 2.4 because of a strange bug/error : slapd stop it self/crash with the following message in logs :

Apr 27 18:45:35 gavotte slapd[1086351]: conn=1224 op=0 BIND dn="uid=syncrepl,ou=sysaccounts,o=example" method=128 Apr 27 18:45:35 gavotte slapd[1086351]: conn=1224 op=0 BIND dn="uid=syncrepl,ou=sysaccounts,o=example" mech=SIMPLE bind_ssf=0 ssf=256 Apr 27 18:45:35 gavotte slapd[1086351]: conn=1224 op=0 RESULT tag=97 err=0 qtime=0.000036 etime=0.000164 text= Apr 27 18:45:35 gavotte slapd[1086351]: conn=1224 op=1 SRCH base="o=example" scope=2 deref=0 filter="(objectClass=*)"
Apr 27 18:45:35 gavotte slapd[1086351]: conn=1224 op=1 SRCH attr=* +
Apr 27 18:45:35 gavotte slapd[1086351]: conn=1224 op=1 syncprov_op_search: got a persistent search with a cookie=rid=000,csn=20190213173033.952331Z#000000#000#000000;20230427155638.609257Z#000000#001#000000;20190916120217.913828Z#000000#003#000000 Apr 27 18:45:35 gavotte slapd[1086351]: conn=1224 op=1 syncprov_findbase: searching Apr 27 18:45:35 gavotte slapd[1086351]: conn=1224 op=1 syncprov_op_search: registered persistent search
Apr 27 18:45:35 gavotte slapd[1086662]: Stopping OpenLDAP: slapd.

It seem related with syncprov and in fact, in preprod, I have no slave/replication.

My syncrepl configuration is quite simple :

On master:

dn: olcOverlay={3}syncprov,olcDatabase={1}mdb,cn=config
objectClass: olcOverlayConfig
objectClass: olcSyncProvConfig
objectClass: top
olcOverlay: {3}syncprov
olcSpNoPresent: TRUE
olcSpReloadHint: TRUE

On slave:

dn: olcDatabase={1}mdb,cn=config
[...]
olcSyncrepl: {0}rid=0 provider=ldaps://ldap-master
   bindmethod=simple timeout=0 network-timeout=0
   binddn="uid=syncrepl,ou=sysaccounts,o=example" credentials="secret"
   keepalive=0:0:0 filter="(objectclass=*)" searchbase="o=example"
   scope=sub schemachecking=off type=refreshAndPersist retry="5 5 300 +"
olcUpdateRef: ldaps://ldap.enercoop.org

Do you have idea of what could produce these crashs/stops ?

Thanks !




Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to