CSharp exception when trying to use Selenium grid - selenium-chromedriver
I am receiving the following error when trying to launch my automation tests using selenium grid.
I have the hub running after launching this command.
When I browse http://10.1.27.27:4441/grid/register
I receive this error message:
HTTP ERROR 500
Problem accessing /grid/register. Reason:
Server Error
Caused by:
java.lang.IllegalStateException: Not a JSON Object: null
at com.google.gson.JsonElement.getAsJsonObject(JsonElement.java:90)
at org.openqa.grid.web.servlet.RegistrationServlet.process(RegistrationServlet.java:84)
at org.openqa.grid.web.servlet.RegistrationServlet.doGet(RegistrationServlet.jav
Command to start the hub
C:\seleniumserver\java -jar selenium-server-standalone-3.4.0.jar -role hub -port 4441
C:\seleniumserver\java -jar selenium-server-standalone-3.4.0.jar -role wd -hub http://localhost:4441/grid/register
Code
var capabilities = DesiredCapabilities.Chrome();
capabilities.Platform = Platform.CurrentPlatform;
IWebDriver driver = new RemoteWebDriver(new Uri("http://localhost:4441/wd/hub"), capabilities);
Error message received
at OpenQA.Selenium.Remote.RemoteWebDriver.UnpackAndThrowOnError(Response errorResponse)
at OpenQA.Selenium.Remote.RemoteWebDriver.Execute(String driverCommandToExecute, Dictionary`2 parameters)
at OpenQA.Selenium.Remote.RemoteWebDriver.StartSession(ICapabilities desiredCapabilities)
at OpenQA.Selenium.Remote.RemoteWebDriver..ctor(ICommandExecutor commandExecutor, ICapabilities desiredCapabilities)
at OpenQA.Selenium.Remote.RemoteWebDriver..ctor(Uri remoteAddress, ICapabilities desiredCapabilities)
at Boden.Automation.Workflow.BodenMobileNavigation..ctor() in C:\Projects\UAT Automation\Dev\SourceCode\test.cs:line 43
at test..ctor() in C:\Projects\UAT Automation\Dev\SourceCode\test.cs:line 21
Log
Log 2
Update
Here are my actions. Open command prompt (as administrator), navigate to the selenium jar folder and execute this command
java -jar selenium-server-standalone-3.4.0.jar -role hub -port 4441
The output from this command is here:
C:\SeleniumGrid>java -jar selenium-server-standalone-3.4.0.jar -role hub -port 4441
14:40:34.811 INFO - Selenium build info: version: '3.4.0', revision: 'unknown'
14:40:34.811 INFO - Launching Selenium Grid hub
2017-08-03 14:40:35.252:INFO::main: Logging initialized #603ms to org.seleniumhq.jetty9.util.log.StdErrLog
14:40:35.262 INFO - Will listen on 4441
2017-08-03 14:40:35.299:INFO:osjs.Server:main: jetty-9.4.3.v20170317
2017-08-03 14:40:35.322:INFO:osjs.session:main: DefaultSessionIdManager workerName=node0
2017-08-03 14:40:35.322:INFO:osjs.session:main: No SessionScavenger set, using defaults
2017-08-03 14:40:35.324:INFO:osjs.session:main: Scavenging every 600000ms
2017-08-03 14:40:35.329:INFO:osjsh.ContextHandler:main: Started o.s.j.s.ServletContextHandler#154b04f{/,null,AVAILABLE}
2017-08-03 14:40:35.341:INFO:osjs.AbstractConnector:main: Started ServerConnector#13af739{HTTP/1.1,[http/1.1]}{0.0.0.0:4441}
2017-08-03 14:40:35.341:INFO:osjs.Server:main: Started #692ms
14:40:35.342 INFO - Nodes should register to
http://10.1.27.27:4441/grid/register/
14:40:35.342 INFO - Selenium Grid hub is up and running
Then, I open a new command prompt (as administrator) and execute the following command in the selenium folder
java -jar selenium-server-standalone-3.4.0.jar -role wd -hub http://localhost:4441/grid/register
The output from this command is here:
C:\SeleniumGrid>java -jar selenium-server-standalone-3.4.0.jar -role wd -hub http://localhost:4441/grid/register
14:41:19.175 INFO - Selenium build info: version: '3.4.0', revision: 'unknown'
14:41:19.175 INFO - Launching a Selenium Grid node
2017-08-03 14:41:19.516:INFO::main: Logging initialized #505ms to org.seleniumhq.jetty9.util.log.StdErrLog
14:41:19.563 INFO - Driver class not found: com.opera.core.systems.OperaDriver
14:41:19.563 INFO - Driver provider com.opera.core.systems.OperaDriver
registration is skipped:Unable to create new instances on this machine.
14:41:19.564 INFO - Driver class not found: com.opera.core.systems.OperaDriver
14:41:19.564 INFO - Driver provider com.opera.core.systems.OperaDriver is not registered
14:41:19.565 INFO - Driver provider org.openqa.selenium.safari.SafariDriver registration is skipped: registration capabilities Capabilities [{browserName=safari, version=, platform=MAC}] does not match the current platform WIN8_1
2017-08-03 14:41:19.592:INFO:osjs.Server:main: jetty-9.4.3.v20170317
2017-08-03 14:41:19.613:INFO:osjsh.ContextHandler:main: Started o.s.j.s.ServletContextHandler#10f1111{/,null,AVAILABLE}
2017-08-03 14:41:19.625:INFO:osjs.AbstractConnector:main: Started ServerConnector#23e5ee{HTTP/1.1,[http/1.1]}{0.0.0.0:5555}
2017-08-03 14:41:19.626:INFO:osjs.Server:main: Started #615ms
14:41:19.626 INFO - Selenium Grid node is up and ready to register to the hub
14:41:19.636 INFO - Starting auto registration thread. Will try to register every 5000 ms.
14:41:19.636 INFO - Registering the node to the hub:http://localhost:4441/grid/register
14:41:19.675 INFO - The node is registered to the hub and ready to use
C# error (from running it within visual studio)
at OpenQA.Selenium.Remote.RemoteWebDriver.UnpackAndThrowOnError(Response errorResponse)
at OpenQA.Selenium.Remote.RemoteWebDriver.Execute(String driverCommandToExecute, Dictionary`2 parameters)
at OpenQA.Selenium.Remote.RemoteWebDriver.StartSession(ICapabilities desiredCapabilities)
at OpenQA.Selenium.Remote.RemoteWebDriver..ctor(ICommandExecutor commandExecutor, ICapabilities desiredCapabilities)
at OpenQA.Selenium.Remote.RemoteWebDriver..ctor(Uri remoteAddress, ICapabilities desiredCapabilities)
at ....ctor() in C:\Projects\UAT Automation\Dev\SourceCode...cs:line 38
at ....ctor() in C:\Projects\UAT Automation\Dev\SourceCode...cs:line 21
This is the error I receive
Related
TIBCO BW failing to debug successfully a REST service .I have created a jdbc resource and tested the connection was a success but i have this error
<>#BWEclipseAppNode> 12:12:32.545 INFO [main] com.tibco.thor.frwk.Deployer - Started by BusinessStudio. 12:12:34.970 INFO [main] com.tibco.bw.frwk.engine.BWEngine - TIBCO-BW-FRWK-300002: BW Engine [Main] started successfully. 12:12:35.355 INFO [Framework Event Dispatcher: Equinox Container: 80edabb3-8e47-001c-18c5-90bdbc610de0] com.tibco.thor.frwk.Deployer - TIBCO-THOR-FRWK-300001: Started OSGi Framework of AppNode [BWEclipseAppNode] in AppSpace [BWEclipseAppSpace] of Domain [BWEclipseDomain] 12:12:35.483 INFO [Framework Event Dispatcher: Equinox Container: 80edabb3-8e47-001c-18c5-90bdbc610de0] com.tibco.thor.frwk.Application - TIBCO-THOR-FRWK-300018: Deploying BW Application [RESTservice2.application:1.0]. 12:12:40.067 INFO [Framework Event Dispatcher: Equinox Container: 80edabb3-8e47-001c-18c5-90bdbc610de0] com.tibco.thor.frwk.Application - TIBCO-THOR-FRWK-300021: All Application dependencies are resolved for Application [RESTservice2.application:1.0] 12:12:41.431 INFO [Thread-28] com.tibco.thor.frwk.Application - TIBCO-THOR-FRWK-300019: BW Application [RESTservice2.application:1.0] is impaired. 12:12:41.435 INFO [Framework Event Dispatcher: Equinox Container: 80edabb3-8e47-001c-18c5-90bdbc610de0] com.tibco.thor.frwk.Application - Started by BusinessStudio, ignoring .enabled settings. 12:12:41.438 ERROR [CM Configuration Updater (Update: pid=bw.resource.jdbc.916120c9-fbcb-45de-a13c-b22e3edf76ec)] com.tibco.bw.sharedresource.runtime.dependency.ReferenceDependency - TIBCO-BW-SR-FRWK-503000: Unable to start SharedResource [restservice2.JDBCConnectionResource] from Module [RESTservice2:1.0.0.qualifier], DeploymentUnit [RESTservice2.application:1.0]. <Reason>: TIBCO-BW-SR-JDBC-500003: The database driver [com.mysql.jdbc.Driver] is not found. Ensure that DataSourceFactory bundle providing this driver is available in the environment. so this is the error i am getting as a result i cant run OSGi commands to request endpoint urls and for my rest service even though my code has no errors before debug ,i am getting this during debug ,please help.
In order to use the MySql JDBC driver you need to install it in the BusinessWorks environment of your machine. This is done by running the command 'bwinstall mysql-driver' from the <TIBCO_HOME>bw/6.X/bin folder.
As Emmanuel suggested, according to the error, you probably missed the required JDBC driver installation. Once you execute the command, it will start successfully.
Issue when trying to start Sonarqube services
I installed sonarqube-6.3.1 in my machine and created a database in mysql db named 'sonarqubedb'. Now when I am making changes in sonar.properties file to use the database, sonarqube is not getting started and throwing error msg, but If I am using the default DB configuration (and NOT mysql), I am able to start. Could somebody please provide me a solution what is going wrong when I am using mysql db. My sonar.properties file be like: sonar.jdbc.username=root sonar.jdbc.password= sonar.jdbc.url=jdbc:mysql://localhost:3306/sonarqubedb?useUnicode=true&characterEncoding=utf8&rewriteBatchedStatements=true&useConfigs=maxPerformance and the sonar log file when I try to start service, be like: --> Wrapper Started as Service Launching a JVM... WrapperManager class initialized by thread: main Using classloader: sun.misc.Launcher$AppClassLoader#4e25154f Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved. Wrapper Manager: JVM #1 Running a 64-bit JVM. Wrapper Manager: Registering shutdown hook Wrapper Manager: Using wrapper Load native library. One or more attempts may fail if platform specific libraries do not exist. Loading native library failed: wrapper-windows-x86-64.dll Cause: java.lang.UnsatisfiedLinkError: no wrapper-windows-x86-64 in java.library.path Loaded native library: wrapper.dll Calling native initialization method. Initializing WrapperManager native library. Java Executable: C:\ProgramData\Oracle\Java\javapath\java.exe Windows version: 6.1.7600 Java Version : 1.8.0_45-b15 Java HotSpot(TM) 64-Bit Server VM Java VM Vendor : Oracle Corporation Control event monitor thread started. Startup runner thread started. WrapperManager.start(org.tanukisoftware.wrapper.WrapperSimpleApp#4f023edb, args[]) called by thread: main Communications runner thread started. Open socket to wrapper...Wrapper-Connection Failed attempt to bind using local port 31000 Opened Socket from 31001 to 32000 Send a packet KEY : 4hhDEyNqmPXAiWpf handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=31001]) Received a packet LOW_LOG_LEVEL : 1 Wrapper Manager: LowLogLevel from Wrapper is 1 Received a packet PING_TIMEOUT : 0 PingTimeout from Wrapper is 0 Received a packet PROPERTIES : (Property Values) Received a packet START : start calling WrapperListener.start() Waiting for WrapperListener.start runner thread to complete. WrapperListener.start runner thread started. WrapperSimpleApp: start(args) Will wait up to 2 seconds for the main method to complete. WrapperSimpleApp: invoking main method 2017.04.26 14:54:12 INFO app[][o.s.a.AppFileSystem] Cleaning or creating temp directory C:\Program Files\Sonar\sonarqube-6.3.1\sonarqube-6.3.1\temp 2017.04.26 14:54:12 INFO app[][o.s.p.m.JavaProcessLauncher] Launch process[es]: C:\Program Files\Java\jre1.8.0_45\bin\java - Djava.awt.headless=true -Xmx1G -Xms256m -Xss256k -Djna.nosys=true - XX:+UseParNewGC -XX:+UseConcMarkSweepGC - XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly - XX:+HeapDumpOnOutOfMemoryError -Djava.io.tmpdir=C:\Program Files\Sonar\sonarqube-6.3.1\sonarqube-6.3.1\temp -javaagent:C:\Program Files\Java\jre1.8.0_45\lib\management-agent.jar -cp ./lib/common/*;./lib/search/* org.sonar.search.SearchServer C:\Program Files\Sonar\sonarqube-6.3.1\sonarqube-6.3.1\temp\sq- process3041279828124660880properties Send a packet START_PENDING : 5000 Send a packet START_PENDING : 5000 WrapperSimpleApp: start(args) end. Main Completed=false, exitCode=null WrapperListener.start runner thread stopped. returned from WrapperListener.start() Send a packet STARTED : Startup runner thread stopped. Received a packet PING : ping Send a packet PING : ok Received a packet PING : ping Send a packet PING : ok 2017.04.26 14:54:23 INFO app[][o.s.p.m.Monitor] Process[es] is up 2017.04.26 14:54:23 INFO app[][o.s.p.m.JavaProcessLauncher] Launch process[web]: C:\Program Files\Java\jre1.8.0_45\bin\java - Djava.awt.headless=true -Dfile.encoding=UTF-8 -Xmx512m -Xms128m - XX:+HeapDumpOnOutOfMemoryError -Djava.io.tmpdir=C:\Program Files\Sonar\sonarqube-6.3.1\sonarqube-6.3.1\temp -javaagent:C:\Program Files\Java\jre1.8.0_45\lib\management-agent.jar -cp ./lib/common/*;./lib/server/*;C:\Program Files\Sonar\sonarqube- 6.3.1\sonarqube-6.3.1\lib\jdbc\mysql\mysql-connector-java-5.1.39.jar org.sonar.server.app.WebServer C:\Program Files\Sonar\sonarqube- 6.3.1\sonarqube-6.3.1\temp\sq-process5745752416531116392properties Received a packet PING : ping Send a packet PING : ok 2017.04.26 14:54:28 INFO app[][o.s.p.m.Monitor] Process[es] is stopping 2017.04.26 14:54:28 ERROR app[][o.s.p.m.Monitor] Process[web] failed to start 2017.04.26 14:54:28 INFO app[][o.s.p.m.Monitor] Process[es] is stopped Wrapper Manager: ShutdownHook started WrapperManager.stop(0) called by thread: Wrapper-Shutdown-Hook Send a packet STOP : 0 Received a packet STOP : Thread, Wrapper-Shutdown-Hook, handling the shutdown process. calling listener.stop() WrapperSimpleApp: stop(0) returned from listener.stop() -> 0 shutdownJVM(0) Thread:Wrapper-Shutdown-Hook Send a packet STOPPED : 0 Closing socket. Server daemon shut down Wrapper Manager: ShutdownHook complete <-- Wrapper Stopped Thanks in Advance :)
Go to your sonarqube/logs directory. You'll find several log files and one of them will contain the detailed error on why sonarqube won't start.(you'll have to scroll all the way down inside the files for the latest information iirc)
Go through this sonar documentation, you will get some help - https://docs.sonarqube.org/display/SONAR/Installing+the+Server
I had the same issue. The problem was that my MySQL version didn't meet the minimum requirements.
ChromeDriver keeps crashing on Jenkins Selenium Job: "WebDriverError: Chrome failed to start: crashed"
I am trying to run some automated tests on Jenkins using protractor which uses selenium and chromedriver. I have also setup xvfb so that we can run these tests in a headless manner. I have the xvfb jenkins plugin installed and it is working correctly. Error The problem I'm having, is when I start the tests, chrome keeps crashing. I get this error: E/launcher - WebDriverError: unknown error: Chrome failed to start: crashed ... E/launcher - Process exited with error code 199 Setup Here is the information I have on the setup of the system: Chrome Location: /usr/bin/google-chrome Version: Chromium 52.0.2743.0 ChromeDriver Location: {project_home}/src/js/node_modules/webdriver-manager/selenium/chromedriver_2.24 Version: ChromeDriver 2.24.417424 Selenium Location: {project_home}/src/js/node_modules/webdriver-manager/selenium/selenium-server-standalone-2.53.1.jar Version: 2.53.1 Protractor Location: {project_home}/src/js/node_modules/protractor Version: 4.0.9 WebDriver Manager Location: {project_home}/src/js/node_modules/webdriver-manager Version: 10.2.4 Jenkins Version: 1.6.17 xvfb Version: Unknown Node Version: 6.7 Java Version: java-8-openjdk-amd64 Output Here is the console output from Jenkins: ... 21:58:07.380 INFO - Launching a standalone Selenium Server 21:58:07.407 INFO - Java: Oracle Corporation 25.111-b14 21:58:07.407 INFO - OS: Linux 4.4.0-47-generic amd64 21:58:07.418 INFO - v2.53.1, with Core v2.53.1. Built from revision a36b8b1 21:58:07.473 INFO - Driver provider org.openqa.selenium.ie.InternetExplorerDriver registration is skipped: registration capabilities Capabilities [{ensureCleanSession=true, browserName=internet explorer, version=, platform=WINDOWS}] does not match the current platform LINUX 21:58:07.474 INFO - Driver provider org.openqa.selenium.edge.EdgeDriver registration is skipped: registration capabilities Capabilities [{browserName=MicrosoftEdge, version=, platform=WINDOWS}] does not match the current platform LINUX 21:58:07.474 INFO - Driver class not found: com.opera.core.systems.OperaDriver 21:58:07.474 INFO - Driver provider com.opera.core.systems.OperaDriver is not registered 21:58:07.475 INFO - Driver provider org.openqa.selenium.safari.SafariDriver registration is skipped: registration capabilities Capabilities [{browserName=safari, version=, platform=MAC}] does not match the current platform LINUX 21:58:07.475 INFO - Driver class not found: org.openqa.selenium.htmlunit.HtmlUnitDriver 21:58:07.475 INFO - Driver provider org.openqa.selenium.htmlunit.HtmlUnitDriver is not registered 21:58:07.527 INFO - RemoteWebDriver instances should connect to: http://127.0.0.1:4444/wd/hub 21:58:07.527 INFO - Selenium Server is up and running Current webdriver status: [21:58:08] I/status - selenium standalone version available: 2.53.1 [default] [21:58:08] I/status - chromedriver versions available: 2.22, 2.24 [default] [21:58:08] I/status - geckodriver version available: v0.9.0 [default] [21:58:08] I/status - android-sdk is not present [21:58:08] I/status - appium is not present **** STARTING GUI TESTS **** Running ./node_modules/protractor/bin/protractor conf-server.js [21:58:08] I/local - Starting selenium standalone server... [21:58:08] I/launcher - Running 1 instances of WebDriver [21:58:09] I/local - Selenium standalone server started at http://10.0.0.82:33509/wd/hub [21:59:09] E/launcher - unknown error: Chrome failed to start: crashed (Driver info: chromedriver=2.24.417424 (c5c5ea873213ee72e3d0929b47482681555340c3),platform=Linux 4.4.0-47-generic x86_64) (WARNING: The server did not provide any stacktrace information) Command duration or timeout: 60.17 seconds Build info: version: '2.53.1', revision: 'a36b8b1', time: '2016-06-30 17:37:03' System info: host: 'ip-10-0-0-82', ip: '10.0.0.82', os.name: 'Linux', os.arch: 'amd64', os.version: '4.4.0-47-generic', java.version: '1.8.0_111' Driver info: org.openqa.selenium.chrome.ChromeDriver [21:59:09] E/launcher - WebDriverError: unknown error: Chrome failed to start: crashed (Driver info: chromedriver=2.24.417424 (c5c5ea873213ee72e3d0929b47482681555340c3),platform=Linux 4.4.0-47-generic x86_64) (WARNING: The server did not provide any stacktrace information) Command duration or timeout: 60.17 seconds Build info: version: '2.53.1', revision: 'a36b8b1', time: '2016-06-30 17:37:03' System info: host: 'ip-10-0-0-82', ip: '10.0.0.82', os.name: 'Linux', os.arch: 'amd64', os.version: '4.4.0-47-generic', java.version: '1.8.0_111' Driver info: org.openqa.selenium.chrome.ChromeDriver at WebDriverError ({project_home}/src/js/node_modules/selenium-webdriver/lib/error.js:27:5) at Object.checkLegacyResponse ({project_home}/src/js/node_modules/selenium-webdriver/lib/error.js:639:15) at parseHttpResponse ({project_home}/src/js/node_modules/selenium-webdriver/http/index.js:538:13) at client_.send.then.response ({project_home}/src/js/node_modules/selenium-webdriver/http/index.js:472:11) at ManagedPromise.invokeCallback_ ({project_home}/src/js/node_modules/selenium-webdriver/lib/promise.js:1379:14) at TaskQueue.execute_ ({project_home}/src/js/node_modules/selenium-webdriver/lib/promise.js:2913:14) at TaskQueue.executeNext_ ({project_home}/src/js/node_modules/selenium-webdriver/lib/promise.js:2896:21) at asyncRun ({project_home}/src/js/node_modules/selenium-webdriver/lib/promise.js:2820:25) at {project_home}/src/js/node_modules/selenium-webdriver/lib/promise.js:639:7 at process._tickCallback (internal/process/next_tick.js:103:7) From: Task: WebDriver.createSession() at Function.createSession ({project_home}/src/js/node_modules/selenium-webdriver/lib/webdriver.js:329:24) at Builder.build ({project_home}/src/js/node_modules/selenium-webdriver/builder.js:458:24) at Local.DriverProvider.getNewDriver ({project_home}/src/js/node_modules/protractor/built/driverProviders/driverProvider.js:37:33) at Runner.createBrowser ({project_home}/src/js/node_modules/protractor/built/runner.js:198:43) at {project_home}/src/js/node_modules/protractor/built/runner.js:277:30 at _fulfilled ({project_home}/src/js/node_modules/q/q.js:834:54) at self.promiseDispatch.done ({project_home}/src/js/node_modules/q/q.js:863:30) at Promise.promise.promiseDispatch ({project_home}/src/js/node_modules/q/q.js:796:13) at {project_home}/src/js/node_modules/q/q.js:604:44 at runSingle ({project_home}/src/js/node_modules/q/q.js:137:13) [21:59:09] E/launcher - Process exited with error code 199 Protractor Config exports.config = { seleniumServerJar: './node_modules/webdriver-manager/selenium/selenium-server-standalone-2.53.1.jar', chromeDriver: './node_modules/webdriver-manager/selenium/chromedriver_2.24', capabilities: { 'browserName': 'chrome', 'chromeOptions': { binary: '/usr/bin/google-chrome', args: ['--enable-logging','--v=1'], extensions: [] } }, framework: 'custom', frameworkPath: require.resolve('./node_modules/protractor-cucumber-framework'), specs: [ '../../features/gui/active/*.feature' ], onPrepare: function () { require('babel-register')({ presets : ['es2015'] }) } }; Jenkins xvfb plugin Related Chrome reference: https://sites.google.com/a/chromium.org/chromedriver/help/chrome-doesn-t-start unknown error: Chrome failed to start: exited abnormally (Driver info: chromedriver=2.9 suggests configuring xvfb WebDriverError: unknown error: Chrome failed to start: exited abnormally unsolved https://github.com/seleniumhq/selenium-google-code-issue-archive/issues/8409 suggests using direct connect: "Protractor can test directly against Chrome and Firefox without using a Selenium Server. To use this, in your config file set directConnect: true." Selenium Webdriver & Chrome driver - not able to run chrome driver suggests using java 1.6 instead Chrome on remote webdriver (via Grid) failed to start suggests using x64 chromedriver and specifying it in a parameter
Please try updating Protractor to latest 4.0.11 and chrome driver to 2.25 as there were lot of issues reported in 2.24 version which has been fixed. Try it once and let us know.
Can you follow below : - In you jenkins settings add a global property key : DISPLAY value:0:0 - On your server start Xvfb in the background: Xvfb :0 -ac -screen 0 1024x768x24 & Reference link: unknown error: Chrome failed to start: exited abnormally (Driver info: chromedriver=2.9
I had the same issue as you I ended up to change my args as a below args: [ "--headless", "--no-sandbox" ,"--disable-dev-shm-usage"]
eJabberd with Riak
I have configured a Riak cluster and all is well. I configured ejabberd.yml to talk to it but the last few lines I see in the logs are as below and I can't figure out how to debug it any further. Anyone able to help? Change ejabberd install user to root... Missing ssl cert for your host. Generating snakeoil ssl cert for xmpp.alchemy.local... Generating a 4096 bit RSA private key ..............................................++ ..............................................++ writing new private key to '/tmp/selfsigned.key' ----- Writing ssl cert and private key to '/opt/ejabberd/ssl/host.pem'... Missing ssl cert for your xmpp domain. Generating snakeoil ssl cert for alchemy.local... Generating a 4096 bit RSA private key ................................................++ ........................++ writing new private key to '/tmp/selfsigned.key' ----- Writing ssl cert and private key to '/opt/ejabberd/ssl/alchemy.local.pem'... Generating ejabberd config file... Generating ejabberdctl config file... Starting ejabberd... tail: cannot open ‘/var/log/ejabberd/crash.log’ for reading: No such file or directory tail: cannot open ‘/var/log/ejabberd/error.log’ for reading: No such file or directory tail: cannot open ‘/var/log/ejabberd/erlang.log’ for reading: No such file or directory tail: ‘/var/log/ejabberd/crash.log’ has been replaced with a remote file. giving up on this name tail: ‘/var/log/ejabberd/error.log’ has been replaced with a remote file. giving up on this name 09:57:16.424 [info] Application lager started on node ejabberd#xmpp 09:57:16.431 [info] Application crypto started on node ejabberd#xmpp 09:57:16.442 [info] Application sasl started on node ejabberd#xmpp 09:57:16.452 [info] Application asn1 started on node ejabberd#xmpp 09:57:16.452 [info] Application public_key started on node ejabberd#xmpp 09:57:16.466 [info] Application ssl started on node ejabberd#xmpp 09:57:16.474 [info] Application p1_yaml started on node ejabberd#xmpp 09:57:16.485 [info] Application p1_tls started on node ejabberd#xmpp 09:57:16.493 [info] Application p1_xml started on node ejabberd#xmpp 09:57:16.507 [info] Application p1_stringprep started on node ejabberd#xmpp 09:57:16.511 [info] Application p1_zlib started on node ejabberd#xmpp 09:57:16.519 [info] Application cache_tab started on node ejabberd#xmpp 09:57:16.677 [info] Application mnesia started on node ejabberd#xmpp 09:57:17.179 [info] Application inets started on node ejabberd#xmpp 09:57:17.558 [notice] Changed loglevel of //var/log/ejabberd/ejabberd.log to debug 09:57:17.567 [debug] Supervisor ejabberd_sup started ejabberd_hooks:start_link() at pid <0.239.0> 09:57:17.575 [debug] Supervisor kernel_safe_sup started pg2:start_link() at pid <0.241.0> 09:57:17.575 [debug] Supervisor ejabberd_sup started ejabberd_node_groups:start_link() at pid <0.240.0> 09:57:17.575 [debug] Supervisor ejabberd_sup started ejabberd_system_monitor:start_link() at pid <0.242.0> 09:57:17.577 [debug] Supervisor ejabberd_sup started ejabberd_router:start_link() at pid <0.243.0> 09:57:17.579 [debug] Supervisor ejabberd_sup started ejabberd_router_multicast:start_link() at pid <0.249.0> 09:57:17.582 [debug] Supervisor ejabberd_sup started ejabberd_s2s:start_link() at pid <0.255.0> 09:57:17.584 [debug] Supervisor ejabberd_sup started ejabberd_local:start_link() at pid <0.265.0> 09:57:17.585 [debug] The option captcha_cmd is not configured, but some module wants to use the CAPTCHA feature. 09:57:17.587 [debug] Supervisor ejabberd_sup started ejabberd_captcha:start_link() at pid <0.271.0> 09:57:17.587 [debug] Supervisor ejabberd_sup started ejabberd_tmp_sup:start_link(ejabberd_s2s_in_sup, ejabberd_s2s_in) at pid <0.273.0> 09:57:17.587 [debug] Supervisor ejabberd_sup started ejabberd_tmp_sup:start_link(ejabberd_s2s_out_sup, ejabberd_s2s_out) at pid <0.274.0> 09:57:17.587 [debug] Supervisor ejabberd_sup started ejabberd_tmp_sup:start_link(ejabberd_service_sup, ejabberd_service) at pid <0.275.0> 09:57:17.587 [debug] Supervisor ejabberd_sup started ejabberd_tmp_sup:start_link(ejabberd_iq_sup, gen_iq_handler) at pid <0.276.0> 09:57:17.588 [debug] Supervisor ejabberd_sup started ejabberd_tmp_sup:start_link(ejabberd_frontend_socket_sup, ejabberd_frontend_socket) at pid <0.277.0> 09:57:17.588 [debug] Supervisor ejabberd_sup started ejabberd_listener:start_link() at pid <0.278.0> 09:57:17.591 [info] Application protobuffs started on node ejabberd#xmpp 09:57:17.591 [info] Application riak_pb started on node ejabberd#xmpp 09:57:17.591 [info] Application riakc started on node ejabberd#xmpp 09:57:17.600 [debug] Supervisor inet_gethost_native_sup started undefined at pid <0.289.0> 09:57:17.600 [debug] Supervisor kernel_safe_sup started inet_gethost_native:start_link() at pid <0.288.0> I managed to get a bit more detail by ejabberdctl debug. It seems to be having an issue with the node name, but the exact same config works fine if i don't add Riak to the ejabberd.yml file. tail: cannot open ‘/var/log/ejabberd/crash.log’ for reading: No such file or directory tail: cannot open ‘/var/log/ejabberd/error.log’ for reading: No such file or directory tail: cannot open ‘/var/log/ejabberd/erlang.log’ for reading: No such file or directory {error_logger,{{2016,2,4},{19,30,38}},"Invalid node name: ~p~n",['debug-not a tty-ejabberd#xmpp']} {error_logger,{{2016,2,4},{19,30,38}},crash_report,[[{initial_call,{net_kernel,init,['Argument__1']}},{pid,<0.20.0>},{registered_name,[]},{error_info,{exit,{error,badarg},[{gen_server,init_it,6,[{file,"gen_server.erl"},{line,322}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,237}]}]}},{ancestors,[net_sup,kernel_sup,<0.10.0>]},{messages,[]},{links,[<0.17.0>]},{dictionary,[{longnames,false}]},{trap_exit,true},{status,running},{heap_size,987},{stack_size,27},{reductions,902}],[]]} {error_logger,{{2016,2,4},{19,30,38}},supervisor_report,[{supervisor,{local,net_sup}},{errorContext,start_error},{reason,{'EXIT',nodistribution}},{offender,[{pid,undefined},{name,net_kernel},{mfargs,{net_kernel,start_link,[['debug-not a tty-ejabberd',shortnames]]}},{restart_type,permanent},{shutdown,2000},{child_type,worker}]}]} {error_logger,{{2016,2,4},{19,30,38}},supervisor_report,[{supervisor,{local,kernel_sup}},{errorContext,start_error},{reason,{shutdown,{failed_to_start_child,net_kernel,{'EXIT',nodistribution}}}},{offender,[{pid,undefined},{name,net_sup},{mfargs,{erl_distribution,start_link,[]}},{restart_type,permanent},{shutdown,infinity},{child_type,supervisor}]}]} {error_logger,{{2016,2,4},{19,30,38}},crash_report,[[{initial_call,{application_master,init,['Argument__1','Argument__2','Argument__3','Argument__4']}},{pid,<0.9.0>},{registered_name,[]},{error_info,{exit,{{shutdown,{failed_to_start_child,net_sup,{shutdown,{failed_to_start_child,net_kernel,{'EXIT',nodistribution}}}}},{kernel,start,[normal,[]]}},[{application_master,init,4,[{file,"application_master.erl"},{line,133}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,237}]}]}},{ancestors,[<0.8.0>]},{messages,[{'EXIT',<0.10.0>,normal}]},{links,[<0.8.0>,<0.7.0>]},{dictionary,[]},{trap_exit,true},{status,running},{heap_size,376},{stack_size,27},{reductions,117}],[]]} {error_logger,{{2016,2,4},{19,30,38}},std_info,[{application,kernel},{exited,{{shutdown,{failed_to_start_child,net_sup,{shutdown,{failed_to_start_child,net_kernel,{'EXIT',nodistribution}}}}},{kernel,start,[normal,[]]}}},{type,permanent}]} {"Kernel pid terminated",application_controller,"{application_start_failure,kernel,{{shutdown,{failed_to_start_child,net_sup,{shutdown,{failed_to_start_child,net_kernel,{'EXIT',nodistribution}}}}},{kernel,start,[normal,[]]}}}"} Crash dump was written to: //var/log/ejabberd/erl_crash_20160204-193037.dump Kernel pid terminated (application_controller) ({application_start_failure,kernel,{{shutdown,{failed_to_start_child,net_sup,{shutdown,{failed_to_start_child,net_kernel,{'EXIT',nodistribution}}}}},{k **** Update **** The reason that this was happening was because I hadn't specified the --net network connection in my Docker run command and so it couldn't find the network. Unfortunately there is no debug to indicate this it just hangs forever (this would happen in the general case where the network that hosts the Riak cluster cannot be found and is a nightmare to debug). I still don't know why the "debug" flag causes tty to be added to the node name but i suspect it is somehow related as when i fixed it that also stopped appearing. Anyone interested in knowing the detail can view it here https://github.com/rroemhild/docker-ejabberd/issues/81#issuecomment-181133336
You are starting the Erlang VM with an invalid node name: {error_logger,{{2016,2,4},{19,30,38}},"Invalid node name: ~p~n",['debug-not a tty-ejabberd#xmpp']} Check where you have configured this: 'debug-not a tty-ejabberd#xmpp', as it is indeed not a valid Erlang VM cluster node name.
Junit with Embedded Glassfish fails - JMS Resource Adapter should be EMBEDDED
I'm trying to test a session bean (NetBeans 6.8, Glassfish V3). Unfortunately, the embedded glassfish is unable to start properly, as it tries to connect to a remote JMS Provider (at localhost:7676): $ ant test ... [junit] Mar 23, 2010 12:13:51 PM com.sun.messaging.jms.ra.ResourceAdapter start [junit] INFO: MQJMSRA_RA1101: SJSMQ JMS Resource Adapter starting: REMOTE [junit] Mar 23, 2010 12:13:51 PM com.sun.messaging.jmq.jmsclient.ExceptionHandler throwConnectionException [junit] WARNING: [C4003]: Error occurred on connection creation [localhost:7676]. - cause: java.net.ConnectException: Connection refused The error is in itself correct, as no (other) JMS provider is running. I was expecting the embedded glassfish to start the JMS provider in EMBEDDED mode. My test uses javax.ejb.embeddable.EJBContainer : #BeforeClass public static void initContainer() throws Exception { ec = EJBContainer.createEJBContainer(); ctx = ec.getContext(); } When I start glassfish normally, it's fine: $ bin/asadmin get server.jms-service.type server.jms-service.type=EMBEDDED How can I get my junit tests to use an embedded glassfish with an EMBEDDED JMS Provider?
Ok, I downloaded an official glassfish build (v3.0.1) from here, and now it's starting the JMS Provider EMBEDDED as expected.