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

Unable to connect web start agents after updating to 2.318 from 2.311. "Terminated" after 1 second

      Unable to connect to nodes after updating to 2.318 from 2.311. Agent connects for about 1 second before "terminated". No other changes made. All nodes are set to "Launch agent by connecting it to the controller". I even redownloaded new jenkins-agent.jnlp (from slave-agent.jnlp) from the nodes menu to connect on each agent. Still terminates. When I check the specific node on that same nodes menu in Jenkins is states: terminated: java.nio.channels.ClosedChannelException.

          [JENKINS-67034] Unable to connect web start agents after updating to 2.318 from 2.311. "Terminated" after 1 second

          Mark Waite added a comment -

          Please provide enough details so that others can duplicate the failure. I'm running Jenkins 2.318 with an agent connected using "Launch agent by connecting it to the controller" from a Windows 10 agent.

          Are you able to duplicate the failure if you run a test Jenkins instance and connect agents from those nodes to the test instance?

          Mark Waite added a comment - Please provide enough details so that others can duplicate the failure. I'm running Jenkins 2.318 with an agent connected using "Launch agent by connecting it to the controller" from a Windows 10 agent. Are you able to duplicate the failure if you run a test Jenkins instance and connect agents from those nodes to the test instance?

          Daniel Cohen added a comment -

          Good Morning Mark,

          What other information is needed/helpful to diagnose this specific issue? This is the first Jenkins bug I have ran into and reported.

          Also can you elaborate on "Are you able to duplicate the failure if you run a test Jenkins instance and connect agents from those nodes to the test instance?". How am I able to run a test Jenkins instance?

          Thank you very much

          Daniel Cohen added a comment - Good Morning Mark, What other information is needed/helpful to diagnose this specific issue? This is the first Jenkins bug I have ran into and reported. Also can you elaborate on "Are you able to duplicate the failure if you run a test Jenkins instance and connect agents from those nodes to the test instance?". How am I able to run a test Jenkins instance? Thank you very much

          Mark Waite added a comment -

          I can't duplicate the problem based on your description. That likely means there are differences between my environment and your environment. It likely means that one or more of those differences are important to identify the root cause of the problem.

          The description doesn't tell me the configuration you are using. Without that configuration, I can't tell if there are any configuration differences between your environment and mine. The Jenkins support core plugin can generate a detailed report of the configuration of your Jenkins installation, including plugins installed, JDK version that is running, operating system of the controller, operating system of the agents, etc.

          You can upload a support bundle as one way of sharing your configuration. You can describe your configuration in detail (Java version, controller operating system, agent operating system, agent java version, etc.) if you'd rather not upload a support bundle.

          A Jenkins instance can be run on almost any computer with Java 8 or Java 11 available. Download the "war" file from www.jenkins.io/download and type the command "java -jar jenkins.war". Define a Windows agent, connect the Windows agent, and report if there is a failure in that configuration.

          Mark Waite added a comment - I can't duplicate the problem based on your description. That likely means there are differences between my environment and your environment. It likely means that one or more of those differences are important to identify the root cause of the problem. The description doesn't tell me the configuration you are using. Without that configuration, I can't tell if there are any configuration differences between your environment and mine. The Jenkins support core plugin can generate a detailed report of the configuration of your Jenkins installation, including plugins installed, JDK version that is running, operating system of the controller, operating system of the agents, etc. You can upload a support bundle as one way of sharing your configuration. You can describe your configuration in detail (Java version, controller operating system, agent operating system, agent java version, etc.) if you'd rather not upload a support bundle. A Jenkins instance can be run on almost any computer with Java 8 or Java 11 available. Download the "war" file from www.jenkins.io/download and type the command "java -jar jenkins.war". Define a Windows agent, connect the Windows agent, and report if there is a failure in that configuration.

          Piotr Pieta added a comment - - edited

          Hello Mark,

          I've got exactly the same issue, it's I checked it on 2.327 and 2.321 version,s and on both it's failing. For example on 2.312 my node is working correctly. I prefer not to share the support bundle for now, I hope the below details will be enough:

          controller: 

          • java version "1.8.0_271"
          • Microsoft Windows 10 Pro

          node:

          • java version "1.8.0_271"
          • Microsoft Windows 10 Pro

            The interesting thing is that when I do the update from the version that has no issues with connecting Slave to Controller and jenkins-agent.jnlp is on - then after the upgrade, it will also still connected. But when we close it and try to re-run it will gonna fail. Here are the error logs from slave:

          Please let me know it you need any other information regarding the configuration.

          Regards,

          Piotr

          Piotr Pieta added a comment - - edited Hello Mark, I've got exactly the same issue, it's I checked it on 2.327 and 2.321 version,s and on both it's failing. For example on 2.312 my node is working correctly. I prefer not to share the support bundle for now, I hope the below details will be enough: controller:  java version "1.8.0_271" Microsoft Windows 10 Pro node: java version "1.8.0_271" Microsoft Windows 10 Pro The interesting thing is that when I do the update from the version that has no issues with connecting Slave to Controller and jenkins-agent.jnlp is on - then after the upgrade, it will also still connected. But when we close it and try to re-run it will gonna fail. Here are the error logs from slave: Please let me know it you need any other information regarding the configuration. Regards, Piotr

          Piotr Pieta added a comment -

          Actually I tried the batch script approach and it seems to be working fine for me. I'm still wondering what is the reason that .jnlp way doesn't but I've seen here it's not only for me like that https://issues.jenkins.io/browse/JENKINS-67000

          Piotr Pieta added a comment - Actually I tried the batch script approach and it seems to be working fine for me. I'm still wondering what is the reason that .jnlp way doesn't but I've seen here it's not only for me like that  https://issues.jenkins.io/browse/JENKINS-67000

          Allen Johnson added a comment -

          I have the same issue (web start says 'Terminated' about 1 second after starting) when transferring my existing nodes to a new Jenkins server on a new host and trying to upgrade at the same time.

          I finally confirmed that 2.277 (prior version on the old machine) and 2.312 work.  2.318 and 2.333 do not.

          With the newer versions, I can do a command line start using the same deployment files and slave.jar populated by the older version when I installed as a service.  But for permissions reasons I have to have the node run as a local service, so I've reverted to 2.312 until this is resolved.

          Allen Johnson added a comment - I have the same issue (web start says 'Terminated' about 1 second after starting) when transferring my existing nodes to a new Jenkins server on a new host and trying to upgrade at the same time. I finally confirmed that 2.277 (prior version on the old machine) and 2.312 work.  2.318 and 2.333 do not. With the newer versions, I can do a command line start using the same deployment files and slave.jar populated by the older version when I installed as a service.  But for permissions reasons I have to have the node run as a local service, so I've reverted to 2.312 until this is resolved.

          Mark Waite added a comment -

          Closing as a duplicate of JENKINS-67000. The pull request to resolve JENKINS-67000 is merged in the Jenkins core master branch and should arrive in tomorrow Jenkins 2.335 release. It is already described in the changelog pull request.

          Mark Waite added a comment - Closing as a duplicate of JENKINS-67000 . The pull request to resolve JENKINS-67000 is merged in the Jenkins core master branch and should arrive in tomorrow Jenkins 2.335 release. It is already described in the changelog pull request .

            Unassigned Unassigned
            dcohen241 Daniel Cohen
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: