Details
-
New Feature
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Fixed
Description
In Jenkins projects we have many users complaining that the slave/agent is "already connected", because they have a runaway slave/agent process. It happens when WinSW gets terminated without executing the process shutdown logic (force kill) or when WinSW fails to terminate the process.
As a part of WinSW 2.0, it would be great to create a logic, which...
- records PID of the created process to the disc
- performs status check of the previously spawned process upon restart
- terminates the runaway process if required
It can be done via WinSW 2 "plugin"
Issue: https://github.com/kohsuke/winsw/issues/125
Attachments
Issue Links
- is duplicated by
-
JENKINS-29825 some windows agents unable to reconnect after master restart
-
- Resolved
-
- is related to
-
JENKINS-24155 Jenkins Slaves Go Offline In Large Quantities and Don't Reconnect Until Reboot
-
- Open
-
-
JENKINS-28492 The server rejected the connection: *** is already connected to this master. Rejecting this connection.
-
- Resolved
-
-
JENKINS-26020 Will not start builds even though there are available slots on executor
-
- Resolved
-
-
JENKINS-22024 Windows "services" shows Jenkins as not running.. but it is.
-
- Resolved
-
- links to
Jenkins master is on 2.32.1
Master and slaves running Win2012
The symptoms sound very familiar to a problem where we've had a jenkins slave up.... then we reboot the windows server (slave).
When the server returns and the slave is automatically started, it hangs around for about 30secs then terminates connection which kills our job.
We've also witnessed the hosting windows service winsw 1.17 (which auto upgrades to 1.18) bombs out but leaves the java process running.
The java process is still keeping the slave active to the master for an indiscriminate amount of time (anywhere between 20secs to 2hrs) before eventually dying of its own accord, with no fresh jobs sent or interaction with the windows service.