search

ericmckean / chromedriver

Automatically exported from code.google.com/p/chromedriver
0 stars 0 forks source link

unknown error: Chrome failed to start: crashed #974

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Java code to invoke Node with chrome on CentOS - 

   public static void setUp() throws MalformedURLException {

                Proxy proxy = new Proxy();
            proxy.setHttpProxy(PROXY);
            DesiredCapabilities cap DesiredCapabilities.chrome();
            cap.setBrowserName("chrome");
            cap.setPlatform(org.openqa.selenium.Platform.LINUX);
            cap.setCapability(CapabilityType.PROXY, proxy);
            dr = new RemoteWebDriver(new URL("http://172.21.137.36:4444/wd/hub"),cap);
            try {
                TestBase.initialize(dr);
            } catch (IOException e) {
                e.printStackTrace();
            }
        }

Node is registered to hub with following command line and it is registered 
successfully.

java -jar selenium-server-standalone-2.44.0.jar -role node -browser 
browserName=chrome -hub https://IPOFHUB:4444/grid/register -port 5566 
-Dwebdriver.chrome.driver="/usr/bin/chromedriver"

Everything looks good but getting an unknown error as follows and there is not 
much info on the error given.
unknown error: Chrome failed to start: crashed
  (Driver info: chromedriver=2.12.301324 (de8ab311bc9374d0ade71f7c167bad61848c7c48),platform=Linux 2.6.32-431.el6.x86_64 x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 60.56 seconds
Build info: version: '2.44.0', revision: '76d78cf', time: '2014-10-23 20:02:37'
System info: host: 'localhost.localdomain', ip: '127.0.0.1', os.name: 'Linux', 
os.arch: 'amd64', os.version: '2.6.32-431.el6.x86_64', java.version: '1.7.0_45'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Command duration or timeout: 61.94 seconds
Build info: version: '2.44.0', revision: 
'76d78cf323ce037c5f92db6c1bba601c2ac43ad8', time: '2014-10-23 13:11:40'
System info: host: 'amundale-WS', ip: '10.82.250.33', os.name: 'Windows 7', 
os.arch: 'amd64', os.version: '6.1', java.version: '1.7.0_40'
Driver info: org.openqa.selenium.remote.RemoteWebDriver
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
    at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:204)
    at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:156)
    at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:599)
    at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:240)
    at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:126)
    at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:153)
    at foo.TestSuiteRunner_Linux_Chrome.setUp(TestSuiteRunner_Linux_Chrome.java:54)

Please suggest if there is any workaround. Also, if it's a known issue then 
workaround if any.

Platform-
Selenium version: 2.44
OS: CentOS 6.5
Browser: Chrome
Browser version: 38

Original issue reported on code.google.com by mundlean...@gmail.com on 11 Nov 2014 at 4:37

GoogleCodeExporter commented 9 years ago

Original comment by andrewch...@chromium.org on 13 Nov 2014 at 1:08

GoogleCodeExporter commented 9 years ago 
please change your java client port to 5566

http://172.21.137.36:5566/wd/hub

Original comment by andrewch...@chromium.org on 13 Nov 2014 at 1:12

GoogleCodeExporter commented 9 years ago

Original comment by andrewch...@chromium.org on 13 Nov 2014 at 1:13

GoogleCodeExporter commented 9 years ago 
Tried to change the port and run the test. Still it gives error as follows -

org.openqa.selenium.WebDriverException: The process has not exited yet 
therefore no result is available ...
Command duration or timeout: 23.43 seconds
Build info: version: '2.44.0', revision: 
'76d78cf323ce037c5f92db6c1bba601c2ac43ad8', time: '2014-10-23 13:11:40'
System info: host: 'amundale-WS', ip: '10.154.17.97', os.name: 'Windows 7', 
os.arch: 'amd64', os.version: '6.1', java.version: '1.7.0_40'
Driver info: org.openqa.selenium.remote.RemoteWebDriver
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
    at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:204)
    at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:156)
    at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:599)
    at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:240)
    at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:126)
    at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:153)
    at foo.TestSuiteRunner_Linux_Chrome.setUp(TestSuiteRunner_Linux_Chrome.java:55)
Caused by: java.lang.IllegalStateException: The process has not exited yet 
therefore no result is available ...
    at org.apache.commons.exec.DefaultExecuteResultHandler.getException(DefaultExecuteResultHandler.java:74)
    at org.openqa.selenium.os.UnixProcess.checkForError(UnixProcess.java:165)
    at org.openqa.selenium.os.CommandLine.checkForError(CommandLine.java:183)
    at org.openqa.selenium.remote.service.DriverService.start(DriverService.java:165)
    at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:62)
    at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:572)
    at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:240)
    at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:126)
    at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:139)
    at org.openqa.selenium.chrome.ChromeDriver.<init>(ChromeDriver.java:171)
    at org.openqa.selenium.chrome.ChromeDriver.<init>(ChromeDriver.java:139)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
    at org.openqa.selenium.remote.server.DefaultDriverProvider.callConstructor(DefaultDriverProvider.java:59)
    at org.openqa.selenium.remote.server.DefaultDriverProvider.newInstance(DefaultDriverProvider.java:53)
    at org.openqa.selenium.remote.server.DefaultDriverFactory.newInstance(DefaultDriverFactory.java:54)
    at org.openqa.selenium.remote.server.DefaultSession$BrowserCreator.call(DefaultSession.java:214)
    at org.openqa.selenium.remote.server.DefaultSession$BrowserCreator.call(DefaultSession.java:1)
    at java.util.concurrent.FutureTask.run(FutureTask.java:262)
    at org.openqa.selenium.remote.server.DefaultSession$1.run(DefaultSession.java:168)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at java.lang.Thread.run(Thread.java:744)

Original comment by mundlean...@gmail.com on 13 Nov 2014 at 1:29

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
we ran chromedriver  in Linux(Ubumtu)   hub/node, and do not see the problem.

     can you check following
  1. set DISPLAY -  make sure chrome can be launched where your hub/node is running.
  2. make sure your chromedriver and chrome run well manually.

Original comment by andrewch...@chromium.org on 17 Nov 2014 at 11:20

GoogleCodeExporter commented 9 years ago 
Chrome opens manually from /usr/bin

chromedriver runs with following message -
"Starting chromedriver 2.12.301324() on port 9515
only local connections are allowed."

Original comment by mundlean...@gmail.com on 17 Nov 2014 at 11:54

GoogleCodeExporter commented 9 years ago 
both Chrome browser and chromedriver in /usr/bin?  you did open browser 
manually?
can you provide me the log from chromedriver when it launch the browser?
use
-Dwebdriver.chrome.logfile=/tmp/chromedriver.log

Original comment by andrewch...@chromium.org on 18 Nov 2014 at 10:26

GoogleCodeExporter commented 9 years ago

Original comment by andrewch...@chromium.org on 19 Nov 2014 at 7:10

GoogleCodeExporter commented 9 years ago 
do you have this issue  still?
otherwise, can we close the case?

Original comment by andrewch...@chromium.org on 2 Dec 2014 at 11:51

GoogleCodeExporter commented 9 years ago

Original comment by andrewch...@chromium.org on 20 Jan 2015 at 11:04

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
I a having same issue with chrome linux driver 2.13 and chrome 
39.0.2171.95(64-bit)
strangely this only happens on my linux fedora VM, not on my fedora desktop.

Original comment by gli00...@gmail.com on 28 Jan 2015 at 6:54

GoogleCodeExporter commented 9 years ago 
if you can open another ticket,  since they are different.
please also describe more detail.

Original comment by andrewch...@chromium.org on 28 Jan 2015 at 8:01

GoogleCodeExporter commented 9 years ago

Original comment by samu...@chromium.org on 21 Feb 2015 at 12:26