• Type: Bug
• Resolution: Unresolved
• Priority: Major
• Component/s: core
• Labels:

  • service
  • slave
  • windows
• Environment:

  Jenkins 1.495 -> 1.506

[JENKINS-17246] Windows agents die on Jenkins update

Alex Vesely created issue - 2013-03-18 06:00

Daniel Beck made changes - 2014-05-25 20:43

Resolution		New: Incomplete [ 4 ]
Status	Original: Open [ 1 ]	New: Resolved [ 5 ]

Oleg Nenashev made changes - 2014-05-25 21:44

Resolution	Original: Incomplete [ 4 ]
Status	Original: Resolved [ 5 ]	New: Reopened [ 4 ]

R. Tyler Croy made changes - 2016-07-25 23:53

Workflow

Original: JNJira [ 148079 ]

New: JNJira + In-Review [ 186114 ]

Alex Earl made changes - 2022-07-28 13:58

Summary

Original: Windows slaves die on Jenkins update

New: Windows agents die on Jenkins update

Alex Earl made changes - 2022-07-28 13:59

Description

Original: I have multiple Windows slaves that are being launched as services. When I updated Jenkins from 1.495 to 1.506, all the slaves died - they just failed to launch, even though they did it without issues during regular Jenkins restarts. In order to bring the slaves back to life, I had to remove the services from each Windows host ("sc delete jenkinsslave..."), manually remove the slave directory (containing the .jars and .exe), and then create the service from scratch. If I skip any of the described steps, the slave fails to launch. Slaves are running Windows 2003 Server and Windows 2008 Server, the behavior is identical.

New: I have multiple Windows agents that are being launched as services. When I updated Jenkins from 1.495 to 1.506, all the slaves died - they just failed to launch, even though they did it without issues during regular Jenkins restarts. In order to bring the agents back to life, I had to remove the services from each Windows host ("sc delete jenkinsslave..."), manually remove the agent directory (containing the .jars and .exe), and then create the service from scratch. If I skip any of the described steps, the agent fails to launch. Agents are running Windows 2003 Server and Windows 2008 Server, the behavior is identical.