Pipelines are queued forerver

160 views
Skip to first unread message

Angel Fernandez - Cañada Vilata

unread,
May 4, 2016, 7:39:31 AM5/4/16
to xnat_discussion
Hi,
 I've XNAT 1.6.5. My problem is related to the pipelines. I can't launch any pipiline even AutoRun. The error obtained is belong this lines:

DEBUG main org.nrg.pipeline.client.CommandLineArguments - Pipeline executed with command line: -config /home/xxxxxx/instance/setup/xnat/pipeline/pipeline.config -log /home/xxxxxx/instance/setup/xnat/pipeline/log4j.properties -catalogPath /home/cafetero/instance/setup/xnat/pipeline/catalog -pipeline /home/xxxxxx/instance/setup/xnat/pipeline/catalog/pipeline-dcm2niigz/pipeline-dcm2niigz.xml -id xxxxxx -host https://xxxxxxx/xnat -u fbb6ed5b-f641-470c-bd2a-9cb3260c22b5 -pwd XXXXXXXXX -dataType xnat:mrSessionData -label 49015019493451477403517183525388096979 -supressNotification -project pruebas -parameterFile /home/xxxxx/instance/data/build/pruebas/20160504_122835/49015019493451477403517183525388096979/49015019493451477403517183525388096979_params_20160504.xml -notify xx...@gmail.com -parameter mailhost=smtp.gmail.com -parameter userfullname=A.Admin -parameter builddir=/home/xxxxx/instance/data/build/pruebas/20160504_122835 -parameter xnatserver=ceibcs -parameter adminemail=xxx...@gmail.com -parameter useremail=xxx...@gmail.com -workFlowPrimaryKey 161
DEBUG main org.nrg.pipeline.utils.PipelineProperties - Initializing the pipeline properties from the specified properties object
DEBUG main org.nrg.pipeline.utils.PipelineProperties - Setting admin email to:xx...@gmail.com
DEBUG main org.nrg.pipeline.utils.PipelineProperties - Setting email ID to: xx...@gmail.com
DEBUG main org.nrg.pipeline.utils.PipelineProperties - Setting SMTP host to: smtp.gmail.com
DEBUG main org.nrg.pipeline.utils.PipelineProperties - Setting REST mail host to: https://xxxxx/xnat/data/services/mail/send
FATAL main org.nrg.pipeline.client.XNATPipelineLauncher - Couldn't search for queued workflows
java.net.ConnectException: Connection refused
        at java.net.PlainSocketImpl.socketConnect(Native Method)
        at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
        at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
        at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
        at java.net.Socket.connect(Socket.java:579)
        at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:625)
        at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:522)
        at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:401)
        at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177)
        at org.apache.http.impl.conn.ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:304)
        at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611)
        at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446)
        at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863)
        at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
        at org.nrg.xnattools.SessionManager.createJSESSION(SessionManager.java:84)
        at org.nrg.xnattools.SessionManager.getJSESSION(SessionManager.java:136)
        at org.nrg.xnattools.service.WebServiceClient.connect(WebServiceClient.java:84)
        at org.nrg.pipeline.client.XNATPipelineLauncher.isPipelineQueuedOrAwaitingOrOnHold(XNATPipelineLauncher.java:368)
        at org.nrg.pipeline.client.XNATPipelineLauncher.isPipelineQueuedOrAwaitingOrOnHold(XNATPipelineLauncher.java:352)
        at org.nrg.pipeline.client.XNATPipelineLauncher.launch(XNATPipelineLauncher.java:61)
        at org.nrg.pipeline.client.XNATPipelineLauncher.run(XNATPipelineLauncher.java:298)
        at org.nrg.pipeline.client.XNATPipelineLauncher.main(XNATPipelineLauncher.java:260)

My certificate seems to be well installed but the conexion is refused.

Also I've other problem. When I try to list the project pipelines I received the next message: "Failed to load pipeline list for project pruebas."

Can anybody help me?

Thanks for advanced

Angel Fernandez - Cañada Vilata

unread,
May 4, 2016, 10:24:31 AM5/4/16
to xnat_discussion

I found more information launching some rest petitions

/home/xxxxx/instance/setup/xnat/pipeline/xnat-tools/XNATRestClient -ts $JRE_HOME/lib/security/cacerts -tsPass xxxx -host https://ceib.cipf.es/xnat -u xxxx -p xxxxx -m GET -remote "/data/archive/projects/pruebas/subjects?format=json"
Loaded Certificate: /home/cafetero/instance/setup/java/jre/lib/security/cacerts
ERROR CODE 13: Unable to connect to Web Service Server: https://ceib.cipf.es/xnat/

and in error.log

Wed May 04 16:17:59 CEST 2016 admin@https://ceib.cipf.es/xnat/:java.net.ConnectException: Connection refused

        at java.net.PlainSocketImpl.socketConnect(Native Method)
        at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
        at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
        at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392).................



Angel Fernandez - Cañada Vilata

unread,
May 4, 2016, 11:13:25 AM5/4/16
to xnat_discussion
Ok it seems that if i put the port in my rest petition it runs ok. However, in a earlier installation I didn't do it and it worked.
In the other hand, How I could specify this in my pipelines, they have a tag for port or host?                                

Reply all
Reply to author
Forward
0 new messages