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

Swarm client failed to reconnect after connection to "Jenkins" server was lost.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • swarm-plugin
    • None
    • Windows 10 Enterprise 64 bit OS, x64 based processor
      swarm-client 3.27

      Swarm client 3.27.

      After loosing connection (I don't know the reason), the swarm client shall reconnect to the "Jenkins" server, but it says in the log, that connection is already established.

      I expect that the swarm client reconnect to the "Jenkins" server without error,
      or having the following situation, clears up old connection, and creates a new, fresh one.

      Please for correcting, or for advice, what is going wrong, maybe client swarm is ok.

      I attach also some full error logs.

      The issue is repeatable and always the same, as in the following example log:

      Jul 07, 2021 10:57:41 PM hudson.remoting.jnlp.Main$CuiListener status
      INFO: Terminated
      (...)
      .
      .
      .
      (...)
      Jul 07, 2021 10:57:41 PM hudson.plugins.swarm.Client run
      WARNING: Remaining retries: 299
      Jul 07, 2021 10:57:41 PM hudson.plugins.swarm.Client run
      INFO: Retrying in 60 seconds
      Jul 07, 2021 10:58:41 PM hudson.plugins.swarm.Client run
      INFO: Attempting to connect to https://jenkins-regression-nft.kce.devops.rockwell.com/
      (...)
      .
      .
      .
      (...)
      INFO: Handshaking
      Jul 07, 2021 10:58:46 PM hudson.remoting.jnlp.Main$CuiListener status

      INFO: Connecting to jenkins-regression-nft.kce.devops.rockwell.com:32035
      Jul 07, 2021 10:58:46 PM hudson.remoting.jnlp.Main$CuiListener status
      INFO: Trying protocol: JNLP4-connect
      Jul 07, 2021 10:58:46 PM hudson.remoting.jnlp.Main$CuiListener status
      INFO: Remote identity confirmed: 52:4d:78:17:3a:9b:22:e8:eb:33:75:df:a6:71:37:45
      Jul 07, 2021 10:58:46 PM org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecv
      INFO: [JNLP4-connect connection to jenkins-regression-nft.kce.devops.rockwell.com/10.76.72.130:32035] Local headers refused by remote: tbenzt-1 is already connected to this master. Rejecting this connection.
      Jul 07, 2021 10:58:46 PM hudson.remoting.jnlp.Main$CuiListener status
      INFO: Protocol JNLP4-connect encountered an unexpected exception
      java.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: tbenzt-1 is already connected to this master. Rejecting this connection.

      Related issues:

      https://issues.jenkins.io/browse/JENKINS-5055

      https://issues.jenkins.io/browse/JENKINS-5973

      Best regards

      Grzegoz Guzik

      "NoYes" Team

      Rockwell Automation

            Unassigned Unassigned
            gguzik Grzegorz
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: