Quantcast

[JIRA] (JENKINS-14856) Slave Registered Remote Controls not identified in Jenkins Selenium Grid

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-14856) Slave Registered Remote Controls not identified in Jenkins Selenium Grid

JIRA noreply@jenkins-ci.org
Issue Type: Bug Bug
Affects Versions: current
Assignee: Kohsuke Kawaguchi
Components: selenium
Created: 17/Aug/12 8:20 PM
Description:

I was attempting to rename the newest selenium-server-standalone-*.jar to replace the older one (as per some of the users posts).
When I restarted the Jenkins server, the Selenium Grid page shows that the jenkins.nodeName is null for all of the connected remote contols clients (as shown below)

{seleniumProtocol=Selenium, browserName=*firefox, maxInstances=5, jenkins.nodeName=}

I put everything back the way it was, but this problem still exists, and the process for the hudson.remoting.Launcher of the selenium-server-standalone-*.jar is not running on the agents.

Everything says that it should automatically configure and start when the Jenkins server is restarted.

Environment: Linux RHEL server
Linux Ubuntu slave agent remote client
Project: Jenkins
Priority: Major Major
Reporter: rejesi
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-14856) Slave Registered Remote Controls not identified in Jenkins Selenium Grid

JIRA noreply@jenkins-ci.org

Does that happen when using the latest 2.2 version ?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-14856) Slave Registered Remote Controls not identified in Jenkins Selenium Grid

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
Change By: Richard Lavoie (08/Sep/12 1:48 PM)
Assignee: Kohsuke Kawaguchi Richard Lavoie
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-14856) Slave Registered Remote Controls not identified in Jenkins Selenium Grid

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
rejesi closed Bug JENKINS-14856 as Cannot Reproduce

Closing this issue as it was probably user error.

Change By: rejesi (17/Jan/13 6:56 PM)
Status: Open Closed
Resolution: Cannot Reproduce
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-14856) Slave Registered Remote Controls not identified in Jenkins Selenium Grid

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
rejesi commented on Bug JENKINS-14856

I believe that somehow it was user error. It resolved and started showing properly after a week or so. I have since stopped using this plugin.

I will close this issue.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Loading...