On Mon, Aug 21, 2017 at 1:11 AM, Clément OUDOT < [email protected]> wrote:
> > > Le 21/08/2017 à 04:20, David Erickson a écrit : > >> Hi all- >> > > Hello David, > >> I'd like to run LSC in async mode listening for updates and acting on >> them, as opposed to polling, however a couple things I've noticed: >> >> -Clean doesn't get run at all while in async mode, why? Can I enable it? >> > > No, clean phase must be run with option -c. Async phase is just for sync > (-a instead of -s). Bummer, it would be really nice if the async phase could also optionally run a clean periodically as well, so the user doesn't have to set up a separate process to do that. > > > -I have OpenLDAP 2.4.28, and my async ldap source service configured, but >> when I watch debug logging, it looks like it is still polling every 10 >> seconds as opposed to being triggered based on changes, why? >> > > > Are you to have syncprov overlay configured on OpenLDAP? Note also that > OpenLDAP 2.4.28 is really old, you should use a more recent version. Probably not, will check into that. > > > >> Also, when I run "sudo lsc -t 1 -s all -c all", I'm seeing the following >> errors printed in the log: >> >> Aug 20 15:38:45 - ERROR - There is no future associated with operation >> message ID 15, perhaps the operation would have been completed >> Aug 20 15:38:45 - ERROR - There is no future associated with operation >> message ID 15, perhaps the operation would have been completed >> Aug 20 15:38:45 - ERROR - There is no future associated with operation >> message ID 20, perhaps the operation would have been completed >> Aug 20 15:38:45 - ERROR - There is no future associated with operation >> message ID 20, perhaps the operation would have been completed >> >> Can these be ignored? And if so, are they going to be fixed? I'd like >> to turn my logging to error only and have it email me in the event of an >> error, and if these are being printed on every run that won't work. >> >> > > Don't know, try to use a more recent version of OpenLDAP to see if these > messages are still present. > It looks like I was getting these errors while running the asyncProvider but executing the sync version of lsc, they went away when I changed to a sync provider. Thanks, David
_______________________________________________________________ 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
