Problem on "locking port 7054"

139 views
Skip to first unread message

Ishwar Dharmadhkari

unread,
Apr 23, 2014, 1:15:14 AM4/23/14
to seleniu...@googlegroups.com
Hi all
we are frequently facing the the Issue "Unable to bind to locking port 7054 within 45000 ms" in Grid 2,

Please help regarding below mention  the issue :-
org.openqa.selenium.WebDriverException: Unable to bind to locking port 7054 within 45000 ms
Build info: version: '2.39.0', revision: 'ff23eac', time: '2013-12-16 16:11:15'
System info: host: 'LN-PUN-D041', ip: '192.168.2.41', os.name: 'Windows 7', os.arch: 'x86', os.version: '6.1', java.version: '1.6.0_22'
Driver info: driver.version: FirefoxDriver
Command duration or timeout: 92.32 seconds
Build info: version: '2.39.0', revision: 'ff23eac', time: '2013-12-16 16:12:12'
System info: host: 'LN-PUN-T07', ip: '192.168.3.7', os.name: 'Windows 7', os.arch: 'x86', os.version: '6.1', java.version: '1.6.0_25'
Driver info: org.openqa.selenium.remote.RemoteWebDriver
	at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:193)
	at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:145)
	at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:554)
	at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:216)
	at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:111)
	at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:129)
	at TestBase.setUp(TestBase.java:83)
	at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
	at java.util.concurrent.FutureTask.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
Caused by: org.openqa.selenium.WebDriverException: Unable to bind to locking port 7054 within 45000 ms
Build info: version: '2.39.0', revision: 'ff23eac', time: '2013-12-16 16:11:15'
System info: host: 'LN-PUN-D041', ip: '192.168.2.41', os.name: 'Windows 7', os.arch: 'x86', os.version: '6.1', java.version: '1.6.0_22'
Driver info: driver.version: FirefoxDriver
Build info: version: '2.39.0', revision: 'ff23eac', time: '2013-12-16 16:12:12'
System info: host: 'LN-PUN-T07', ip: '192.168.3.7', os.name: 'Windows 7', os.arch: 'x86', os.version: '6.1', java.version: '1.6.0_25'
Driver info: driver.version: FirefoxDriver
	at org.openqa.selenium.internal.SocketLock.lock(SocketLock.java:98)
	at org.openqa.selenium.firefox.internal.NewProfileExtensionConnection.start(NewProfileExtensionConnection.java:84)
	at org.openqa.selenium.firefox.FirefoxDriver.startClient(FirefoxDriver.java:250)
	at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:110)
	at org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:197)
	at org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:190)
	at org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:108)
	at org.openqa.selenium.remote.server.DefaultDriverFactory.callConstructor(DefaultDriverFactory.java:62)
	at org.openqa.selenium.remote.server.DefaultDriverFactory.newInstance(DefaultDriverFactory.java:56)
	at org.openqa.selenium.remote.server.DefaultSession$BrowserCreator.call(DefaultSession.java:216)
	at org.openqa.selenium.remote.server.DefaultSession$BrowserCreator.call(DefaultSession.java:1)
	at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
	at java.util.concurrent.FutureTask.run(Unknown Source)
	at org.openqa.selenium.remote.server.DefaultSession$1.run(DefaultSession.java:170)
	

Shankar Kurella

unread,
Apr 27, 2014, 10:47:08 PM4/27/14
to seleniu...@googlegroups.com
hi 
if you have any antivirus installed, it would be blocking selenium to run.. try disabling your antivirus and run.... if it works then add selenium to known virus definitions... as quickheal is stopping selenium to run, i faced this issue
regards
shankar


--
You received this message because you are subscribed to the Google Groups "Selenium Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to selenium-user...@googlegroups.com.
To post to this group, send email to seleniu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-users/3e370216-2878-4b43-ad1b-26426a2647eb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
shankar k b
shankarkurella.blogspot.com

Ishwar Dharmadhkari

unread,
Apr 29, 2014, 2:10:42 AM4/29/14
to seleniu...@googlegroups.com

hi shankar
As per your suggestion, I have block my antivirus but still we are facing the problem 
Please help

Regards
Ishwar

Shankar Kurella

unread,
Apr 29, 2014, 5:11:04 AM4/29/14
to seleniu...@googlegroups.com
are you using the right version of firefox and selenium??? use the latest selenium drivers, and as per my knowledge selenium dint work on firefox versions of 22 or above so i am using with firefox 19... probably this should make your code work... 
regards
shankar 



For more options, visit https://groups.google.com/d/optout.

Alasdair Macmillan

unread,
Apr 29, 2014, 5:49:12 AM4/29/14
to seleniu...@googlegroups.com
Hi Ishwar,

I seem to have the same problem under Linux (Debian 7.4), on a machine which is running two Firefox nodes at the same time (and has no anti-virus). The nodes run fine for a while, and then after a few days start failing with this issue.

I temporarily changed the implementation of SocketLock to print the exception, and it says:

java.net.BindException: Address already in use

The port doesn't show up as open on any Linux tools, apart from this tool (which seems to examine OS information a bit more deeply):

http://linuxpoison.blogspot.co.uk/2008/06/tool-to-find-hidden-processes-and-ports.html

After quite a bit of Googling, this article seems to suggest that it could be an issue related to binding a TCP port, but never listening on it (which SocketLock currently does):

http://dcid.me/blog/2007/06/hidden-ports-on-linux/

Ishwar - to help debug this issue, could you tell me how many Firefox nodes you have had running on this machine, and when they started failing?

Thanks,

Alasdair
Reply all
Reply to author
Forward
0 new messages