Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-55689

Not able to connect to jenkins master from windows slave

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Blocker
    • Resolution: Incomplete
    • Component/s: windows-slaves-plugin
    • Labels:
      None
    • Environment:
      Jenkins Version: 2.150.1
      Master is running in Docker Container in DC/OS (Mesos) environment.
      web browser: chrome
    • Similar Issues:

      Description

      Hi Team,

      we are running jenkins master as docker container in DC/OS(mesos) environment.  we have two ports available for setting up the configuration. 

      container port 8080 is mapped to service port 29XXXfor jenkins.

      container port 50000 is mapped to service port  29XXX for jenkins-agent.

      I have configured the jenkins-agent port in manage Jenkins->Global Security->TCP port for JNLP agents. and also tried to give the default port and multiple random ports but while running the agent i get the error as port is not reachable.

      SEVERE: https://develop.qa.ampf.com/jenkins/ provided port:41172 is not reachable
      java.io.IOException: https://develop.qa.ampf.com/jenkins/ provided port:41172 is not reachable
      at org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:286)
      at hudson.remoting.Engine.innerRun(Engine.java:523)
      at hudson.remoting.Engine.run(Engine.java:474)
      Suppressed: java.io.IOException: http://develop.qa.ampf.com/jenkins/tcpSlaveAgentListener/ is invalid: 302 Found
      at org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:201)
      ... 2 more

       

      Do i need to mention anything in the tunnel part?

       

      Thanks,

      Mohit Saraf

       

       

       

        Attachments

          Activity

          Hide
          msaraf1 Mohit Saraf added a comment -

          Hi Team,

          Any suggestions?

          Show
          msaraf1 Mohit Saraf added a comment - Hi Team, Any suggestions?
          Hide
          msaraf1 Mohit Saraf added a comment -

          Hi,

          Please advise if i need to change anything in the configuration

          Show
          msaraf1 Mohit Saraf added a comment - Hi, Please advise if i need to change anything in the configuration
          Hide
          escoem Emilio Escobar added a comment -

          hello Mohit, probably adding the tunnel with ":41172" might be enough. Anyway, this is not a windows-slaves-plugin issue but a question to ask at Jenkins users mailing list.

          Show
          escoem Emilio Escobar added a comment - hello Mohit, probably adding the tunnel with ":41172" might be enough. Anyway, this is not a windows-slaves-plugin issue but a question to ask at Jenkins users mailing list.
          Hide
          punshett Punith Shetty added a comment -

          Hi, Is there a resolution for this issue ?

          I am seeing the same error for my servers

           

          INFO: Setting up agent: windows_agent
          Aug 26, 2019 1:10:22 PM hudson.remoting.jnlp.Main$CuiListener <init>
          INFO: Jenkins agent is running in headless mode.
          Aug 26, 2019 1:10:22 PM hudson.remoting.Engine startEngine
          INFO: Using Remoting version: 3.25
          Aug 26, 2019 1:10:22 PM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir
          INFO: Using F:\win_jenkins\remoting as a remoting work directory
          Aug 26, 2019 1:10:22 PM hudson.remoting.jnlp.Main$CuiListener status
          INFO: Locating server among https://myserver/
          Aug 26, 2019 1:10:22 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve
          INFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping, Diagnostic-Ping, OperationsCenter2]
          Aug 26, 2019 1:10:23 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver isPortVisible
          WARNING: Connection refused: connect
          Aug 26, 2019 1:10:23 PM hudson.remoting.jnlp.Main$CuiListener error
          SEVERE: https://myserver/ provided port:46080 is not reachable
          java.io.IOException: https://myserver/ provided port:46080 is not reachable
          at org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:286)
          at hudson.remoting.Engine.innerRun(Engine.java:523)
          at hudson.remoting.Engine.run(Engine.java:474)

          Show
          punshett Punith Shetty added a comment - Hi, Is there a resolution for this issue ? I am seeing the same error for my servers   INFO: Setting up agent: windows_agent Aug 26, 2019 1:10:22 PM hudson.remoting.jnlp.Main$CuiListener <init> INFO: Jenkins agent is running in headless mode. Aug 26, 2019 1:10:22 PM hudson.remoting.Engine startEngine INFO: Using Remoting version: 3.25 Aug 26, 2019 1:10:22 PM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir INFO: Using F:\win_jenkins\remoting as a remoting work directory Aug 26, 2019 1:10:22 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Locating server among https://myserver/ Aug 26, 2019 1:10:22 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve INFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping, Diagnostic-Ping, OperationsCenter2] Aug 26, 2019 1:10:23 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver isPortVisible WARNING: Connection refused: connect Aug 26, 2019 1:10:23 PM hudson.remoting.jnlp.Main$CuiListener error SEVERE: https://myserver/ provided port:46080 is not reachable java.io.IOException: https://myserver/ provided port:46080 is not reachable at org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:286) at hudson.remoting.Engine.innerRun(Engine.java:523) at hudson.remoting.Engine.run(Engine.java:474)
          Hide
          jthompson Jeff Thompson added a comment -

          Have you asked on the Jenkins users email list as suggested? Or the gitter channel? This looks like a usage or configuration question and not a specific defect.

          Show
          jthompson Jeff Thompson added a comment - Have you asked on the Jenkins users email list as suggested? Or the gitter channel? This looks like a usage or configuration question and not a specific defect.
          Hide
          punshett Punith Shetty added a comment - - edited

          Thanks i was able to get this working, the issue was the nodeport. TCP traffic is only served on nodeport on openshift/kubernetes platform. Once i got the nodeport opened on the platform and created a tunnel for it to route traffic to the slave agent port on jenkins, i was able to make the connection.

          Show
          punshett Punith Shetty added a comment - - edited Thanks i was able to get this working, the issue was the nodeport. TCP traffic is only served on nodeport on openshift/kubernetes platform. Once i got the nodeport opened on the platform and created a tunnel for it to route traffic to the slave agent port on jenkins, i was able to make the connection.
          Hide
          jthompson Jeff Thompson added a comment -

          Punith Shetty, thanks for responding with your success and describing the solution that worked for you. That helps others who might encounter a similar problem.

          Show
          jthompson Jeff Thompson added a comment - Punith Shetty , thanks for responding with your success and describing the solution that worked for you. That helps others who might encounter a similar problem.

            People

            Assignee:
            jeffret Jeff Thompson
            Reporter:
            msaraf1 Mohit Saraf
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: