Software Quality Assurance & Testing Stack Exchange is a question and answer site for software quality control experts, automation engineers, and software testers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I tried to set up a Selenium Grid node on a virtual machine. I am using VirtualBox for the VM and Jenkins (with VirtualBox plugin) to set up the grid. When I try to register the node, I get the following errors:

<===[JENKINS REMOTING CAPACITY]===>channel started
Slave.jar version: 2.20
This is a Unix slave
Copied maven-agent.jar
Copied maven3-agent.jar
Copied maven3-interceptor.jar
Copied maven-interceptor.jar
Copied maven2.1-interceptor.jar
Copied plexus-classworld.jar
Copied classworlds.jar
Evacuated stdout
Starting Selenium Grid nodes on Ubuntu 1
is running
Copy grid jar
Creating selenium VM
Starting Selenium RC
$ /usr/lib/jvm/java-7-openjdk-i386/jre/bin/java -cp /home/ubuntu/~/Desktop/Jenkins/slave.jar hudson.remoting.Launcher -cp /home/ubuntu/~/Desktop/Jenkins/~/Desktop/Jenkins/selenium-server-standalone-2.25.0.jar -connectTo localhost:38497
channel started
Starting the selenium process
adding seleniumProtocol=WebDriver,browserName=firefox,maxInstances=1,version=16.01
Slave successfully connected and online
[VirtualBox] Stage 2 launcher completed
Jan 08, 2013 4:27:42 PM org.openqa.grid.internal.utils.SelfRegisteringRemote startRemoteServer
WARNING: error getting the parameters from the hub. The node may end up with wrong timeouts.Connection to http://localhost:4444 refused
16:27:42.373 INFO - Java: Oracle Corporation 23.2-b09
16:27:42.381 INFO - OS: Linux 3.5.0-17-generic i386
16:27:42.393 INFO - v2.25.0, with Core v2.25.0. Built from revision 17482
16:27:43.015 INFO - RemoteWebDriver instances should connect to:
16:27:43.025 INFO - Version Jetty/5.1.x
16:27:43.029 INFO - Started HttpContext[/selenium-server/driver,/selenium-server/driver]
16:27:43.032 INFO - Started HttpContext[/selenium-server,/selenium-server]
16:27:43.033 INFO - Started HttpContext[/,/]
16:27:43.121 INFO - Started org.openqa.jetty.jetty.servlet.ServletHandler@781ecc
16:27:43.122 INFO - Started HttpContext[/wd,/wd]
16:27:43.141 INFO - Started SocketListener on
16:27:43.141 INFO - Started org.openqa.jetty.jetty.Server@1997447
16:27:43.144 INFO - using the json request : {"class":"org.openqa.grid.common.RegistrationRequest","capabilities":[{"platform":"LINUX","seleniumProtocol":"WebDriver","browserName":"firefox","maxInstances":"1","jenkins.nodeName":"Ubuntu 1","version":"16.01"}],"configuration":{"port":4444,"host":"","hubHost":"localhost","registerCycle":5000,"hub":"http://localhost:4444/grid/register","url":"","remoteHost":"","register":true,"proxy":"org.openqa.grid.selenium.proxy.DefaultRemoteProxy","maxSession":5,"browser":"seleniumProtocol=WebDriver,browserName=firefox,maxInstances=1,version=16.01","role":"node","hubPort":4444}}
16:27:43.154 INFO - starting auto register thread. Will try to register every 5000 ms.
16:27:43.154 INFO - Registering the node to hub :http://localhost:4444/grid/register
16:27:43.341 INFO - couldn't register this node : Error sending the registration request.
16:27:48.348 INFO - couldn't register this node : hub down or not responding.
16:27:53.360 INFO - couldn't register this node : hub down or not responding.
16:27:58.367 INFO - couldn't register this node : hub down or not responding.

Interestingly, the node still comes online and is shown as matching the Selenium node configuration I have set up. I can start it as a Selenium node and everything. However, when I try to run Selenium tests with it via the WebDriver, that machine is not recognized as part of my pool.

Also, when only that node is started on the Jenkins Selenium plugin, the following message (which is normally displayed when NO Selenium nodes are started) displays:

**Registered Remote Controls**

Selenium Grid is running at localhost:4444. Selenium 1 clients should connect as follow: Selenium selenium = new DefaultSelenium("localhost", 4444, "*firefox", ""); Selenium 2 clients should connect as follow: WebDriver driver = new RemoteWebDriver(new URL("http://localhost:4444/wd/hub"), capability); No RCs have checked in yet. Have you started some slaves?
share|improve this question

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.