• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • remoting
    • all
    • 3159.vb_8c0ef2b_55a_f as included in Jenkins 2.428 and 2.426.1

      agent.jar 4.3 does not work behind a firewall.  The last release that I can successfully get to connect is 3.17.  I am using -Dhttps.proxyHost and -Dhttps.proxyPort - with no success with the newer release, but it does work successfully with the old release

          [JENKINS-65368] Remoting agent.jar does not work behind proxy

          Annette added a comment - - edited

          getting can't connect to port 49187.

          Annette added a comment - - edited getting can't connect to port 49187.

          Annette added a comment -

          jenkins log reports - SEVERE: HTTPS://Jenkins.server/ provided port:49187 is not reachable

           

          Annette added a comment - jenkins log reports - SEVERE: HTTPS://Jenkins.server/ provided port:49187 is not reachable  

          Sun WeiSheng added a comment -

          System management interface, select the global security configuration, modify the TCP port for inbound agents to be selected randomly, and click save.

          Sun WeiSheng added a comment - System management interface, select the global security configuration, modify the TCP port for inbound agents to be selected randomly, and click save.

          Sun WeiSheng added a comment -

          If you can’t solve it, please provide more detailed information and environmental instructions, thank you

          Sun WeiSheng added a comment - If you can’t solve it, please provide more detailed information and environmental instructions, thank you

          Annette added a comment -

          thanks for your input...so this is a jenkins server that is supporting many slaves..all operational.  This is the only slave that is behind a proxy server... adding startup parameters.

          Annette added a comment - thanks for your input...so this is a jenkins server that is supporting many slaves..all operational.  This is the only slave that is behind a proxy server... adding startup parameters.

          Annette added a comment -

          I am a little hesitant to change ..

          here is more infor...

          java -Djavax.net.ssl.keystore=/usr/local./share/certs/dev-03.p12 -Djavax.net.ssl.keyStorePassword=password -Djava.net.ssl.trustStore=/usr/local/share/certs/trust.jks -Djavax.new.ssl.trustStorePassword=password -Djava.io.tmpdir=/data/1/jenkins/tmp -Dhttps.Host=proxy.server -Dhttps.proxyPort=1234 -jar /usr/local/share/applications/slave.jar -jnlpUrl https://jenkins.server.jenkins.computer.dev-03/slave-agent.jnlp -loggingConfig /usr/local/share/applications/logging.properties

          These are the parameters that I am specifying......if I use the older slave.jar mentioned above, it works and conects...if I new the newer one it does not with the error listed above.

          I hope this helps.

           

           

          Annette added a comment - I am a little hesitant to change .. here is more infor... java -Djavax.net.ssl.keystore=/usr/local./share/certs/dev-03.p12 -Djavax.net.ssl.keyStorePassword=password -Djava.net.ssl.trustStore=/usr/local/share/certs/trust.jks -Djavax.new.ssl.trustStorePassword=password -Djava.io.tmpdir=/data/1/jenkins/tmp -Dhttps.Host=proxy.server -Dhttps.proxyPort=1234 -jar /usr/local/share/applications/slave.jar -jnlpUrl https://jenkins.server.jenkins.computer.dev-03/slave-agent.jnlp -loggingConfig /usr/local/share/applications/logging.properties These are the parameters that I am specifying......if I use the older slave.jar mentioned above, it works and conects...if I new the newer one it does not with the error listed above. I hope this helps.    

          Annette added a comment - - edited

          more detail on error messages -

          INFO: Jenkins agent is running in headless mode.
          hudons.remoting.engine.Engine startEngine
          INFO Using Remoting version 4.3
          org.jenkinsci.remoting.engine.WordDirManager initializeWorkDir
          INFO: using /data/1/jenkins/remoting as a remoting work directory
          hudson.remoting.jnlp.Main$CuiListener status
          INFO: Location server among https://jenkins.server/jenkins/
          org.jenkinsci.remoting.engine.JnlpAgentEndpoint.Resolver resolve
          INFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]
          org.jenkinsci.remoting.engine.JnlpAgentEndpointRrsolver isPortvisible
          WARNING: connect timed out

          SEVERE java.io.IOException:https://jenkins.server/jenkins provided port:49187 is not reachable
          at org.jenkinsci.remoting.ening.JnlpAgentEndpointresolver.resolv(JNLPAgentEndpointResolver.java.314)
          at hudson.remoting.Engine.innerRun(Engine.java:663)
          at hudson.remoting.Engine.run(Enginer.java.528)

          Annette added a comment - - edited more detail on error messages - INFO: Jenkins agent is running in headless mode. hudons.remoting.engine.Engine startEngine INFO Using Remoting version 4.3 org.jenkinsci.remoting.engine.WordDirManager initializeWorkDir INFO: using /data/1/jenkins/remoting as a remoting work directory hudson.remoting.jnlp.Main$CuiListener status INFO: Location server among https://jenkins.server/jenkins/ org.jenkinsci.remoting.engine.JnlpAgentEndpoint.Resolver resolve INFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping] org.jenkinsci.remoting.engine.JnlpAgentEndpointRrsolver isPortvisible WARNING: connect timed out SEVERE java.io.IOException: https://jenkins.server/jenkins provided port:49187 is not reachable at org.jenkinsci.remoting.ening.JnlpAgentEndpointresolver.resolv(JNLPAgentEndpointResolver.java.314) at hudson.remoting.Engine.innerRun(Engine.java:663) at hudson.remoting.Engine.run(Enginer.java.528)

          Annette added a comment - - edited

          run openssl s_cleint and conect successfully..ie...I ge the connected....but it stops there..almost like it can't get back,,,

          openssl11 s_client -connect jenkins.server:49187 -proxy proxy.server:1234
          CONNECTED (00000003)
          hit cntrl c to get out

          Its almost like it can reach the server, but the server cannot find its way back again. Once parameter that looked hopeful was tunnel connection through on the advanced panel when configuring the slave. I found a brief reference to this on cloud bees.
          as follows -
          Load balancer or ha-proxy

          If you are using a load balancer or a ha-proxy and you are not running Jenkins on ha mode, you might want to bypass any of them through the Agent advance option of Tunnel connection through.

          I tried configuring it with the proxy server, with no success. What is this parameter supposed to be? Or if you have other suggestions, it would be most helpful. Thanks for your help.

          Annette added a comment - - edited run openssl s_cleint and conect successfully..ie...I ge the connected....but it stops there..almost like it can't get back,,, openssl11 s_client -connect jenkins.server:49187 -proxy proxy.server:1234 CONNECTED (00000003) hit cntrl c to get out Its almost like it can reach the server, but the server cannot find its way back again. Once parameter that looked hopeful was tunnel connection through on the advanced panel when configuring the slave. I found a brief reference to this on cloud bees. as follows - Load balancer or ha-proxy If you are using a load balancer or a ha-proxy and you are not running Jenkins on ha mode, you might want to bypass any of them through the Agent advance option of Tunnel connection through. I tried configuring it with the proxy server, with no success. What is this parameter supposed to be? Or if you have other suggestions, it would be most helpful. Thanks for your help.

          Annette added a comment -

          on Jenkins node server side - (errors are as follows)
          java.nio.channels.ClosedChannelException
          at org.jankinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154)
          at org.jankinsci.remoting.protocol.impl.NIONetworkLayer.ready(NIONetworkLayer.java.142)
          at org.jankinsci.remoting.protocol.IOHub$OnReady.run(IOHub.java.795)
          at jenkins.util.ContextResettingExecutorService$1$1.run(ContextResettingExecutorService.java.28)
          at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutor.Service.java.59)
          at Java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java.1149)
          at Java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java.624)
          at java.lang.thread.run(Thread.java.748)

          Annette added a comment - on Jenkins node server side - (errors are as follows) java.nio.channels.ClosedChannelException at org.jankinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154) at org.jankinsci.remoting.protocol.impl.NIONetworkLayer.ready(NIONetworkLayer.java.142) at org.jankinsci.remoting.protocol.IOHub$OnReady.run(IOHub.java.795) at jenkins.util.ContextResettingExecutorService$1$1.run(ContextResettingExecutorService.java.28) at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutor.Service.java.59) at Java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java.1149) at Java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java.624) at java.lang.thread.run(Thread.java.748)

            bluersw Sun WeiSheng
            annette Annette
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: