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

server rejected connection: already connected to master

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Critical
    • Resolution: Fixed
    • Component/s: remoting
    • Labels:
      None
    • Environment:
    • Similar Issues:

      Description

      After some idle time (no jobs running, master and slaves idle), the master showed a slave as offline.

      on the slave, I see an Error pop-up window saying:
      ...
      java.lang.Exception: The server rejected the connection: nlvhtcnxp1dt361 is
      already connected to this master. Rejecting this connection. at
      hudson.remoting.engine.Run(Engine.java:191)
      ...

      after clicking ok on pop-up windows, the hudson slave app terminates.
      restarting the hudson slave app manually seems to work fine.

        Attachments

          Issue Links

            Activity

            Hide
            dwooster Douglas Wooster added a comment - - edited

            We are seeing this issue in Jenkins 1.574, after rebooting the slave machine.
            Issue is intermittent - perhaps 1/3 of the time.
            Slaves are Linux, RHEL 6.4
            The slave is started from a local /etc/init.d script.
            Master is also RHEL 6.4 running on Tomcat 7.0.63.

            JENKINS-28492 was opened last year for the same error message, so I linked the two JIRAs.

            Show
            dwooster Douglas Wooster added a comment - - edited We are seeing this issue in Jenkins 1.574, after rebooting the slave machine. Issue is intermittent - perhaps 1/3 of the time. Slaves are Linux, RHEL 6.4 The slave is started from a local /etc/init.d script. Master is also RHEL 6.4 running on Tomcat 7.0.63. JENKINS-28492 was opened last year for the same error message, so I linked the two JIRAs.
            Hide
            gtirloni Giovanni Tirloni added a comment - - edited

            We're seeing this with Jenkins 2.14 after restarting the master.

            Workaround is to manually kill the java process running on the slave.

            Show
            gtirloni Giovanni Tirloni added a comment - - edited We're seeing this with Jenkins 2.14 after restarting the master. Workaround is to manually kill the java process running on the slave.
            Hide
            mmitche Matthew Mitchell added a comment -

            I have some other data (Jenkins 6.42.1 running on Ubuntu 16.04 Java 8).

            • This only happens on nodes that were connected via jnlp by running a command on the node (java -jar ...) and is not limited to Windows. Seen on OSX too.
            • The failure is always preceded by: INFO: Ping failed. Terminating the channel <node name>
            • The ping fails for many machines within a few seconds.
            • Only those machines connected via manual jnlp remoting call fail ping
            • In the server we have running, the nodes running that don't fail are connected via ssh and are Linux, FreeBSD, etc.
            • The nodes that fail and don't fail exist in the same locations (VMs in Azure)

            So the interesting data point here I think is the fact that the ping doesn't fail on the machines connected via SSH channel. Is it that they aren't using the JNLP remoting protocol?

            Show
            mmitche Matthew Mitchell added a comment - I have some other data (Jenkins 6.42.1 running on Ubuntu 16.04 Java 8). This only happens on nodes that were connected via jnlp by running a command on the node (java -jar ...) and is not limited to Windows. Seen on OSX too. The failure is always preceded by: INFO: Ping failed. Terminating the channel <node name> The ping fails for many machines within a few seconds. Only those machines connected via manual jnlp remoting call fail ping In the server we have running, the nodes running that don't fail are connected via ssh and are Linux, FreeBSD, etc. The nodes that fail and don't fail exist in the same locations (VMs in Azure) So the interesting data point here I think is the fact that the ping doesn't fail on the machines connected via SSH channel. Is it that they aren't using the JNLP remoting protocol?
            Hide
            cecchisandrone Alessandro Dionisi added a comment -

            Did you try to play with -Dhudson.slaves.ChannelPinger.pingInterval property?

            Show
            cecchisandrone Alessandro Dionisi added a comment - Did you try to play with -Dhudson.slaves.ChannelPinger.pingInterval property?
            Hide
            mmitche Matthew Mitchell added a comment -

            Woops I was wondering where this comment went. Was supposed to go to another issue. And yes. It doesn't have anything to do with the ping rate.

            Show
            mmitche Matthew Mitchell added a comment - Woops I was wondering where this comment went. Was supposed to go to another issue. And yes. It doesn't have anything to do with the ping rate.

              People

              • Assignee:
                Unassigned
                Reporter:
                tomdevries tomdevries
              • Votes:
                9 Vote for this issue
                Watchers:
                21 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: