Critical After upgrading Jenkins from 2.3.16 to 2.3.18 on 1st November 2021, we started facing issue with Windows Agent unable to start. If we try to manually start them, it use to start and then immediately show as terminated. After trying lot of fixes, we had to rollback the version to 2.316 and that seems to have fixed the issue.
So wanted to know, if this a known bug in this release.
[JENKINS-67069] Jenkins windows agent fails to start after update to 2.318
Nikit Shinde
created issue -
Nikit Shinde
made changes -
| Summary | Original: Jenkins windows agent fails to start after update to 2.3.18 | New: Jenkins windows slave agent fails to start after update to 2.3.18 |
Nikit Shinde
made changes -
| Description |
Original:
After upgrading Jenkins from 2.3.16 to 2.3.18 on 1st November 2021, we started facing issue with Windows Agent unable to start. If we try to manually start them, it use to start and then immediately show as terminated. After trying lot of fixes, we had to rollback the version to 2.3.16 and that seems to have fixed the issue.
So wanted to know, if this a known bug in this release. |
New:
After upgrading Jenkins from 2.3.16 to 2.3.18 on 1st November 2021, we started facing issue with Windows slave Agent unable to start. If we try to manually start them, it use to start and then immediately show as terminated. After trying lot of fixes, we had to rollback the version to 2.3.16 and that seems to have fixed the issue.
So wanted to know, if this a known bug in this release. |
Kalle Niemitalo
made changes -
| Component/s | New: remoting [ 15489 ] | |
| Component/s | Original: agent-server-parameter-plugin [ 27422 ] |
We've received other reports that 2.318 was unable to connect Windows agents, but the submitter did not provide enough information so that others could duplicate the problem. Can you share more details that describe the issue in enough detail so that others can duplicate your configuration?
- Where is the controller running (operating system, Java version)?
- Where is the agent running (operating system, Java version)?
- How is the agent launched (batch file, web start, some other method)?
- What plugins are installed on the controller (precise versions)?
- Are there any special details about network configuration that might cause you to see this issue but prevent others from seeing it?
- Are there other details that might make your Jenkins installation different from other Jenkins installations?
| Summary | Original: Jenkins windows slave agent fails to start after update to 2.3.18 | New: Jenkins windows slave agent fails to start after update to 2.318 |
| Summary | Original: Jenkins windows slave agent fails to start after update to 2.318 | New: Jenkins windows agent fails to start after update to 2.318 |
| Description |
Original:
After upgrading Jenkins from 2.3.16 to 2.3.18 on 1st November 2021, we started facing issue with Windows slave Agent unable to start. If we try to manually start them, it use to start and then immediately show as terminated. After trying lot of fixes, we had to rollback the version to 2.3.16 and that seems to have fixed the issue.
So wanted to know, if this a known bug in this release. |
New:
After upgrading Jenkins from 2.3.16 to 2.3.18 on 1st November 2021, we started facing issue with Windows Agent unable to start. If we try to manually start them, it use to start and then immediately show as terminated. After trying lot of fixes, we had to rollback the version to 2.316 and that seems to have fixed the issue.
So wanted to know, if this a known bug in this release. |
SeungWook Yoon
added a comment -
2022-02-04 04:58:25.594+0000 [id=381] INFO h.TcpSlaveAgentListener$ConnectionHandler#run: Connection #13 failed: java.io.EOFException 2022-02-04 04:58:25.631+0000 [id=382] INFO h.TcpSlaveAgentListener$ConnectionHandler#run: Accepted JNLP4-connect connection #14 from /****:13848 2022-02-04 04:58:26.710+0000 [id=336] INFO j.s.DefaultJnlpSlaveReceiver#channelClosed: Computer.threadPoolForRemoting [#181] for buildserver_59 terminated: java.nio.channels.ClosedChannelException 2022-02-04 04:58:26.712+0000 [id=332] INFO hudson.remoting.Request$2#run: Failed to send back a reply to the request UserRequest:UserRPCRequest:hudson.remoting.JarLoader.writeJarTo[long,long,java.io.OutputStream](3): hudson.remoting.ChannelClosedException: Channel "hudson.remoting.Channel@44b318c9:JNLP4-connect connection from ****/****:13848": channel is already closed
This error message is shown in jenkins.err.log when I try to connect with .jnlp file.
I'm using JDK 1.8.0_202 on windows for both jenkins master(controller) and slave agent.
Connection is stable when agent is started as service, but it is terminated immediately after connected if I start agent by running .jnlp file.
As the log shows, I believe this error is about remoting 4.11 update included in jenkins 2.317.
Hope this bug is fixed soon
SeungWook Yoon
added a comment -
2022-02-04 04:58:25.594+0000 [id=381] INFO h.TcpSlaveAgentListener$ConnectionHandler#run: Connection #13 failed: java.io.EOFException
2022-02-04 04:58:25.631+0000 [id=382] INFO h.TcpSlaveAgentListener$ConnectionHandler#run: Accepted JNLP4-connect connection #14 from /****:13848
2022-02-04 04:58:26.710+0000 [id=336] INFO j.s.DefaultJnlpSlaveReceiver#channelClosed: Computer.threadPoolForRemoting [#181] for buildserver_59 terminated: java.nio.channels.ClosedChannelException
2022-02-04 04:58:26.712+0000 [id=332] INFO hudson.remoting.Request$2#run: Failed to send back a reply to the request UserRequest:UserRPCRequest:hudson.remoting.JarLoader.writeJarTo[ long , long ,java.io.OutputStream](3): hudson.remoting.ChannelClosedException: Channel "hudson.remoting.Channel@44b318c9:JNLP4-connect connection from ****/****:13848" : channel is already closed
This error message is shown in jenkins.err.log when I try to connect with .jnlp file.
I'm using JDK 1.8.0_202 on windows for both jenkins master(controller) and slave agent.
Connection is stable when agent is started as service, but it is terminated immediately after connected if I start agent by running .jnlp file.
As the log shows, I believe this error is about remoting 4.11 update included in jenkins 2.317.
Hope this bug is fixed soon
In your production environment, it would be safer to run only LTS releases of Jenkins.
Between 2.316 and 2.318, Remoting was upgraded to address
JENKINS-61212andJENKINS-64831. That might be related.Anyway, the log files of the agents may indicate what the problem is.