Hi, Deactivated pageSize ( -1) with same result (no updates, no error).
The directory server was freshly restarted before sync. You willl find bellow the 389 DS traces : Regards Jean-Marc BAJET Centre informatique - Cirti DSI - Sous-Direction Architecture Technique CET Sécurité Tél. : 02 40 68 38 80 2 rue de Coulongé CS 61911 44319 NANTES Cedex 03 [email protected] Contribuons au respect de l'environnement, n'imprimez ce courriel qu'en cas de nécessité et ayez le réflexe recto-verso De : Raphaël Ouazana-Sustowski <[email protected]> A : Jean-Marc BAJET <[email protected]>, Cc : [email protected] Date : 17/09/2015 14:36 Objet : Re: [lsc-users] Lsc 2.1.3 - Can't update changes Hi, Can you try to remove pagesize configuration? You can deactivate pagesize providing value -1: <pageSize>-1</pageSize> Do you have any log on 389DS side? Regards, Raphaël Ouazana. Le 2015-09-17 14:15, Jean-Marc BAJET a écrit : > Hello, > > Sorry but this post is related to the post of 09/01/2015 "Lsc 2.1.3 - > Can't update changes" where I attached lsc.xml. I re-attached it > anyway. > I tried the minimal logback which does not produce more info (see > below, : no error). Changes are still not propagated. > > Thanks > > Console output : > > 14:04:07,409 |-INFO in ch.qos.logback.classic.LoggerContext[default] - > Found resource [logback.xml] at [file:/etc/lsc/sesame/logback.xml] > 14:04:07,414 |-WARN in ch.qos.logback.classic.LoggerContext[default] - > Resource [logback.xml] occurs multiple times on the classpath. > 14:04:07,414 |-WARN in ch.qos.logback.classic.LoggerContext[default] - > Resource [logback.xml] occurs at [file:/etc/lsc/sesame/logback.xml] > 14:04:07,414 |-WARN in ch.qos.logback.classic.LoggerContext[default] - > Resource [logback.xml] occurs at > [jar:file:/usr/lib/lsc/lsc-core-2.1.3.jar!/logback.xml] > 14:04:07,604 |-INFO in > ch.qos.logback.classic.joran.action.ConfigurationAction - debug > attribute not set > 14:04:07,681 |-INFO in ch.qos.logback.core.joran.action.AppenderAction > - About to instantiate appender of type > [ch.qos.logback.core.ConsoleAppender] > 14:04:07,705 |-INFO in ch.qos.logback.core.joran.action.AppenderAction > - Naming appender as [CONSOLE] > 14:04:07,756 |-INFO in > ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Pushing > component [encoder] on top of the object stack. > 14:04:07,796 |-INFO in > ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Pushing > component [layout] on top of the object stack. > 14:04:07,946 |-INFO in > ch.qos.logback.classic.joran.action.LoggerAction - Setting additivity > of logger [communicationLogger] to true > 14:04:07,946 |-INFO in > ch.qos.logback.core.joran.action.AppenderRefAction - Attaching > appender named [CONSOLE] to Logger[communicationLogger] > 14:04:07,979 |-INFO in > ch.qos.logback.classic.joran.action.LoggerAction - Setting level of > logger [org.apache] to ERROR > 14:04:07,979 |-INFO in > ch.qos.logback.classic.joran.action.LoggerAction - Setting additivity > of logger [org.apache] to true > 14:04:07,979 |-INFO in > ch.qos.logback.core.joran.action.AppenderRefAction - Attaching > appender named [CONSOLE] to Logger[org.apache] > 14:04:07,979 |-INFO in > ch.qos.logback.classic.joran.action.LoggerAction - Setting additivity > of logger [poolLogger] to true > 14:04:07,979 |-INFO in > ch.qos.logback.core.joran.action.AppenderRefAction - Attaching > appender named [CONSOLE] to Logger[poolLogger] > 14:04:07,979 |-INFO in > ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level > of ROOT logger to DEBUG > 14:04:07,979 |-INFO in > ch.qos.logback.core.joran.action.AppenderRefAction - Attaching > appender named [CONSOLE] to Logger[ROOT] > > sept. 17 14:04:08 - > DEBUG - Loading XML configuration from: /etc/lsc/sesame/lsc.xml > sept. 17 14:04:08 - > DEBUG - going to scan these urls: > jar:file:/usr/lib/lsc/lsc-core-2.1.3.jar!/ > sept. 17 14:04:09 - > INFO - Reflections took 206 ms to scan 1 urls, producing 55 keys and > 115 values > sept. 17 14:04:09 - > DEBUG - Importing XML schema file: schemas/lsc-core-2.1.xsd > sept. 17 14:04:09 - > INFO - Logging configuration successfully loaded from > /etc/lsc/sesame/logback.xml > sept. 17 14:04:09 - > INFO - LSC configuration successfully loaded from /etc/lsc/sesame/ > sept. 17 14:04:09 - > INFO - Connecting to LDAP server ldap://localhost:10389/o=mrecouv as > cn=Directory Manager > sept. 17 14:04:09 - > INFO - Connecting to LDAP server > ldap://localhost/ou=Recouvrement,dc=recouv as cn=Directory Manager > sept. 17 14:04:10 - > INFO - Starting sync for ANAIS_USERS_MAIL > sept. 17 14:04:21 - > INFO - All entries: 188, to modify entries: 0, successfully modified > entries: 0, errors: 0 > > De : [email protected] > A : [email protected], > Date : 17/09/2015 12:00 > Objet : lsc-users Digest, Vol 68, Issue 10 > Envoyé par : [email protected] > > ------------------------- > > Send lsc-users mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.lsc-project.org/listinfo/lsc-users [1] > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of lsc-users digest..." > > Today's Topics: > > 1. Re: Lsc 2.1.3 - Can't update changes (Cl?ment OUDOT) > 2. Re: Problem with launching LSC (Cl?ment OUDOT) > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 17 Sep 2015 09:41:41 +0200 > From: Cl?ment OUDOT <[email protected]> > Subject: Re: [lsc-users] Lsc 2.1.3 - Can't update changes > To: [email protected] > Message-ID: <[email protected]> > Content-Type: text/plain; charset="windows-1252"; Format="flowed" > > Le 16/09/2015 15:30, Jean-Marc BAJET a ?crit : > > Hello, > > > > Thanks for your quick answer, I tried : > > > > Lsc 2.1.3 with the same script : > > - Sync from 389 Directory Server 1.2.8 to ODJ 2.6 : KO - only new > > entries are added to the destination, changes are not updated at > all > > - Sync from 389 Directory Server 1.3.3 to ODJ 2.6 : KO - only new > > entries are added to the destination, changes are not updated at > all > > - Sync from ODJ 2.6 to ODJ 2.6 : OK - sync works successfully, > > including changes. > > > > When no changes are updated (first 2 cases with 389 DS) , in debug > > mode, I have no error reported to the console (no error, no > modified > > entries, All entries: 188, to modify entries: 0, successfully > modified > > entries: 0, errors: 0). > > > > Lsc 1.2.2 with the same (converted) script : > > - Sync from 389 Directory Server 1.2.8 to ODJ 2.4 : OK - sync works > > > successfully, including changes. > > > > Is 389 DS supported by Lsc 2.1.3 ? > > Or may be we miss something else ... > > > > LSC supports all LDAPv3 servers. > > Try this minimal logback configuration: > > ---- > <?xml version="1.0" encoding="UTF-8"?> > > <configuration> > > <!-- Standard output to console --> > <appender name="CONSOLE" > class="ch.qos.logback.core.ConsoleAppender"> > <encoder > class="ch.qos.logback.core.encoder.LayoutWrappingEncoder"> > <layout class="org.lsc.utils.output.LdifLayout"> > <Pattern>%date{MMM dd HH:mm:ss} - > %-5level - %message%n</Pattern> > </layout> > </encoder> > </appender> > > <!-- Other messages --> > <logger name="communicationLogger"> > <appender-ref ref="CONSOLE"/> > </logger> > <logger name="org.apache" level="ERROR"> > <appender-ref ref="CONSOLE"/> > </logger> > <logger name="poolLogger"> > <appender-ref ref="CONSOLE"/> > </logger> > <!-- Root logger --> > <root level="DEBUG"> > <appender-ref ref="CONSOLE"/> > </root> > </configuration> > --- > > And see what happens. I think the conversion between old and new > configuration format may not be good. Try to send your lsc.xml if you > > don't find the issue yourself. > > -- > Cl?ment OUDOT > Consultant en logiciels libres, Expert infrastructure et s?curit? > Savoir-faire Linux > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > < http://lists.lsc-project.org/pipermail/lsc-users/attachments/20150917/9a88119a/attachment.html > [2]> > > ------------------------------ > > Message: 2 > Date: Thu, 17 Sep 2015 09:47:11 +0200 > From: Cl?ment OUDOT <[email protected]> > Subject: Re: [lsc-users] Problem with launching LSC > To: [email protected] > Message-ID: <[email protected]> > Content-Type: text/plain; charset="windows-1252"; Format="flowed" > > Le 16/09/2015 17:58, Kaoutar Hajji a ?crit : > > Hi, > > > > When i run this command: sudo /usr/bin/lsc -f/etc/lsc/ -s all-c all > > i get this error: > > > Caused by: org.xml.sax.SAXParseException: Le contenu des ?l?ments > doit inclure un balisage ou des caract?res au format correct > > Means your XML file is not valid. > > I tried to parse with this online tool: http://www.xmlvalidation.com, > > and I found that you have spaces in "CDATA" markups, you should > remove > them to have only '<![CDATA[' > > -- > Cl?ment OUDOT > Consultant en logiciels libres, Expert infrastructure et s?curit? > Savoir-faire Linux > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > < http://lists.lsc-project.org/pipermail/lsc-users/attachments/20150917/8b722449/attachment-0001.htm > [3]> > > ------------------------------ > > _______________________________________________ > lsc-users mailing list > [email protected] > http://lists.lsc-project.org/listinfo/lsc-users [1] > > End of lsc-users Digest, Vol 68, Issue 10 > ***************************************** > > > > Links: > ------ > [1] http://lists.lsc-project.org/listinfo/lsc-users > [2] > http://lists.lsc-project.org/pipermail/lsc-users/attachments/20150917/9a88119a/attachment.html > [3] > http://lists.lsc-project.org/pipermail/lsc-users/attachments/20150917/8b722449/attachment-0001.htm > > _______________________________________________________________ > Ldap Synchronization Connector (LSC) - http://lsc-project.org > > lsc-users mailing list > [email protected] > http://lists.lsc-project.org/listinfo/lsc-users
access
Description: Binary data
errors
Description: Binary data
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-users
