While running automation in webdriver standalone server, i get this exception randomly. Once it comes, I killed all java process . So what is the solution for this exception ? Why it comes randomly ?
Unfortunately as far as i know, all have suggested to use latest version of selenium jar or come compatible firefox version depending on the selenium version or they have said to check if that port is on use (though it won't!) or reboot system.Few have suggested to uninstall firefox version and reinstall it. Any permanent solution or any idea why it comes?
org.openqa.selenium.WebDriverException: Unable to bind to locking port 7054 within 45000 ms
Build info: version: '2.30.0', revision: 'dc1ef9c', time: '2013-02-19 00:15:27'
System info: os.name: 'Windows 7', os.arch: 'x86', os.version: '6.1', java.version: '1.7.0'
Driver info: driver.version: FirefoxDriver
Command duration or timeout: 47.94 seconds
Build info: version: '2.28.0', revision: '18309', time: '2012-12-11 15:53:30'
System info: os.name: 'Windows 7', os.arch: 'x86', os.version: '6.1', java.version: '1.7.0'
Driver info: org.openqa.selenium.remote.RemoteWebDriver
Seems like previous webDriver instance (or something else) didn't release the port. Here is workaround (bad practice) for this problem (Java):
public static FirefoxBrowser forceInit() {
try {
return new FirefoxBrowser();
} catch (WebDriverException exc) {
return forceInit();
}
}
Make sure your tests close driver correctly by:
driver.quit();
Make sure that you don't have any WebDriver Firefox windows open!
Although the issue/question is from quite some time, I faced same one today on Windows environment. I manage to resolve it with a simple machine reboot.
I encourage you to do this first before everything else.
OS Windows 7
selenium-server version : 2.35.0
I had the same issue with firefox 47.0 and selenium-webdriver 2.45.1 on fedora 23. The problem was fixed by using firefox version 41. (Version 42 was tested and worked as well.) To install ff41 on fedora using a terminal run:
dnf install firefox-41.0.1-2.fc23
Just in case it could help someone, I solved this error removing any reference to localhost from my hosts file in Windows (I'm executing the tests remotely from Linux to Windows)
Kill firefox by going to Task Manager, this may help.
Related
I need help running Katalon studio with Chrome portable.
I am using ChromeDriver 75.0.3770.90 and Chrome Portable Version 75.0.3770.100 which I downloaded from portableapps.com
I have configured Katalon studio to use the portable version as seen in the screenshot below:
When I run the Katalon tests or try to record, the webdriver throws the following error:
Caused by: org.openqa.selenium.WebDriverException: unknown error: Failed to create a Chrome process.
Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:25:53'
System info: host: 'JHBPWM467086', ip: '10.110.43.144', os.name: 'Windows 7', os.arch: 'amd64', os.version: '6.1', java.version: '1.8.0_181'
Driver info: driver.version: CChromeDriver
I have tried running Katalon as an admin and I have tried different supported Chrome drivers and I get the same error.
Is it possible to use Katalon with portable chrome ? If so, what configuration items am I missing to get it working ?
Thank you in advance for any help. Please let me know if I can clarify anything.
Katalon is unable to find the browser. You will need to set path to chromedriver manually:
System.setProperty("webdriver.chrome.driver", "path-to\chromedriver.exe")
So I have VM with Ubuntu on it. The host is on Win10. Inside this VM I installed a docker where I pulled jenkins and installed selenium plugin for jenkins.
I could reached a selenium node from win10. But when I try to launch a test from my IDE :
val cap: DesiredCapabilities = DesiredCapabilities.chrome()
cap.setBrowserName("chrome")
webDriver = new RemoteWebDriver(new URL("http://192.168.10.223:4445/wd/hub/"), cap)
go to "https://www.google.com"
I have this error and i don't understand why...
Exception encountered when invoking run on a nested suite - Unable to create new service: ChromeDriverService
Build info: version: '3.12.0', revision: '7c6e0b3', time: '2018-05-08T15:15:08.936Z'
System info: host: '2d3135afb490', ip: '172.17.0.2', os.name: 'Linux', os.arch: 'amd64', os.version: '4.15.0-24-generic', java.version: '1.8.0_171'
Driver info: driver.version: unknown
Command duration or timeout: 101 milliseconds
Am I doing something wrong ? or am I missing some configuration ?
Docker Containers do not have a Desktop(and your selenium process is running inside such a container if I udnerstood it right) so they will not run UI tests. Your chances are:
Use PhantomJS Driver. This is a browser that won't render anything and does not need a Desktop. Disclaimer: Tried it in Headless(Desktopless) sessions but not on Docker
Try to Hack your Docker image and create an X Desktop Session.
I searched and found very similar mentions in older questions from several months ago which seemed to suggest problem should have been fixed by now, but it is still occurring for me.
Pytest on my Linux server - Build info: version: '3.0.1', revision: '1969d75', time: '2016-10-18 09:48:19 -0700'
Firefox on my remote Win7 laptop - browserVersion 50.0.2
Geckodriver on my remote Win7 laptop - geckodriver-v0.11.1-win64 .
System info: host: 'XXXXXXXXX', ip: 'XXX.XXX.XXX.XXX', os.name: 'Windows 7', os.arch: 'x86', os.version: '6.1', java.version: '1.8.0_111'
Driver info: org.openqa.selenium.firefox.FirefoxDriver
Geckodriver on my Linux server in my $PATH - geckodriver-v0.11.1-linux64.tar
My pytest+selenium session opens a browser window on my remote laptop OK, and does everything properly until the test completes. At that point, Firefox crashes and the remote Geckodriver reports "[Child 1688] ###!!! ABORT: Aborting on channel error.: file c:/builds/moz2_slave/m-rel-w32-00000000000000000000/build/src/ipc/glue/MessageChannel.cpp, line 2056".
I would appreciate any & all suggestions or guidance so Firefox does not end up crashing. Thank you very much.
Im currently on Yosemite and Safari 8.
I keep getting this error:
Caused by: org.openqa.selenium.remote.UnreachableBrowserException: Failed to connect to SafariDriver after 10161 ms
Build info: version: '2.44.0', revision: '76d78cf', time: '2014-10-23 20:02:37'
System info: host: 'TODIGWS000993.local', ip: 'xx.xx.xx.xx', os.name: 'Mac OS X', os.arch: 'x86_64', os.version: '10.10.1', java.version: '1.8.0_25'
Driver info: driver.version: SafariDriver
at org.openqa.selenium.safari.SafariDriverCommandExecutor.start(SafariDriverCommandExecutor.java:124)
at org.openqa.selenium.safari.SafariDriver.startClient(SafariDriver.java:72)
at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:114)
at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:139)
at org.openqa.selenium.safari.SafariDriver.<init>(SafariDriver.java:58)
at org.openqa.selenium.safari.SafariDriver.<init>(SafariDriver.java:51)
... 14 more
18:42:43.408 WARN - Exception: Failed to connect to SafariDriver after 10161 ms
Build info: version: '2.44.0', revision: '76d78cf', time: '2014-10-23 20:02:37'
System info: host: 'TODIGWS000993.local', ip: 'xx.xx.xx.xx', os.name: 'Mac OS X', os.arch: 'x86_64', os.version: '10.10.1', java.version: '1.8.0_25'
Driver info: driver.version: SafariDriver
I am setting up my own grid and I'm using the standalone jar files (2.44.0). I am running the hub and node via daemons using launchd and a .plist file for each respectively.
All other browsers (FF and Chrome) load and run the tests fine.
I followed the instructions listed by
https://code.google.com/p/selenium/issues/detail?id=7933#c33
and successfully, manually, installed webdriver extension into the safari 8 browser
Initially when running selenium jars via daemons this did not work. But when i stopped the daemons and ran the jars (with the same arguments) using the logged in user the safari driver error went away and the safari browser loaded and ran the test.
I have tried with the argument
-Dwebdriver.safari.noinstall=true
but still no progress.
Have also set the daemon to have the same env variables as the logged in user that did successfully run the test but this also did not work.
Basically, the same command works when ran via the logged in user but not via a daemon. Any help will be greatly appreciated.
/usr/bin/java -jar /usr/lib/selenium/selenium-server-standalone-2.44.0.jar -port 5555 -role node -hub http://localhost:4444/grid/register -nodeConfig /usr/lib/selenium-code/osx/node_config.json -Dwebdriver.chrome.driver=/usr/lib/selenium/chromedriver
Build info: version: '2.44.0', revision: '76d78cf', time: '2014-10-23 20:02:37'
System info: host: 'TODIGWS000993.local', ip: 'xxxxxxxx', os.name: 'Mac OS X', os.arch: 'x86_64', os.version: '10.10.1', java.version: '1.8.0_25'
safari 8
Here are the logs from the safari driver:
18:40:41.78 [safaridriver.extension] Creating global session...
18:40:41.78 [safaridriver.extension.TabManager] Registering new tab
18:40:41.78 [safaridriver.extension.TabManager] Set command tab to hncoksu5irc9
18:40:41.78 [safaridriver.extension] Creating debug driver...
18:40:41.78 [safaridriver.extension] Waiting for connect command...
18:43:04.20 [safaridriver.extension.TabManager] Registering new tab
18:43:04.20 [safaridriver.extension.TabManager] Tab opened: wgoy5x4bmbnw
18:43:04.34 [safaridriver.extension.TabManager] Ignoring open window event
18:43:04.34 [safaridriver.extension.TabManager] Deleting entry for tab wgoy5x4bmbnw
18:43:04.89 [safaridriver.extension.Server] [wi8mei4r9u3q] Executing command: newSession
Thanks
I was facing the similar issue: createDriver
org.openqa.selenium.remote.UnreachableBrowserException: Failed to connect to SafariDriver after 10342 ms
To get it resolved after trying some things, I registered myself at the Apple Site for “Safari Developer Program” and generated a certificate to use in Safari. Installed the certificate in my Key-chain and added the Safari Extension to the browser.
Can refer the site for steps to proceed: https://rationaleemotions.wordpress.com/2012/05/25/working-with-safari-driver/
I am using software configurations like:
Selenium: selenium-server-standalone-2.43.1.jar
Safari: 7.1.3
Mac: 10.9.5
Even tested on latest Selenium 2.44.0 and Safari 8.0. This approach works.
im trying to get a bunch of selenium tests to work on my Jenkins. Its an Ubuntu machine and i installed Chromedriver Chromium and xvfb.
After some problems it seems like its finding my chromedriver and the xfvb now but i still cant get any tests to run. They work fine local but now on Jenkins it says :
Fehlermeldung
Timed out after 5 seconds waiting for visibility of element located by By.xpath: //*[#id='loginForm-loginUsernameInput']
Build info: version: '2.25.0', revision: '17482', time: '2012-07-18 21:09:54'
System info: os.name: 'Linux', os.arch: 'amd64', os.version: '3.13.0-39-generic', java.version: '1.7.0_67'
Driver info: driver.version: unknown
Stacktrace
org.openqa.selenium.TimeoutException: Timed out after 5 seconds waiting for visibility of element located by By.xpath: //*[#id='loginForm-loginUsernameInput']
Build info: version: '2.25.0', revision: '17482', time: '2012-07-18 21:09:54'
System info: os.name: 'Linux', os.arch: 'amd64', os.version: '3.13.0-39-generic', java.version: '1.7.0_67'
Driver info: driver.version: unknown
at org.openqa.selenium.support.ui.FluentWait.timeoutException(FluentWait.java:255)
at org.openqa.selenium.support.ui.FluentWait.timeoutException(FluentWait.java:270)
at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:222)
Im wondering why it doesnt show the chromedriver Version? Like version unknown? Im running the xvfb and the chromedriver in the background and im not using Jenkins to start it. I tried it with letting Jenkins start chromedriver and set the path -Dwebdriver.chrome.path=
but that results in the same error. Does anyone have a idea about this? I tried quite a few things but im still wondering if its the chromedriver that is not working or whats the Problem? Im using ChromeDriver v2.9.248304
You are using a very outdated version of Selenium. Typically, the newer Chrome versions might not work with older version of Selenium.
Try updating to Selenium version 2.44.0
I'm willing to bet this will fix your issue.