com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager$SauceConnectDidNotStartException

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • Intermittently, SauceConnect fails to launch using the OnDemand plugin in Jenkins, failing builds. Usually, this does not appear to be a problem with SauceLabs service, as status.saucelabs.com does not report error, and I am able to launch SauceConnect manually on various other machines. Unfortunately, this is not readily reproducible -- it happens intermittently and seemingly randomly. Hopefully, the stack trace will give you some idea. Details: - Sauce Connect launched on slave using credentials set in job - v3 checkbox is unchecked - Slave is 64bit linux box running Debian 6.0.10 in ec2 - Configured to use webdriver Log: Starting Sauce Connect on slave node using tunnel identifier: default Launching Sauce Connect on <hostname> Error launching Sauce Connect Flushing Sauce Connect Input Stream Flushing Sauce Connect Error Stream Closing Sauce Connect process FATAL: Error launching Sauce Connect com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager$SauceConnectDidNotStartException: Error launching Sauce Connect at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:286) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$SauceConnectHandler.call(SauceOnDemandBuildWrapper.java:710) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$SauceConnectHandler.call(SauceOnDemandBuildWrapper.java:663) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:701) at ......remote call to build9.www.dash.d1.usw1.opendns.com(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356) at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) at hudson.remoting.Channel.call(Channel.java:752) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper.setUp(SauceOnDemandBuildWrapper.java:223) at hudson.model.Build$BuildExecution.doRun(Build.java:154) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:536) at hudson.model.Run.execute(Run.java:1718) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240)
    via by Nick Guilford,
  • Intermittently, SauceConnect fails to launch using the OnDemand plugin in Jenkins, failing builds. Usually, this does not appear to be a problem with SauceLabs service, as status.saucelabs.com does not report error, and I am able to launch SauceConnect manually on various other machines. Unfortunately, this is not readily reproducible -- it happens intermittently and seemingly randomly. Hopefully, the stack trace will give you some idea. Details: - Sauce Connect launched on slave using credentials set in job - v3 checkbox is unchecked - Slave is 64bit linux box running Debian 6.0.10 in ec2 - Configured to use webdriver Log: Starting Sauce Connect on slave node using tunnel identifier: default Launching Sauce Connect on <hostname> Error launching Sauce Connect Flushing Sauce Connect Input Stream Flushing Sauce Connect Error Stream Closing Sauce Connect process FATAL: Error launching Sauce Connect com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager$SauceConnectDidNotStartException: Error launching Sauce Connect at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:286) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$SauceConnectHandler.call(SauceOnDemandBuildWrapper.java:710) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$SauceConnectHandler.call(SauceOnDemandBuildWrapper.java:663) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:701) at ......remote call to build9.www.dash.d1.usw1.opendns.com(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356) at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) at hudson.remoting.Channel.call(Channel.java:752) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper.setUp(SauceOnDemandBuildWrapper.java:223) at hudson.model.Build$BuildExecution.doRun(Build.java:154) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:536) at hudson.model.Run.execute(Run.java:1718) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240)
    via by Nick Guilford,
  • Since upgrading Jenkins and sauce-ondemand we are having mostly failures with sauce connect launching. Occasionally sauce does launch correctly. Jenkins is running on Ubuntu 12.04, but we're launching sauce on the slave which is Debian 6.0.10. We are not using sauce on demand 1.142 because that was working even worse for us. Starting Sauce Connect on slave node using tunnel identifier: test-pull-requests-jsunit-tests-1446583886414 Launching Sauce Connect on localhost 03 Nov 20:51:04 - Sauce Connect 4.3.11, build 1757 2b421bb 03 Nov 20:51:04 - Using CA certificate bundle /etc/ssl/certs/ca-certificates.crt. 03 Nov 20:51:04 - Using CA certificate verify path /etc/ssl/certs. 03 Nov 20:51:04 - Starting up; pid 7789 03 Nov 20:51:04 - Command line arguments: /home/autotest/sc-4.3.11-linux/bin/sc -u jenkinsbuild -k **** -P 4445 03 Nov 20:51:04 - Using no proxy for connecting to Sauce Labs REST API. 03 Nov 20:51:04 - Resolving saucelabs.com to 162.222.75.243 took 1 ms. 03 Nov 20:51:04 - Started scproxy on port 35287. 03 Nov 20:51:04 - Please wait for 'you may start your tests' to start your tests. 03 Nov 20:51:04 - Starting secure remote tunnel VM... 03 Nov 20:51:09 - Secure remote tunnel VM provisioned. 03 Nov 20:51:09 - Tunnel ID: 98cdb43fe69b49c48ef2098d332ceded 03 Nov 20:51:09 - Secure remote tunnel VM is now: booting 03 Nov 20:52:16 - Error bringing up tunnel VM. 03 Nov 20:52:16 - Sauce Connect could not establish a connection. 03 Nov 20:52:16 - Please check your firewall and proxy settings. 03 Nov 20:52:16 - You can also use sc --doctor to launch Sauce Connect in diagnostic mode. 03 Nov 20:52:16 - Cleaning up. 03 Nov 20:52:16 - Checking domain overlap for my domain sauce-connect.proxy, other tunnel domain sauce-connect.proxy 03 Nov 20:52:16 - Overlapping domain: sauce-connect.proxy, shutting down tunnel 98cdb43fe69b49c48ef2098d332ceded. 03 Nov 20:52:19 - Goodbye. Error launching Sauce Connect Flushing Sauce Connect Input Stream Flushing Sauce Connect Error Stream Closing Sauce Connect process FATAL: Error launching Sauce Connect com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager$SauceConnectDidNotStartException: Error launching Sauce Connect at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:320) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$SauceConnectHandler.call(SauceOnDemandBuildWrapper.java:841) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$SauceConnectHandler.call(SauceOnDemandBuildWrapper.java:777) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) at ......remote call to pullrequests.www.dash.d1.usw1.opendns.com(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1413) at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) at hudson.remoting.Channel.call(Channel.java:778) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper.setUp(SauceOnDemandBuildWrapper.java:315) at hudson.model.Build$BuildExecution.doRun(Build.java:156) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537) at hudson.model.Run.execute(Run.java:1741) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) Notifying upstream projects of job completion Finished: FAILURE
    via by Michael Merritt,
  • Since upgrading Jenkins and sauce-ondemand we are having mostly failures with sauce connect launching. Occasionally sauce does launch correctly. Jenkins is running on Ubuntu 12.04, but we're launching sauce on the slave which is Debian 6.0.10. We are not using sauce on demand 1.142 because that was working even worse for us. Starting Sauce Connect on slave node using tunnel identifier: test-pull-requests-jsunit-tests-1446583886414 Launching Sauce Connect on localhost 03 Nov 20:51:04 - Sauce Connect 4.3.11, build 1757 2b421bb 03 Nov 20:51:04 - Using CA certificate bundle /etc/ssl/certs/ca-certificates.crt. 03 Nov 20:51:04 - Using CA certificate verify path /etc/ssl/certs. 03 Nov 20:51:04 - Starting up; pid 7789 03 Nov 20:51:04 - Command line arguments: /home/autotest/sc-4.3.11-linux/bin/sc -u jenkinsbuild -k **** -P 4445 03 Nov 20:51:04 - Using no proxy for connecting to Sauce Labs REST API. 03 Nov 20:51:04 - Resolving saucelabs.com to 162.222.75.243 took 1 ms. 03 Nov 20:51:04 - Started scproxy on port 35287. 03 Nov 20:51:04 - Please wait for 'you may start your tests' to start your tests. 03 Nov 20:51:04 - Starting secure remote tunnel VM... 03 Nov 20:51:09 - Secure remote tunnel VM provisioned. 03 Nov 20:51:09 - Tunnel ID: 98cdb43fe69b49c48ef2098d332ceded 03 Nov 20:51:09 - Secure remote tunnel VM is now: booting 03 Nov 20:52:16 - Error bringing up tunnel VM. 03 Nov 20:52:16 - Sauce Connect could not establish a connection. 03 Nov 20:52:16 - Please check your firewall and proxy settings. 03 Nov 20:52:16 - You can also use sc --doctor to launch Sauce Connect in diagnostic mode. 03 Nov 20:52:16 - Cleaning up. 03 Nov 20:52:16 - Checking domain overlap for my domain sauce-connect.proxy, other tunnel domain sauce-connect.proxy 03 Nov 20:52:16 - Overlapping domain: sauce-connect.proxy, shutting down tunnel 98cdb43fe69b49c48ef2098d332ceded. 03 Nov 20:52:19 - Goodbye. Error launching Sauce Connect Flushing Sauce Connect Input Stream Flushing Sauce Connect Error Stream Closing Sauce Connect process FATAL: Error launching Sauce Connect com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager$SauceConnectDidNotStartException: Error launching Sauce Connect at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:320) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$SauceConnectHandler.call(SauceOnDemandBuildWrapper.java:841) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$SauceConnectHandler.call(SauceOnDemandBuildWrapper.java:777) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) at ......remote call to pullrequests.www.dash.d1.usw1.opendns.com(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1413) at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) at hudson.remoting.Channel.call(Channel.java:778) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper.setUp(SauceOnDemandBuildWrapper.java:315) at hudson.model.Build$BuildExecution.doRun(Build.java:156) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537) at hudson.model.Run.execute(Run.java:1741) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) Notifying upstream projects of job completion Finished: FAILURE
    via by Michael Merritt,
  • GitHub comment 88#69109076
    via GitHub by gkushang
    ,
  • [JIRA] (JENKINS-38292) Sauce Connect 4.3.16: Error launching Sauce Connect
    via by akshar....@hotmail.com (JIRA),
    • com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager$SauceConnectDidNotStartException: Error launching Sauce Connect at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:286) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$SauceConnectHandler.call(SauceOnDemandBuildWrapper.java:710) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$SauceConnectHandler.call(SauceOnDemandBuildWrapper.java:663) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:701)
    No Bugmate found.