Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

VIC Containers Running Selenium Report "org.openqa.selenium.WebDriverException: connection refused" (53282)

Last Updated: 3/31/2018Categories: TroubleshootingTotal Views: 4125Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

When running Selenium Grid WebDriver test, the driver reports a stack trace with "Caused by: org.openqa.selenium.WebDriverException: connection refused". Reviewing the output of "docker -H VCH_IP_FQDN:2376 --tls logs <Container_Name_ID>" Similar to the following is seen.

16:09:24.743 INFO - The node is registered to the hub and ready to use
2018-03-14 16:15:20.489:INFO:osjshC.ROOT:qtp436546048-12: org.openqa.selenium.remote.server.WebDriverServlet-3ba9ad43: Initialising WebDriverServlet
16:15:20.535 INFO - Found handler: org.openqa.selenium.remote.server.commandhandler.BeginSession@2258a381
16:15:20.541 INFO - /session: Executing POST on /session (handler: BeginSession)
16:15:20.669 INFO - Capabilities are: Capabilities {acceptInsecureCerts: true, browserName: firefox, version: }
16:15:20.673 INFO - Capabilities {acceptInsecureCerts: true, browserName: firefox, version: } matched class org.openqa.selenium.remote.server.ServicedSession$Factory (provider: org.openqa.selenium.firefox.GeckoDriverService)
1521044120746   geckodriver     INFO    geckodriver 0.19.1
1521044120752   geckodriver     INFO    Listening on 127.0.0.1:3377
1521044121064   mozrunner::runner       INFO    Running command: "/usr/bin/firefox" "-marionette" "-profile" "/tmp/rust_mozprofile.lZOama6uW0oN"
Error: Access was denied while trying to open files in your profile directory.
(firefox:350): dconf-CRITICAL **: unable to create directory '/root/.cache/dconf': Permission denied.  dconf will not work properly.

When deploying the debug image "selenium/node-firefox-debug" the VNC console will not connect to the container.

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

The home environment path may not be set for the non-root user used within the container image.

Resolution

Set the HOME environment path manually.

To do this using the docker client add -e HOME=/home/seluser to the create or run command. Below is an example of how to do this when using "docker create" to create the container first.

docker -H VCH_IP_FQDN:2376 --tls create -e HOME=/home/seluser -e HUB_PORT_4444_TCP_ADDR=hub -e
HUB_PORT_4444_TCP_PORT=4444 -e NODE_MAX_INSTANCES=5 -e NODE_X_SESSION=3 -e GRID_MAX_SESSION=10 -it --name FireFoxNodeExample selenium/node-firefox

To do this using docker compose the docker-compose.yml will need the FireFox environment section changed to include - HOME=/home/seluse like shown in the example below. (Note docker-compose.yml is sensitive to the leading space count for each line.)

firefox:
cpu_count: 1
image: "selenium/node-firefox"
environment:
- HOME=/home/seluser
- HUB_PORT_4444_TCP_ADDR=hub
- HUB_PORT_4444_TCP_PORT=4444
- NODE_MAX_INSTANCES=5
- NODE_X_SESSION=3
- GRID_MAX_SESSION=10

There is also an example selenium docker-compose.yml for use with VIC located here

Related Information

More information about running Selenium Grid can be found at Running Selenium Grid on vSphere with vSphere Integrated Containers

A tracking issue is also available in GitHub at Set environment variables from non-root user profiles #7536

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere Integrated Containers

VMware vSphere

Related Versions:

VMware vSphere Integrated Containers 1.x

Take Our Survey

Support Assistant