Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
dmitryyu opened this issue Jul 13, 2016 · 3 comments

Comments

@dmitryyu
Copy link
Contributor

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.
@rouke-broersma
Copy link
Member

rouke-broersma commented Jul 22, 2016

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.

@dmitryyu
Copy link
Contributor Author

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

@rouke-broersma
Copy link
Member

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
#95 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADbenNcxQ7GbHvELBVJ2AKY-1qxVA2iIks5qZ-BYgaJpZM4JLTkA
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants