com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager$SauceConnectDidNotStartException: Error launching Sauce Connect

Jenkins JIRA | Hedieh ekhlasi | 1 year ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    SauceConnect fails to launch using the OnDemand plugin in Jenkins, failing builds. There is no problem on Command Prompt since it is showing : *Sauce Connect is up, you may start your tests.* However the Jenkins fails the build with following errors: *Starting pre-build for Sauce Labs plugin Starting Sauce Connect on master node using identifier: default Launching Sauce Connect on ECS-8110eee4.ecs.ads.autodesk.com 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.setUp(SauceOnDemandBuildWrapper.java:327) at hudson.model.Build$BuildExecution.doRun(Build.java:154) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533) at hudson.model.Run.execute(Run.java:1759) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240)*

    Jenkins JIRA | 1 year ago | Hedieh ekhlasi
    com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager$SauceConnectDidNotStartException: Error launching Sauce Connect
  2. 0

    SauceConnect fails to launch using the OnDemand plugin in Jenkins, failing builds. There is no problem on Command Prompt since it is showing : *Sauce Connect is up, you may start your tests.* However the Jenkins fails the build with following errors: *Starting pre-build for Sauce Labs plugin Starting Sauce Connect on master node using identifier: default Launching Sauce Connect on ECS-8110eee4.ecs.ads.autodesk.com 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.setUp(SauceOnDemandBuildWrapper.java:327) at hudson.model.Build$BuildExecution.doRun(Build.java:154) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533) at hudson.model.Run.execute(Run.java:1759) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240)*

    Jenkins JIRA | 1 year ago | Hedieh ekhlasi
    com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager$SauceConnectDidNotStartException: Error launching Sauce Connect
  3. 0

    [JIRA] [sauce-ondemand-plugin] (JENKINS-31615) Sometimes the plugin leaves behind a stale PID file or zombie Sauce Connect process, should the plugin handle this?

    Google Groups | 1 year ago | acam...@saucelabs.com (JIRA)
    com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager$SauceConnectDidNotStartException: Error launching Sauce Connect
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    It's been a while now since an update of this plugin didn't break... So I updated the plugin. Then the job errored out when trying to start sauce connect because if cannot find a file or directory to launch it (...myuser/sc-4.3.8-linux/bin/...sc). Unfortunately I didn't copy the text to paste it here. So I went and checked I had there all kinds of versions like sc-4.3.6-linux and lower, then some \*sauceconnect\*logs then a hidden ._sc-\* folder and some sc-43 archives but indeed no sc-4.3.8-linux. I deleted all of those then ran the job again and that exception went away. Now I got this:{code} Starting Sauce Connect on master node using identifier: default Launching Sauce Connect on ip-*** Sauce Connect 4.3.8 now launched for: *** Incremented process count for ***, now 1 ERROR: Build step failed with exception java.lang.NullPointerException at com.saucelabs.ci.BrowserFactory.getLatestWebDriverBrowserVersion(BrowserFactory.java:314) at com.saucelabs.ci.BrowserFactory.webDriverBrowserForKey(BrowserFactory.java:303) at hudson.plugins.sauce_ondemand.SauceEnvironmentUtil.outputWebDriverVariables(SauceEnvironmentUtil.java:44) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$1.buildEnvVars(SauceOnDemandBuildWrapper.java:296) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:926) at hudson.tasks.Ant.perform(Ant.java:144) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761) at hudson.model.Build$BuildExecution.build(Build.java:203) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:536) 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:374){code} Hmm I said - another bug. Tried to work around it by unchecking the "Use latest versions of selected browsers?" checkbox from job config - sauce section. (I have there "Webdriver" checked but no browser as selenium Java code handles that later on in my job) Then this second error went away and I got a new one: {code}Starting Sauce Connect on master node using identifier: default Launching Sauce Connect on ip-*** Process count non-zero, but no active tunnels found Process count reset to zero FATAL: Unable to start Sauce Connect, please see the Sauce Connect log com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager$SauceConnectDidNotStartException: Unable to start Sauce Connect, please see the Sauce Connect log at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:308) at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:305) at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:305) at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:305) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$SauceConnectHandler.call(SauceOnDemandBuildWrapper.java:819) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper.setUp(SauceOnDemandBuildWrapper.java:279) 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:1741) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374){code} But now I can't see any sauceconnect log files in my user's home... So I'm stuck. Will try to revert again to plugin version 1.113 meanwhile but please fix these - I want to be able to update :).

    Jenkins JIRA | 2 years ago | Andrei Costescu
    com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager$SauceConnectDidNotStartException: Unable to start Sauce Connect, please see the Sauce Connect log
  6. 0

    It's been a while now since an update of this plugin didn't break... So I updated the plugin. Then the job errored out when trying to start sauce connect because if cannot find a file or directory to launch it (...myuser/sc-4.3.8-linux/bin/...sc). Unfortunately I didn't copy the text to paste it here. So I went and checked I had there all kinds of versions like sc-4.3.6-linux and lower, then some \*sauceconnect\*logs then a hidden ._sc-\* folder and some sc-43 archives but indeed no sc-4.3.8-linux. I deleted all of those then ran the job again and that exception went away. Now I got this:{code} Starting Sauce Connect on master node using identifier: default Launching Sauce Connect on ip-*** Sauce Connect 4.3.8 now launched for: *** Incremented process count for ***, now 1 ERROR: Build step failed with exception java.lang.NullPointerException at com.saucelabs.ci.BrowserFactory.getLatestWebDriverBrowserVersion(BrowserFactory.java:314) at com.saucelabs.ci.BrowserFactory.webDriverBrowserForKey(BrowserFactory.java:303) at hudson.plugins.sauce_ondemand.SauceEnvironmentUtil.outputWebDriverVariables(SauceEnvironmentUtil.java:44) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$1.buildEnvVars(SauceOnDemandBuildWrapper.java:296) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:926) at hudson.tasks.Ant.perform(Ant.java:144) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761) at hudson.model.Build$BuildExecution.build(Build.java:203) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:536) 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:374){code} Hmm I said - another bug. Tried to work around it by unchecking the "Use latest versions of selected browsers?" checkbox from job config - sauce section. (I have there "Webdriver" checked but no browser as selenium Java code handles that later on in my job) Then this second error went away and I got a new one: {code}Starting Sauce Connect on master node using identifier: default Launching Sauce Connect on ip-*** Process count non-zero, but no active tunnels found Process count reset to zero FATAL: Unable to start Sauce Connect, please see the Sauce Connect log com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager$SauceConnectDidNotStartException: Unable to start Sauce Connect, please see the Sauce Connect log at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:308) at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:305) at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:305) at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:305) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$SauceConnectHandler.call(SauceOnDemandBuildWrapper.java:819) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper.setUp(SauceOnDemandBuildWrapper.java:279) 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:1741) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374){code} But now I can't see any sauceconnect log files in my user's home... So I'm stuck. Will try to revert again to plugin version 1.113 meanwhile but please fix these - I want to be able to update :).

    Jenkins JIRA | 2 years ago | Andrei Costescu
    com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager$SauceConnectDidNotStartException: Unable to start Sauce Connect, please see the Sauce Connect log

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager$SauceConnectDidNotStartException

      Error launching Sauce Connect

      at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection()
    2. com.saucelabs.ci
      AbstractSauceTunnelManager.openConnection
      1. com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:320)
      1 frame
    3. hudson.plugins.sauce_ondemand
      SauceOnDemandBuildWrapper.setUp
      1. hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$SauceConnectHandler.call(SauceOnDemandBuildWrapper.java:841)
      2. hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper.setUp(SauceOnDemandBuildWrapper.java:327)
      2 frames
    4. Hudson
      ResourceController.execute
      1. hudson.model.Build$BuildExecution.doRun(Build.java:154)
      2. hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533)
      3. hudson.model.Run.execute(Run.java:1759)
      4. hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
      5. hudson.model.ResourceController.execute(ResourceController.java:89)
      5 frames