On Monday, May 5, 2014 2:26:19 PM UTC-7, Kevin Fleming wrote: > > Unfortunately it's not possible to reconnect to an SSH session; if the > session is disconnected, the SSH daemon on the receiving end will close its > end, and kill any processes that had been launched by that connection. In > other words, any job that was running will be lost. >
Fair enough. If the ssh session is disconnected, the existing job shall be terminated and the slave appears offline. It appears Jenkins has the ability to automatically reconnect via SSH (bring the slave online) but is blocked. Subsequent attempts to reconnect manually will then fail as well until a server restart -- even if the slave is accessible via PuTTy. It would be nice to be able to figure out how these SSHLauncher threads were spawned in the first place, the root cause of the blocked threads, and how to recover from the incident after. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
