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

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

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Major Major
    • swarm-plugin
    • None
    • jenkins version: 2.182
      swarm plugin version: 3.17
      Java Version on slave and master is open JDK 1.8.0_201

      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.

        1. jenkins_swarm_verbose_logs.txt
          29 kB

          [JENKINS-58221] Swarm cannot connect to Jenkins Master provided port:50000 is not reachable

          Basil Crow added a comment -

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

          Basil Crow added a comment - Hey tactis , does this failure happen consistently or is it transient?

          Joey Khashab added a comment -

          basil 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.

          Joey Khashab added a comment - basil 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.

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

              Created:
              Updated:
              Resolved: