oops, indeed without the mvn package build , I guess I am missing lots of files 
. 

so I did it : 

[root@buildcentos7-64 lsc-master]# mvn package 

unfortunatly it ends on : 

Tests run: 86, Failures: 4, Errors: 12, Skipped: 0 

[INFO] ------------------------------------------------------------------------ 
[INFO] BUILD FAILURE 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.11:test (default-test) on 
project lsc-core: There are test failures. 
[ERROR] 
[ERROR] Please refer to /tmp/lsc-master/target/surefire-reports for the 
individual test results. 
[ERROR] -> [Help 1] 

I am not fluent in Java, but moving up the error logs I found the 1st one to be 
: 

Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec 
Running org.lsc.utils.directory.LDAPTest 
09:06:36.241 [main] INFO org.lsc.jndi.JndiServices - Connecting to LDAP server 
ldap://no.such.host.really:33389/ anonymously 
09:06:36.257 [main] INFO org.lsc.jndi.JndiServices - Connecting to LDAP server 
ldap://localhost:33389/ anonymously 
09:06:36.495 [main] INFO org.lsc.jndi.JndiServices - Connecting to LDAP server 
ldap://localhost:33389/ as cn=Directory Manager 
09:06:36.516 [main] INFO org.lsc.jndi.JndiServices - Connecting to LDAP server 
ldap://localhost:33389/dc=lsc-project,dc=org as cn=Directory Manager 
09:06:36.561 [main] ERROR org.lsc.jndi.JndiServices - Too many entries returned 
(base: "", filter: "(cn=CN0001)") 
09:06:36.565 [main] INFO org.lsc.jndi.JndiServices - Connecting to LDAP server 
ldap://localhost:33389/dc=lsc-project,dc=com as cn=Directory Manager 
09:06:36.575 [main] ERROR org.lsc.jndi.JndiServices - Error while looking for 
(cn=CN0001) in : javax.naming.NameNotFoundException: [LDAP: error code 32 - The 
entry dc=lsc-project,dc=com specified as the search base does not exist in the 
Directory Server]; remaining name '' 
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.517 sec 
Running org.lsc.utils.GroovyEvaluatorTest 
09:06:36.694 [main] WARN org.lsc.jndi.SimpleJndiSrcService - No clean filter 
has been specified for task=ldap2ldapTestTask. During the clean phase, LSC 
wouldn't be able to get the right entries and may delete all destination 
entries ! 
[java] Java Result: 137 


Then dozens of lines below 


09:06:40.231 [main] INFO org.lsc.Configuration - LSC configuration successfully 
loaded from /tmp/lsc-master/target/test-classes/etc/ 
09:06:40.238 [main] INFO org.lsc.jndi.JndiServices - Communication error, 
retrying: connection closed 
09:06:40.240 [main] DEBUG org.lsc.jndi.JndiServices - connection closed 
javax.naming.CommunicationException: connection closed 
at com.sun.jndi.ldap.LdapCtx.doSearch(LdapCtx.java:2002) ~[na:1.8.0_222] 
.. 
Caused by: java.io.IOException: connection closed 
at com.sun.jndi.ldap.LdapClient.ensureOpen(LdapClient.java:1587) 
~[na:1.8.0_222] 
at com.sun.jndi.ldap.LdapClient.search(LdapClient.java:524) ~[na:1.8.0_222] 
at com.sun.jndi.ldap.LdapCtx.doSearch(LdapCtx.java:1985) ~[na:1.8.0_222] 
... 44 common frames omitted 
09:06:40.259 [main] INFO org.lsc.jndi.JndiServices - Connecting to LDAP server 
ldap://localhost:33389/dc=lsc-project,dc=org as cn=Directory Manager 
09:06:40.264 [main] ERROR org.lsc.jndi.JndiServices - 
javax.naming.CommunicationException: localhost:33389 [Root exception is 
java.net.ConnectException: Connection refused (Connection refused)] 
09:06:40.271 [main] DEBUG org.lsc.jndi.JndiServices - 
javax.naming.CommunicationException: localhost:33389 [Root exception is 
java.net.ConnectException: Connection refused (Connection refused)] 
javax.naming.CommunicationException: localhost:33389 
at com.sun.jndi.ldap.Connection.<init>(Connection.java:238) ~[na:1.8.0_222] 

and many others 

09:06:40.369 [ldap2ldapJmxTestTask] DEBUG org.lsc.AbstractSynchronize - 
Asynchronous synchronize ldap2ldapJmxTestTask 
09:06:40.370 [ldap2ldapJmxTestTask] WARN org.lsc.jndi.JndiServices - 
Communication error, retrying: connection closed 
09:06:40.371 [ldap2ldapJmxTestTask] DEBUG org.lsc.jndi.JndiServices - 
connection closed 
javax.naming.CommunicationException: connection closed 
at com.sun.jndi.ldap.LdapCtx.doSearch(LdapCtx.java:2002) ~[na:1.8.0_222] 

Looking a those error, I am wonderring if I need to install openldap-servers 
packages and open all iptables (which I did without success) . 

If you have an other idea to get one step further ... 

thanks . 



Jehan PROCACCIA 
Ingénieur systèmes et réseaux 
Membre du comité de pilotage REVE : 
Réseau d’Évry Val d'Essonne et THD 
+33160764436 
9 rue Charles Fourier - 91011 Evry Cedex 
[ https://www.imt-bs.eu/ | www.imt-bs.eu ] - [ https://www.telecom-sudparis.eu/ 
| www.telecom-sudparis.eu ] 

----- Mail original ----- 
De: "Clément OUDOT" <clement.ou...@worteks.com> 
À: "General discussions and help for Ldap Synchronization Connector, (LSC) - 
Start here!" <lsc-users@lists.lsc-project.org> 
Envoyé: Mardi 8 Octobre 2019 07:46:21 
Objet: Re: [lsc-users] different pivot attributs and values from ldap source to 
destination 

Le 07/10/2019 à 23:01, Jehan PROCACCIA a écrit : 
> Hello 
> 
> I rebuilt a rpm from latest src rpm and the last version from 
> https://github.com/lsc-project/lsc/ , the zip version of the master (which I 
> named lsc-2.2.0) 
> 
> $ mv lsc-master lsc-2.2.0 
> $ zip -r lsc-core-2.2.0-dist.zip lsc-2.2.0 
> $ cp lsc-core-2.2.0-dist.zip /home/builder/rpmbuild/SOURCES/ 
> 
> then I had to comment some files in lsc-core.spec (cron.d/lsc , default/lsc , 
> init.d/lsc , bin/check_lsc* %{buildroot}/var/lib/lsc/nagios) because not 
> anymore present in master (!?) 
> the package finally built corretly , here it is: 
> lsc-2.2.0-0.el7.centos.src.rpm 
> https://filesender.renater.fr/?s=download&token=90c968ca-1b65-d617-27da-cdec10a8c912
>  
> lsc-2.2.0-0.el7.centos.noarch.rpm at 
> https://filesender.renater.fr/?s=download&token=aeff1287-24aa-3d2d-8bcb-e62595ac1913
>  
> 
> but at 1st run, lsc fails with 
> 
> $ lsc -s user -t 1 --config /etc/lsc/ldapint2ldapfd/ 
> ls: cannot access /usr/lib64/lsc/slf4j-api*.jar: No such file or directory 
> Error: Could not find or load main class org.lsc.Launcher 
> 
> indeed , that file is not present 
> $ls /usr/lib64/lsc/ 
> ant-contrib-1.0b3.jar maven-ant-tasks-2.0.7.jar 
> 
> So I guess it is not that simple to upgrade old 2.1 src rpm to latest 2.2 
> (master) without more important changes than expected. 
> If you happen to create a 2.2 rpm, let me know, If the slf4j-api*.jar is the 
> only pb, maybe there's a simple way to correct it ? 


See https://lsc-project.org/documentation/latest/packaging/rpm 

You need to use mvn package to get the distribution tarball 


There may be indeed some things to fix in RPM packaging pour 2.2, I did 
not test it yet. 

-- 
Clément Oudot | Identity Solutions Manager 

clement.ou...@worteks.com 

Worteks | https://www.worteks.com 

_______________________________________________________________ 
Ldap Synchronization Connector (LSC) - http://lsc-project.org 

lsc-users mailing list 
lsc-users@lists.lsc-project.org 
https://lists.lsc-project.org/cgi-bin/mailman/listinfo/lsc-users 

_______________________________________________________________
Ldap Synchronization Connector (LSC) - http://lsc-project.org

lsc-users mailing list
lsc-users@lists.lsc-project.org
https://lists.lsc-project.org/cgi-bin/mailman/listinfo/lsc-users

Reply via email to