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

          Daniel Cohen created issue -
          Daniel Cohen made changes -
          Description Original: 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. When I check the specific node on the nodes menu in Jenkins is states: terminated: java.nio.channels.ClosedChannelException. New: 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.
          Daniel Cohen made changes -
          Issue Type Original: Task [ 3 ] New: Bug [ 1 ]
          Alex Earl made changes -
          Summary Original: Unable to Connect to Nodes after updating to 2.318 from 2.311. Slave Agent Connects for About 1 Second Before "Terminated" New: Unable to Connect to Nodes after updating to 2.318 from 2.311. Agent Connects for About 1 Second Before "Terminated"

          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
          Daniel Cohen made changes -
          Priority Original: Blocker [ 1 ] New: Critical [ 2 ]

          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 made changes -
          Attachment New: image-2022-01-04-12-24-23-020.png [ 57034 ]
          Piotr Pieta made changes -
          Attachment New: image-2022-01-04-12-39-39-451.png [ 57035 ]

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

              Created:
              Updated:
              Resolved: