Session [(null externalkey)] not available and is not among the last 1000 terminated sessions. #7677

Open
ericomurtez opened this Issue Jan 10, 2017 · 2 comments

Projects

None yet

3 participants

@ericomurtez

The problem

This was working for me and I updated everything on the environment and now I cannot run a test successfully.

Every time I start a test, the chrome (or safari) will start on the device then the test will fail with error. This only happens when I run a test through the grid, if I point straight to node there are no issues. I can also run desktop browser tests through same node, so I dont think it is a grid issues.

Seems to me that the session is being created but as soon as that happens, the grid loses the session and gives error, but the node is waiting for the grid to send it commands.

Session [(null externalkey)] not available and is not among the last 1000 terminated sessions.
Active sessions are[ext. key 7376a1ec-40b9-4d9d-9860-138ca24a3b3a] (org.openqa.grid.common.exception.GridException) (Selenium::WebDriver::Error::UnknownError)

The node and grid continue for 30 seconds until the session times out.

Grid gives message after timeout
WARN - session ext. key 7376a1ec-40b9-4d9d-9860-138ca24a3b3a has TIMED OUT due to client inactivity and will be released.

Environment

  • 1.6.3

Latest version of everything.

Appium logs
https://gist.github.com/ericomurtez/b521115568036d25cb5e9941ca5016b3

Grid logs.
14:27:19.283 INFO - Launching Selenium Grid hub
2017-01-10 14:27:20.159:INFO::main: Logging initialized @1069ms
14:27:20.177 INFO - Will listen on 4444
14:27:20.245 INFO - Will listen on 4444
2017-01-10 14:27:20.252:INFO:osjs.Server:main: jetty-9.2.z-SNAPSHOT
2017-01-10 14:27:20.289:INFO:osjsh.ContextHandler:main: Started o.s.j.s.ServletContextHandler@32eebfc{/,null,AVAILABLE}
2017-01-10 14:27:20.335:INFO:osjs.ServerConnector:main: Started ServerConnector@6ec8211{HTTP/1.1}{0.0.0.0:4444}
2017-01-10 14:27:20.336:INFO:osjs.Server:main: Started @1246ms
14:27:20.337 INFO - Nodes should register to http://192.168.56.1:4444/grid/register/
14:27:20.337 INFO - Selenium Grid hub is up and running
14:27:34.779 INFO - Got a request to create a new session: Capabilities [{rotatable=false, nativeEvents=false, newCommandTimeout=300, platformVersion=6.0, browserName=chrome, takesScreenshot=true, javascriptEnabled=true, platformName=android, version=, deviceName=0715f7c4c56a0b36, platform=ANY, cssSelectorsEnabled=true}]
14:27:35.340 INFO - Registered a node http://localhost:4801
14:27:43.314 INFO - Got a request to create a new session: Capabilities [{rotatable=false, nativeEvents=false, newCommandTimeout=300, platformVersion=6.0, browserName=chrome, takesScreenshot=true, javascriptEnabled=true, platformName=android, version=, deviceName=0715f7c4c56a0b36, platform=ANY, cssSelectorsEnabled=true}]
14:27:43.316 INFO - Available nodes: [http://localhost:4801]
14:27:43.316 INFO - Trying to create a new session on node http://localhost:4801
14:27:43.316 INFO - Trying to create a new session on test slot {browserName=chrome, maxInstances=1, version=6.0, deviceName=0715f7c4c56a0b36, platform=ANDROID}
14:28:29.400 WARN - session ext. key 9c446ca2-3d59-4e26-ab23-285fb48b3353 has TIMED OUT due to client inactivity and will be released.

@triager triager added the NeedsTriage label Jan 10, 2017
@dpgraham
Contributor

What happens if you run the appium tests locally without using Grid?

@ericomurtez

They will run fine.
But what makes me think it is appium related is that if I have chrome desktop browser nodes on the grid there are no issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment