Skip to content
This repository has been archived by the owner on Nov 29, 2018. It is now read-only.

Selenium Grid is unable to send commands to Firefox #2199

Closed
lukeis opened this issue Mar 3, 2016 · 11 comments
Closed

Selenium Grid is unable to send commands to Firefox #2199

lukeis opened this issue Mar 3, 2016 · 11 comments
Assignees
@lukeis
Labels
Component-Grid Priority-High Restrict-AddIssueComment-Commit Status-WontFix Type-Defect

Comments

@lukeis
Copy link
Member

lukeis commented Mar 3, 2016

Originally reported on Google Code with ID 2199

What steps will reproduce the problem?
1. Launch grid hub
2. Launch webdriver node
3. Run test that uses Firefox via RemoteDriver

What is the expected output? What do you see instead?
Firefox should launch and the test commands should execute. Instead, Firefox is launching
and then hanging (2.0) or being cleaned up due to being 'orphaned' (2.1+)

Selenium version: 2.0, 2.1, 2.3
OS: Mac OS X 1.07 (Lion)
Browser: Firefox
Brower version: 4, 5

When launching a standalone server the test executes fine, so it would seem to be a
Grid issue.

The hub and node are on the same machine, registering as localhost. I have also tried
registering based on IP address of the machine with no change.

Hub console reports:
[java] Aug 4, 2011 3:07:19 AM org.openqa.grid.internal.RemoteProxy$CleanUpThread run
[java] WARNING: session ext. key 1312452289030 has been ORPHANED and will be released
[java] timing out ext. key 1312452289030

Reported by dave.hunt on 2011-08-04 10:36:02
@lukeis lukeis closed this as completed Mar 3, 2016
@lukeis lukeis mentioned this issue Mar 3, 2016
Closed
@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016 

Issue 2175 has been merged into this issue.

Reported by david.burns@theautomatedtester.co.uk on 2011-08-07 19:28:51

@lukeis lukeis changed the title placeholder empty issue Selenium Grid is unable to send commands to Firefox Mar 3, 2016
@lukeis lukeis self-assigned this Mar 3, 2016
@lukeis lukeis reopened this Mar 3, 2016
@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016

Reported by francois.reynaud on 2011-08-12 10:28:26

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016 

I'm no longer able to replicate this issue. Please reopen if you are seeing this with
the latest version of Selenium.

Reported by dave.hunt on 2011-09-14 12:06:12

  • Status changed: WontFix

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016 

I am still seeing this issue. Logs attached. Hub on one server, client on another. No
firewalls. Can run tests directly on the client.

Reported by stan.wozniak on 2011-09-14 15:18:37

- _Attachment: [selenium-client.log](https://storage.googleapis.com/google-code-attachments/selenium/issue-2199/comment-4/selenium-client.log)_ - _Attachment: [selenium-server.log](https://storage.googleapis.com/google-code-attachments/selenium/issue-2199/comment-4/selenium-server.log)_

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016 

I see this issue as well on 2.8.0.

Reported by blowery on 2011-10-14 23:54:18

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016 

Hub is running on Centos 5.6
RC is running on Windows Server 2008
See the quick orphaning when trying to use either Firefox 7 or Chrome 14 via chromedriver.


Firewall is off on Win2k8.

Do the hub and the RC communicate on any ports other than the hub port (generally 4444)
and the rc port (generally 5555)?

Reported by blowery on 2011-10-15 00:20:26

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016 

Got the grid working on Windows 7 Desktop, so not strictly windows related. Also tried
running the hub on the same node as the remote and see the issue. 

This may be EC2 related? I can repro if I fire up a Win2k8 Server in Amazon EC2 and
then spin up a hub and a remote and try the following test. The driver itself never
spins up.

Reported by blowery on 2011-10-17 21:12:03

- _Attachment: [drive.py](https://storage.googleapis.com/google-code-attachments/selenium/issue-2199/comment-8/drive.py)_

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016 

+1 for EC2. In my case it's Debian instances rather than win2k.  Any chance we can get
this issue reopened?

Reported by jonlorusso on 2011-10-21 21:07:47

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016 

Figured it out. The grid is binding to a 10.x.x.x address in ec2 and returning that
to the outside world. Set the -host properly on your grid node to your external ip
or host name and it works as expected.

Reported by blowery on 2011-10-21 22:25:37

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016 

Sorry, a better explanation. It's not that the grid node is binding to 10.x.x.x, it's
that it's using a 10.x.x.x IP in the URL it hands back in a Location header during
new session creation. It has no idea it's being hit on some other IP, so it just hands
back a URL built using the IP it knows it's bound to. By settings the -host flag to
the external hostname or IP, the URL generated will be correct and the external client
will be able to send commands to the new session.

A possible fix would be to use the hostname from the Host: header on the request for
the new session instead of the IP bound to.

Reported by blowery on 2011-10-21 23:03:47

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016

Reported by luke.semerau on 2015-09-17 18:13:24

  • Labels added: Restrict-AddIssueComment-Commit

@lukeis lukeis closed this as completed Mar 3, 2016
@SeleniumHQ SeleniumHQ locked and limited conversation to collaborators Mar 4, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@lukeis lukeis

Labels
Component-Grid Priority-High Restrict-AddIssueComment-Commit Status-WontFix Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@lukeis