Le 19/07/2017 à 17:43, Jon C Kidder a écrit :
I’ve got an LSC 2.1.3 implementation running an asynchronous job
against an OpenLDAP 2.4.44 directory. I am continuously encountering
scenarios where LSC is not being triggered by a change in OpenLDAP. I
don’t suspect the OpenLDAP server because this is a distributed
directory. sync/repl functions as expected and changes are
immediately propagated to all nodes. Any thoughts on where I need to
look or steps I can take to improve the responsiveness and reliability
of the asynchronous sync job?
Hi,
if LSC looses the connection to the source, it should stop and log an error.
You can check the status of the async task with check_lsc_remote.pl script.
Anyway, I suggest to restart the async connector at least each day in
order to force a full sync.
--
Clément OUDOT
Consultant en logiciels libres, Expert infrastructure et sécurité
Savoir-faire Linux
137 boulevard de Magenta - 75010 PARIS
Blog: http://sflx.ca/coudot
_______________________________________________________________
Ldap Synchronization Connector (LSC) - http://lsc-project.org
lsc-users mailing list
[email protected]
https://lists.lsc-project.org/cgi-bin/mailman/listinfo/lsc-users
