Discussion:
[selenium-users] DevToolsActivePort file doesn't exist when container used by Jenkins ??
Albert Shamsiyan
2018-10-25 13:58:28 UTC
Permalink
Tests are successfully executed when using the image manually, yet, failes
when using Jenkinsfile to orchatrate proccess.
To Reproduce

1. Spin up container using docker run -d -p 4444:4444 -v
/dev/shm:/dev/shm selenium/standalone-chrome
2. Execute selenium testings using mvn clean test etc - successful
passed.
3. stop container.
4. Try to have this proccess managed by Jenkinsfile using:
def server = Artifactory.server 'Artifactory' def rtMaven =
Artifactory.newMavenBuild() def buildInfo
docker.image("selenium/standalonechrome:latest").inside('--volume=/dev/shm:/dev/shm
--publish=4444:4444') { stage ('code Build') { timestamps { try {
withEnv(['JAVA_HOME=/usr/jdk1.8.0_171/',
'MAVEN_HOME=/usr/local/apache-maven/']) { // Java home of the container
rtMaven.run pom: 'allure-junit-example-master/pom.xml', goals: 'clean
test', buildInfo: buildInfo //sh 'sleep 8200' } } catch(err) { echo
"****************Error: " + err // sh 'sleep 8200' throw err } } } }
5. The follwing error shall be raised:

org.openqa.selenium.WebDriverException: unknown error: Chrome failed to
start: exited abnormally
(unknown error: DevToolsActivePort file doesn't exist)
(The process started from chrome location /usr/bin/google-chrome is no
longer running, so ChromeDriver is assuming that Chrome has crashed.)
(Driver info: chromedriver=2.43.600233
(523efee95e3d68b8719b3a1c83051aa63aa6b10d),platform=Linux
3.10.0-862.3.2.el7.x86_64 x86_64) (WARNING: The server did not provide any
stacktrace information)

Environment

OS:

Docker-Selenium image version:

Docker version:

Client:

Version: 18.03.1-ce

API version: 1.37

Go version: go1.9.5

Git commit: 9ee9f40

Built: Thu Apr 26 07:20:16 2018

OS/Arch: linux/amd64

Experimental: false

Orchestrator: swarm

Server:

Engine:

Version: 18.03.1-ce

API version: 1.37 (minimum version 1.12)

Go version: go1.9.5

Git commit: 9ee9f40

Built: Thu Apr 26 07:23:58 2018

OS/Arch: linux/amd64

Experimental: false
--
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-users+***@googlegroups.com.
To post to this group, send email to selenium-***@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-users/8137708a-ff1c-4e0c-b7dc-5cc8e2bcf3d3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Mustafa Yol
2018-10-25 16:10:45 UTC
Permalink
Hi, can you try to use a chrome driver version older than 2.40? For example
try to test with 2.39
Post by Albert Shamsiyan
Tests are successfully executed when using the image manually, yet, failes
when using Jenkinsfile to orchatrate proccess.
To Reproduce
1. Spin up container using docker run -d -p 4444:4444 -v
/dev/shm:/dev/shm selenium/standalone-chrome
2. Execute selenium testings using mvn clean test etc - successful
passed.
3. stop container.
def server = Artifactory.server 'Artifactory' def rtMaven =
Artifactory.newMavenBuild() def buildInfo
docker.image("selenium/standalonechrome:latest").inside('--volume=/dev/shm:/dev/shm
--publish=4444:4444') { stage ('code Build') { timestamps { try {
withEnv(['JAVA_HOME=/usr/jdk1.8.0_171/',
'MAVEN_HOME=/usr/local/apache-maven/']) { // Java home of the container
rtMaven.run pom: 'allure-junit-example-master/pom.xml', goals: 'clean
test', buildInfo: buildInfo //sh 'sleep 8200' } } catch(err) { echo
"****************Error: " + err // sh 'sleep 8200' throw err } } } }
org.openqa.selenium.WebDriverException: unknown error: Chrome failed to
start: exited abnormally
(unknown error: DevToolsActivePort file doesn't exist)
(The process started from chrome location /usr/bin/google-chrome is no
longer running, so ChromeDriver is assuming that Chrome has crashed.)
(Driver info: chromedriver=2.43.600233
(523efee95e3d68b8719b3a1c83051aa63aa6b10d),platform=Linux
3.10.0-862.3.2.el7.x86_64 x86_64) (WARNING: The server did not provide any
stacktrace information)
Environment
Version: 18.03.1-ce
API version: 1.37
Go version: go1.9.5
Git commit: 9ee9f40
Built: Thu Apr 26 07:20:16 2018
OS/Arch: linux/amd64
Experimental: false
Orchestrator: swarm
Version: 18.03.1-ce
API version: 1.37 (minimum version 1.12)
Go version: go1.9.5
Git commit: 9ee9f40
Built: Thu Apr 26 07:23:58 2018
OS/Arch: linux/amd64
Experimental: false
--
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
To view this discussion on the web visit
https://groups.google.com/d/msgid/selenium-users/8137708a-ff1c-4e0c-b7dc-5cc8e2bcf3d3%40googlegroups.com
<https://groups.google.com/d/msgid/selenium-users/8137708a-ff1c-4e0c-b7dc-5cc8e2bcf3d3%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.
--
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-users+***@googlegroups.com.
To post to this group, send email to selenium-***@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-users/CADcwm%3DGrokQ1n4Osn%2B%2B%2BEUat0kP3uchMOjnyRVOWM1bQ%3Ds-ifg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Loading...