selenium-plugin icon indicating copy to clipboard operation
selenium-plugin copied to clipboard
verified publisher icon jenkinsci

selenium node can't be restarted/started if java process is killed on jenkins node.

Open dmitryyu opened this issue 9 years ago • 3 comments

How to reproduce:

  1. start selenium plugin with 2 jenkins/grid nodes.
  2. go to jenkins node, find and kill "java process" that has been started as grid node
  3. go to jenkins and try to start/restart grid node As a result status "error" is displayed and node cannot be started.

dmitryyu avatar Jul 13 '16 11:07 dmitryyu

I'm not sure if there is any way to check the heartbeat of the node process on the slave machine, and I don't think there is anything that checks if the actual process is still running currently. Because of that I don't think this is a bug, more like a feature request. It is a good feature to have, but I do not know when if ever I am going to have time for something like this.

rouke-broersma avatar Jul 22 '16 20:07 rouke-broersma

I guess just verification that node port is still busy can help to do it.

dmitryyu avatar Jul 27 '16 22:07 dmitryyu

If you could help to fix it that would be appreciated yes.

On Thu, Jul 28, 2016, 00:48 dmitryyu [email protected] wrote:

I guess just verification that node port is still busy can help to do it.

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/jenkinsci/selenium-plugin/issues/95#issuecomment-235745357, or mute the thread https://github.com/notifications/unsubscribe-auth/ADbenNcxQ7GbHvELBVJ2AKY-1qxVA2iIks5qZ-BYgaJpZM4JLTkA .

rouke-broersma avatar Jul 28 '16 04:07 rouke-broersma