-
New Feature
-
Resolution: Fixed
-
Major
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
- 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