Closed heisenbugger closed 6 years ago
Have you tried with the latest version? It looks like that the chrome driver version installed is out of date.
Yes! I tried the latest version and I'm still getting this error.
Traceback (most recent call last):
File "run.py", line 45, in job2
robson.execute(config, ind)
File "/robson/core/flow/robson.py", line 22, in execute
browser = browser_flow(config)
File "/robson/core/flow/browser_flow.py", line 16, in __init__
self.browser = Browser('chrome', **self.executable_path)
File "/robson/env/local/lib/python2.7/site-packages/splinter/browser.py", line 63, in Browser
return driver(*args, **kwargs)
File "/robson/env/local/lib/python2.7/site-packages/splinter/driver/webdriver/chrome.py", line 31, in __init__
self.driver = Chrome(chrome_options=options, **kwargs)
File "/robson/env/local/lib/python2.7/site-packages/selenium/webdriver/chrome/webdriver.py", line 69, in __init__
desired_capabilities=desired_capabilities)
File "/robson/env/local/lib/python2.7/site-packages/selenium/webdriver/remote/webdriver.py", line 98, in __init__
self.start_session(desired_capabilities, browser_profile)
File "/robson/env/local/lib/python2.7/site-packages/selenium/webdriver/remote/webdriver.py", line 188, in start_session
response = self.execute(Command.NEW_SESSION, parameters)
File "/robson/env/local/lib/python2.7/site-packages/selenium/webdriver/remote/webdriver.py", line 256, in execute
self.error_handler.check_response(response)
File "/robson/env/local/lib/python2.7/site-packages/selenium/webdriver/remote/errorhandler.py", line 194, in check_response
raise exception_class(message, screen, stacktrace)
WebDriverException: Message: unknown error: Chrome failed to start: exited abnormally
(Driver info: chromedriver=2.30.477691 (6ee44a7247c639c0703f291d320bdf05c1531b57),platform=Linux 4.11.11-coreos x86_64)
It could be also a problem of chrome with shm size and privilege mode. Please try to start the docker image with the parameter --shm-size=2g --privileged
Hi, any idea how to fix the above issue?
@heisenbugger,
Could you please show us how your Kubernetes manifests/configuration files look like?
Please reopen if the issue is still present.
Just encountered the same problem with standalone-chrome
image. Did mounted /dev/shm
volume.
Running with docker-compose
. Have somebody figured out what is the cause?
@ddnomad Did you find the solutin for your issues? Even i get below error when i use selenium/standalone-chrome image in docker. WebDriverException: Message: 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=73.0.3683.68 (47787ec04b6e38e22703e856e101e840b65afe72),platform=Linux 4.14.109-80.92.amzn1.x86_64 x86_64)
Meta -
Image(s): standalone-chrome
Docker-Selenium Image Version(s): 3.4.0
OS: CoreOS -> Debian Image
Expected Behavior -
Not crashing =)
Actual Behavior -
Crashing all the time :/
I deployed selenium standalone chrome on Kubernetes running Docker. Only selenium containers have been deployed on this cluster. The problem is: when we (devops and dev team) deployed our spider and let running on background (ENTRYPOINT) on Docker container, at the moment the crawler/spider start, Chrome failed and exited abnormally.
Any help will be appreciated.
Cheers Heisenbugger.