0

I'm having trouble running the automation project on a recently installed Jenkins on a Ubuntu server. I'm having the following error:

Selenium::WebDriver::Error::WebDriverError: unable to obtain stable firefox connection in 60 seconds (127.0.0.1:7055)
/var/lib/gems/2.3.0/gems/selenium-webdriver-2.53.0/lib/selenium/webdriver/firefox/launcher.rb:90:in `connect_until_stable'
/var/lib/gems/2.3.0/gems/selenium-webdriver-2.53.0/lib/selenium/webdriver/firefox/launcher.rb:55:in `block in launch'
/var/lib/gems/2.3.0/gems/selenium-webdriver-2.53.0/lib/selenium/webdriver/common/socket_lock.rb:43:in `locked'
/var/lib/gems/2.3.0/gems/selenium-webdriver-2.53.0/lib/selenium/webdriver/firefox/launcher.rb:51:in `launch'
/var/lib/gems/2.3.0/gems/selenium-webdriver-2.53.0/lib/selenium/webdriver/firefox/bridge.rb:43:in `initialize'
/var/lib/gems/2.3.0/gems/selenium-webdriver-2.53.0/lib/selenium/webdriver/common/driver.rb:53:in `new'
/var/lib/gems/2.3.0/gems/selenium-webdriver-2.53.0/lib/selenium/webdriver/common/driver.rb:53:in `for'
/var/lib/gems/2.3.0/gems/selenium-webdriver-2.53.0/lib/selenium/webdriver.rb:84:in `for'
/var/lib/gems/2.3.0/gems/watir-webdriver-0.9.1/lib/watir-webdriver/browser.rb:46:in `initialize'
/var/lib/jenkins/workspace/JobScience/lib/New_Automation/Test/test_basic.rb:15:in `new'
/var/lib/jenkins/workspace/JobScience/lib/New_Automation/Test/test_basic.rb:15:in `setup'

I've read that I should update the selenium-webdriver gem, but I have it up to date. Also installed the firefox plugins in jenkins and still not working.

Chuck van der Linden
  • 6,660
  • 2
  • 28
  • 43
elcharrua
  • 1,582
  • 6
  • 30
  • 50

4 Answers4

3

If you just search SO for "Jenkins unable to obtain stable firefox connection in 60 seconds" you will find that this is a fairly common problem. You will also see that it can be caused by a number of things.

  • Versioning conflict between FF and Webdriver: (most common) usually because you are not running latest version of firefox, and/or using latest selenium-webdriver gem.
  • Permissions issue: account being used by jenkins on the executor system does not have permission to actually execute firefox. If you are testing this by logging into the executor system manually be sure you are using the same user that Jenkins does.
  • No display: caused because most jenkins executors run headless. You may need to set an environment variable such as export DISPLAY=:0, or run a program like XVFB (a virtual frame buffer), or use the headless gem (which wraps XVFB), so firefox doesn't balk at the lack of a display.

A good initial troubleshooting step is to alter your jenkins script to just have it try to launch firefox itself (not via webdriver), If it runs, then that typically rules out permissions or headless issues, so the issue is between webdriver and firefox. If you get an error, it will likely indicate if the problem is permissions, or lack of a display.

You basically need to eliminate all the possible causes for this issue, which as your search will reveal there are many potential causes and solutions for this. Here's a small sample (yes, each of these is a different SO question, despite the nearly identical titles):

Community
  • 1
  • 1
Chuck van der Linden
  • 6,660
  • 2
  • 28
  • 43
  • How can I check the jenkins has permission execute permission (I'm new to ubuntu). – elcharrua Apr 29 '16 at 17:19
  • generally I'd say get one of your dev-ops type folks to assist you with this (or whoever administers Jenkins) You should be able to script the appropriate linux command to check the permissions on firefox for the logged in user. I'm far from a *nix expert, or I – Chuck van der Linden Apr 29 '16 at 21:37
  • Edited the answer to include link to another new example of this issue, also added a good troubleshooting step I was reminded of. – Chuck van der Linden May 05 '16 at 20:30
1

I'm not familiar with the Firefox plugin, you shouldn't need it, and it might be causing the conflicts. Watir uses Selenium which looks for any firefox executable in your path. Make sure Firefox 45 is present on your Ubuntu system in a folder that is listed in $PATH, and Selenium will connect to it.

titusfortner
  • 4,099
  • 2
  • 15
  • 29
  • the Firefox is installed correctly, becuase when I run the test manually on the server it launches the firefox driver and runs the test. But when the test is ran on jenkins the error persists – elcharrua Apr 29 '16 at 17:18
1

In my experience this is a versioning issue, I've settling on using Firefox 33.0

https://ftp.mozilla.org/pub/firefox/releases/

James Eldridge
  • 41
  • 1
  • 5
0

As Chuck van der Linden says

You basically need to eliminate all the possible causes for this issue, which as your search will reveal there are many potential causes and solutions for this.

Then i try to do it Firefox can`t get access to display. Check your Jenkins and(or) Selenium started as service or like program from kde, unity, etc?

whitediver
  • 462
  • 3
  • 12