[Date Prev][Date Next] [Chronological] [Thread] [Top]

[Openldap 2.4.16] Is it possible to force synchronization: files log.xxxx not treated after a crash


I am using openldap 2.4.16 in a multi-master configuration mode (2 servers on linux system - LFS).
My problem is that some data are not synchronised on one of my server and I have some "log.xxxx" files in my var/openldap-data/ directory.
I think it is normal as these files are the synchronisation files and are not suppress until the synchronisation is validated (in my DB_CONFIG I have set the parameter:
set_flags�������������� DB_LOG_AUTOREMOVE).
The replication is at that moment working (I have made some tests) but I know that the ldap process has crashed as I found some logs:

Aug 20 10:08:40 bpldap02s kernel: slapd[19783]: segfault at 0 ip 080926f3 sp ad5a03a0 error 4 in slapd[8048000+1b9000]

But I was on holidays while it happens so I don't have more information on how it happens.

Is there something I can do to force the files to be treated? I have read some articles about "slurpd" but I am not sure it can be used with my version.

For the moment I only see the solution: "slapcat -> ldapadd" to synchronize both instances but if you have any other solution...

Thank you for your help.