我有一个使用硒的服务,使用Chrome headless
模式启动Chrome WebDriver。该应用程序通过tomcat8
启动。我可以在我的Mac上本地运行服务。
但是,一旦我通过AWS Elastic Beanstalk
将其部署到EC2节点后,WebDriver将无法正常启动:
28-Feb-2019 03:32:48.944 SEVERE [http-nio-8080-exec-7] org.apache.catalina.core.StandardWrapperValve.invoke Servlet.service() for servlet [registerCustomer] in context with path [] threw exception
org.openqa.selenium.WebDriverException: Timed out waiting for driver server to start.
Build info: version: '3.8.1', revision: '6e95a6684b', time: '2017-12-01T18:33:54.468Z'
System info: host: 'ip-172-31-16-234', ip: '172.31.16.234', os.name: 'Linux', os.arch: 'amd64', os.version: '4.14.97-74.72.amzn1.x86_64', java.version: '1.8.0_191'
Driver info: driver.version: ChromeDriver
at org.openqa.selenium.remote.service.DriverService.waitUntilAvailable(DriverService.java:192)
at org.openqa.selenium.remote.service.DriverService.start(DriverService.java:178)
at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:79)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:601)
at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:219)
at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:142)
at org.openqa.selenium.chrome.ChromeDriver.<init>(ChromeDriver.java:181)
at org.openqa.selenium.chrome.ChromeDriver.<init>(ChromeDriver.java:168)
at org.openqa.selenium.chrome.ChromeDriver.<init>(ChromeDriver.java:157)
at com.christina.insbot.factory.BrowserDriverFactory.createWebDriver(BrowserDriverFactory.java:64)
at com.christina.insbot.service.InsBot.<init>(InsBot.java:86)
at com.christina.insbot.service.servlet.RegisterCustomerService.doPost(RegisterCustomerService.java:93)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:661)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:742)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:198)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:493)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:140)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:81)
at org.apache.catalina.valves.RemoteIpValve.invoke(RemoteIpValve.java:685)
at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:650)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:87)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:342)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:800)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:800)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1471)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.openqa.selenium.net.UrlChecker$TimeoutException: Timed out waiting for [http://localhost:13611/status] to be available after 20010 ms
at org.openqa.selenium.net.UrlChecker.waitUntilAvailable(UrlChecker.java:100)
at org.openqa.selenium.remote.service.DriverService.waitUntilAvailable(DriverService.java:187)
... 36 more
Caused by: java.util.concurrent.TimeoutException
at java.util.concurrent.FutureTask.get(FutureTask.java:205)
at com.google.common.util.concurrent.SimpleTimeLimiter.callWithTimeout(SimpleTimeLimiter.java:147)
at org.openqa.selenium.net.UrlChecker.waitUntilAvailable(UrlChecker.java:75)
... 37 more
catalina错误:
/var/lib/tomcat8/webapps/ROOT/webdriver/chromedriver: /var/lib/tomcat8/webapps/ROOT/webdriver/chromedriver: cannot execute binary file
28-Feb-2019 03:32:48.926 SEVERE [Forwarding newSession on session null to remote] org.openqa.selenium.os.OsProcess.checkForError org.apache.commons.exec.ExecuteException: Process exited with an error: 126 (Exit value: 126)
我启动WebDriver的方式就是这样:
ChromeOptions options = new ChromeOptions();
// "--headless",
options.addArguments("--disable-gpu", "--window-size=1920,1200",
"--ignore-certificate-errors", "--silent");
if (useHeadlessMode) {
options.addArguments("--headless");
}
System.setProperty("webdriver.chrome.driver", EnvironmentInitialization.obtainChromeDriverPath());
webDriver = new ChromeDriver(options);
此错误消息...
28-Feb-2019 03:32:48.944 SEVERE [http-nio-8080-exec-7] org.apache.catalina.core.StandardWrapperValve.invoke Servlet.service() for servlet [registerCustomer] in context with path [] threw exception
org.openqa.selenium.WebDriverException: Timed out waiting for driver server to start.
Build info: version: '3.8.1', revision: '6e95a6684b', time: '2017-12-01T18:33:54.468Z'
System info: host: 'ip-172-31-16-234', ip: '172.31.16.234', os.name: 'Linux', os.arch: 'amd64', os.version: '4.14.97-74.72.amzn1.x86_64', java.version: '1.8.0_191'
Driver info: driver.version: ChromeDriver
...表示您的程序无法启动/产生新的 Chromedriver head> headless 模式中的服务。
此外,此错误消息...
/var/lib/tomcat8/webapps/ROOT/webdriver/chromedriver: /var/lib/tomcat8/webapps/ROOT/webdriver/chromedriver: cannot execute binary file
28-Feb-2019 03:32:48.926 SEVERE [Forwarding newSession on session null to remote] org.openqa.selenium.os.OsProcess.checkForError org.apache.commons.exec.ExecuteException: Process exited with an error: 126 (Exit value: 126)
...意味着您的程序无法执行 chromedriver 二进制文件,因此将 null 会话转发到 remotewebserver 。P>
有关 chromedriver 和 chromebrowser 的版本的更多信息将帮助我们以更好的方式调试您的问题。但是,您需要处理以下几个事实:
- 按照无头:make -disable-gpu标志不必要的
--disable-gpu
标志不需要 linux Systems 和 macos 。。 - 根据SwiftShader的失败,在无头模式下在Windows上的断言
--disable-gpu
标志也将在 Windows Systems上不必要。。 - 您正在使用 selenium v3.8.1 '2017-12-01T18:33:54.468Z'
- 但是您的 jdk 版本是新的 java.version:'1.8.0_191'
- 几乎可以肯定的是,您的程序正在尝试将 chromedriver 进程作为 root 用户。
解决方案
- 升级 jdk JDK 8U201 。
- 升级硒到当前级别版本3.141.59 。
- 升级 chromedriver 到当前 chromedriver v2.46 latver。
- 保留 chrome Chrome V71-73 级别之间的版本。(根据Chromedriver v2.46发行说明)
- 清洁您的项目工作区通过您的 IDE 和重建项目仅具有所需依赖性。
- ( linuxos )在执行 test Suite 。
- 如果您的base Web客户端版本太旧了,请通过 revo uninstaller 卸载它,并安装最新的GA并发布版本的版本 web client
- 确保在指定位置中存在 Chromedriver 。
- 确保 chromedriver 对非根本用户有可执行的权限。
- 进行系统重新启动。
- 执行您的
@Test
作为 non-root 用户。 - 始终在
tearDown(){}
中调用driver.quit()
以关闭&amp;销毁 WebDriver 和 Web客户端优雅的实例。
琐事
您可以在以下方式找到一些相关的讨论:
- Unterachbrowserexception:无法开始新的会话。可能的原因是使用硒网格的远程服务器的无效地址
- 远程WebDriver Unterachbrowserexception:无法启动新的会话