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

Swarm cannot connect to Jenkins Master provided port:50000 is not reachable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Not A Defect
    • Component/s: swarm-plugin
    • Labels:
      None
    • Environment:
      jenkins version: 2.182
      swarm plugin version: 3.17
      Java Version on slave and master is open JDK 1.8.0_201
    • Similar Issues:

      Description

      Hello,

      I am currently running Jenkins 2.138.3 with plugin version 3.12, I am attempting to upgrade to Jenkins 2.182 and plugin 3.17.

       

      Looks like I am getting an error that it can't connect to port 50000 (the fixed agent port). I attached the verbose logs.

       

      When I do a curl from the slave to the master I see 50000 is available.

      [ec2-user@ip-10-0-6-121 ~]$ curl 10.0.7.19:50000
      Jenkins-Agent-Protocols: JNLP4-connect, Ping
      Jenkins-Version: 2.182
      Jenkins-Session: 02bf8ba3
      Client: 10.0.6.121
      Server: 10.0.7.19
      Remoting-Minimum-Version: 3.4
      

      Any ideas would be appreciated, I am currently just downgrading Jenkins to previous versions to see if that will help.

        Attachments

          Activity

          Hide
          basil Basil Crow added a comment -

          Hey Joey Khashab, does this failure happen consistently or is it transient?

          Show
          basil Basil Crow added a comment - Hey Joey Khashab , does this failure happen consistently or is it transient?
          Hide
          tactis Joey Khashab added a comment -

          Basil Crow thanks for your reply, after trying several things, I realized I was passing in `-Dhudson.TcpSlaveAgentListener.hostName=master_ip` into my Jenkins as part of my Chef provisioning for Jenkins master, after putting in the correct IP address for master it seems to be working.

          Cancelling this issue.

          Show
          tactis Joey Khashab added a comment - Basil Crow thanks for your reply, after trying several things, I realized I was passing in `-Dhudson.TcpSlaveAgentListener.hostName=master_ip` into my Jenkins as part of my Chef provisioning for Jenkins master, after putting in the correct IP address for master it seems to be working. Cancelling this issue.

            People

            • Assignee:
              Unassigned
              Reporter:
              tactis Joey Khashab
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: