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

The server rejected the connection: *** is already connected to this master. Rejecting this connection.

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Blocker Blocker
    • core, remoting
    • None
    • Windows 7, Jenkins 1.613

      I am running Jenkins 1.613.

      i see the slaves log:
      四月 15, 2015 10:15:02 上午 com.youdevise.hudson.slavestatus.SlaveListener call
      信息: Slave-status listener starting
      四月 15, 2015 10:15:02 上午 com.youdevise.hudson.slavestatus.SocketHTTPListener waitForConnection
      信息: Slave-status listener ready on port 3141
      四月 15, 2015 1:41:01 下午 hudson.remoting.jnlp.Main createEngine
      信息: Setting up slave: 192.168.161.8
      四月 15, 2015 1:41:01 下午 hudson.remoting.jnlp.Main$CuiListener <init>
      信息: Jenkins agent is running in headless mode.
      四月 15, 2015 1:41:01 下午 hudson.remoting.jnlp.Main$CuiListener status
      信息: Locating server among http://192.168.95.37:8080/jenkins/
      四月 15, 2015 1:41:01 下午 hudson.remoting.jnlp.Main$CuiListener status
      信息: Connecting to 192.168.95.37:19994
      四月 15, 2015 1:41:01 下午 hudson.remoting.jnlp.Main$CuiListener status
      信息: Handshaking
      四月 15, 2015 1:41:01 下午 hudson.remoting.jnlp.Main$CuiListener error
      严重: The server rejected the connection: 192.168.161.8 is already connected to this master. Rejecting this connection.
      java.lang.Exception: The server rejected the connection: 192.168.161.8 is already connected to this master. Rejecting this connection.
      at hudson.remoting.Engine.onConnectionRejected(Engine.java:306)
      at hudson.remoting.Engine.run(Engine.java:276)

        1. Slave errors
          2 kB
        2. channelclosedstack.txt
          1.30 MB
        3. jenkins-slave.err.log
          293 kB

          [JENKINS-28492] The server rejected the connection: *** is already connected to this master. Rejecting this connection.

          gaffey he created issue -
          sonu kumar made changes -
          Priority Original: Major [ 3 ] New: Blocker [ 1 ]

          sonu kumar added a comment -

          any help here would be great

          sonu kumar added a comment - any help here would be great

          Alex Earl added a comment -

          Can you verify that you don't have another instance of the slave.jar running on your slave computer? Either that, or you may have two computers with the same IP address.

          Alex Earl added a comment - Can you verify that you don't have another instance of the slave.jar running on your slave computer? Either that, or you may have two computers with the same IP address.

          Daniel Beck added a comment -

          I think the "IP address" here may be the slave name? If so, there may also be two machines claiming to be the same slave.

          Daniel Beck added a comment - I think the "IP address" here may be the slave name? If so, there may also be two machines claiming to be the same slave.
          Douglas Wooster made changes -
          Link New: This issue is related to JENKINS-5055 [ JENKINS-5055 ]

          This issue is reporting the same symptoms as JENKINS-5055, which was thought to have been fixed back before the Hudson/Jenkins split, but now has multiple people reporting that the problem is back.

          Douglas Wooster added a comment - This issue is reporting the same symptoms as JENKINS-5055 , which was thought to have been fixed back before the Hudson/Jenkins split, but now has multiple people reporting that the problem is back.

          Douglas Wooster added a comment - - edited

          I am seeing the exact same thing with Jenkins 1.574, after reboot of the slave.
          We download the slave.jar from the master before every startup so we know it is current.
          Both slaves and master are RHEL 6.4 Linux.
          Slaves are started headless from an init script when the machine is booted.
          Error occurs about 1/3 of the time.

          Douglas Wooster added a comment - - edited I am seeing the exact same thing with Jenkins 1.574, after reboot of the slave. We download the slave.jar from the master before every startup so we know it is current. Both slaves and master are RHEL 6.4 Linux. Slaves are started headless from an init script when the machine is booted. Error occurs about 1/3 of the time.

          Matthew Mitchell added a comment - - edited

          I'm also seeing this on Jenkins 1.642.3. In addition, if the connection is explicitly stopped on the slave side, the master still shows the slave as connected.

          Matthew Mitchell added a comment - - edited I'm also seeing this on Jenkins 1.642.3. In addition, if the connection is explicitly stopped on the slave side, the master still shows the slave as connected.

          Matthew Mitchell added a comment - - edited

          Also, we didn't use it see this at all, but there appears to be a large uptick in instances since moving towards more cloud allocated machines (azure-slave-plugin) though the Azure slave plugin machine do not ever see the issue. I have also never seen it on SSH connected machines.

          Matthew Mitchell added a comment - - edited Also, we didn't use it see this at all, but there appears to be a large uptick in instances since moving towards more cloud allocated machines (azure-slave-plugin) though the Azure slave plugin machine do not ever see the issue. I have also never seen it on SSH connected machines.

            oleg_nenashev Oleg Nenashev
            gaffey gaffey he
            Votes:
            9 Vote for this issue
            Watchers:
            17 Start watching this issue

              Created:
              Updated:
              Resolved: