Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WebDriverException: Session was terminated due to TIMEOUT. Grid v2.50.0 #1557

Closed
enivid opened this issue Jan 28, 2016 · 15 comments
Closed

WebDriverException: Session was terminated due to TIMEOUT. Grid v2.50.0 #1557

enivid opened this issue Jan 28, 2016 · 15 comments

Comments

@enivid
Copy link

enivid commented Jan 28, 2016

I upgraded my grid from v2.48.2 to v2.50.0 and now 50% of my tests will get the TIMEOUT error. This is happening on Linux with FF. I have not tried other browsers yet.

I also noticed that if you set the "timeout" option in your node.json file, it gets ignored. Also tried to pass it in through the command line and it was also ignored. This works perfectly fine in v2.48.2.

@lindavz28
Copy link

👍 We've just encountered this as well. Bug from 2.49.0 possibly re-introduced?

@Dillenger69
Copy link

Same happens to me in both Firefox and Chrome. Had to revert to 2.47.1 and Firefox 41 to get my tests to run.

@nixsec
Copy link

nixsec commented Jan 29, 2016

We've also ran into this issue and had to revert to 2.48.x

@lukeis
Copy link
Member

lukeis commented Jan 29, 2016

2.50.1 has been released

@lindavz28
Copy link

@lukeis 👍 Thanks for that!

@lukeis
Copy link
Member

lukeis commented Jan 30, 2016

going to mark this issue closed/fixed. Feel free to comment if that's not the case and you have steps to reproduce any continued error.

@bizmate
Copy link

bizmate commented Sep 7, 2016

i have this problem in both 2.52 and 2.53. Using the docker images at https://hub.docker.com/r/selenium/hub/tags/

Error example

[2016-09-07 23:20:01] app.CRITICAL: Crawler: WebDriverException failed to fetch url due to message: Session [db903e26-4268-45d9-986c-0aced411ef6f] was terminated due to TIMEOUT
[2016-09-07 23:20:01] app.CRITICAL: Crawler: WebDriverException trace: #0 /var/www/sitecrawler/symfony3/vendor/facebook/webdriver/lib/Remote/HttpCommandExecutor.php(287): Facebook\WebDriver\Exception\WebDriverException::throwException(13, 'Session [db903e...', Array) #1 /var/www/sitecrawler/symfony3/vendor/facebook/webdriver/lib/Remote/RemoteWebDriver.php(508): Facebook\WebDriver\Remote\HttpCommandExecutor->execute(Object(Facebook\WebDriver\Remote\WebDriverCommand)) #2 /var/www/sitecrawler/symfony3/vendor/facebook/webdriver/lib/Remote/RemoteWebDriver.php(187): Facebook\WebDriver\Remote\RemoteWebDriver->execute('get', Array) #3 /var/www/sitecrawler/symfony3/src/Bizmate/SiteCrawlerBundle/Service/Crawler/EmailCrawler.php(208): Facebook\WebDriver\Remote\RemoteWebDriver->get('http://andressa...') ...

I have the problem only when using Firefox apparently

$this->driver = RemoteWebDriver::create($host, DesiredCapabilities::firefox(), 3000, 25000);

Any clues? is this just a firefox problem?

@rbenitez
Copy link

We have the same problem with Firefox and Chrome. We are using selenium-java 3.0.0-beta3.

Thanks.

@selenareneephillips
Copy link

I am having this with 2.53.1, 2.53.0, 2.52.0, 2.51.0.

@ameyms
Copy link

ameyms commented Nov 15, 2016

I am seeing this with 2.43.1, 2.52.0, 2.51.0 & 2.53.0.
Seems to be timing out on invoking addCookie and deleteAllCookies.

@Vitkyk
Copy link

Vitkyk commented Feb 7, 2017

I am having it in Grid Console v. 3.0.1.

@essamzaroura
Copy link

how i can Avoid this problem ?
org.openqa.selenium.WebDriverException: Session [1be27502-b50c-4ccf-9788-753e86300165] was terminated due to TIMEOUT
Command duration or timeout: 54 milliseconds

@selenareneephillips
Copy link

@essamzaroura

I followed the suggestion in the accepted answer to this question. I never saw the problem again after I did it. I am using selenium 2.53.1:

https://stackoverflow.com/questions/39798340/selenium-grid-session-terminated-due-to-timeout-after-less-then-100-milliseco

@doomsbuster
Copy link

doomsbuster commented Sep 27, 2017

I am facing the same issue with Firefox 45 on Linux Rhel 7. At this point I have tried following versions of Selenium 2.47.1 and 2.53.0, on Docker Containers, and they both fail. I have tried several versions of browsers between Firefox 38 and 52.
I set the timeout and browserTimeout in my config.json which i think was simply ignored.

Is there a solution for this?

Exception in thread "main" org.openqa.selenium.WebDriverException: <html><body><h1>504 Gateway Time-out</h1>
The server didn't respond in time.
</body></html>
Command duration or timeout: 30.01 seconds
Build info: version: '2.53.1', revision: 'a36b8b1', time: '2016-06-30 17:37:03'
System info: host: '', ip: ', os.name: 'Mac OS X', os.arch: 'x86_64', os.version: '10.12.6', java.version: '1.8.0_25'
Driver info: org.openqa.selenium.remote.RemoteWebDriver
Capabilities [{applicationCacheEnabled=true, rotatable=false, handlesAlerts=true, databaseEnabled=true, version=45.7.0, platform=LINUX, nativeEvents=false, acceptSslCerts=true, webdriver.remote.sessionid=18ec103a-0ff5-4fdd-a97d-b243452db818, webStorageEnabled=true, locationContextEnabled=true, browserName=firefox, takesScreenshot=true, javascriptEnabled=true, cssSelectorsEnabled=true}]
Session ID: 18ec103a-0ff5-4fdd-a97d-b243452db818
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

config.json

{
  "capabilities": [
      {
         "version":"45.7.0",
         "browserName": "firefox",
         "maxInstances": 1,
         "seleniumProtocol": "WebDriver"
      }
  ],
  "configuration": {
      "proxy": "org.openqa.grid.selenium.proxy.DefaultRemoteProxy",
      "maxSession": 1,
      "port": 5555,
      "register": true,
      "registerCycle": 5000,
      "nodePolling": 5000,
      "unregisterIfStillDownAfter": 60000,
      "downPollingLimit": 2,
      "browserTimeout": 0,
      "timeout": 0
  }
}

@jianhaohe
Copy link

You can try adding a parameter when starting the node container --shm-size=512m。
shm-size=512m:Docker's default shared memory, /dev/shm, is only 64m, sometimes causing chrome to crash. This parameter increases the shared memory size to 512m.*

@lock lock bot locked and limited conversation to collaborators Aug 15, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests