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.

  • [JIRA] (JENKINS-38292) Sauce Connect 4.3.16: Error launching Sauce Connect
    via by akshar....@hotmail.com (JIRA),
  • GitHub comment 88#69109076
    via GitHub by gkushang
    ,
  • 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 :).
    via by Andrei Costescu,
  • I am unable to set-up Sauce Connect using v4 and logs are also not created automatically. I always get timeout exception "Time out while waiting for Sauce Connect to start, please check the Sauce Connect log". Since logs are not created, I am unable to know reason for failure. Although I have enabled verbose logging but reason for failure is not known. But I can successfully execute my tests using Sauce Connect v3 and logs are also automatically created. I am attaching Jenkins console output for v4 and v3. Sauce Connect using v4(Jenkins Console): Starting Sauce Connect on master node using identifier: my-tun2 Launching Sauce Connect on Akash 30 May 11:31:58 - Error opening sc_my-tun2.log: No such file or directory Time out while waiting for Sauce Connect to start, please check the Sauce Connect log Flushing Sauce Connect Input Stream Flushing Sauce Connect Error Stream Closing Sauce Connect process FATAL: Time out while waiting for Sauce Connect to start, please check the Sauce Connect log com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager$SauceConnectDidNotStartException: Time out while waiting for Sauce Connect to start, please check the Sauce Connect log at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:337) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$SauceConnectHandler.call(SauceOnDemandBuildWrapper.java:824) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper.setUp(SauceOnDemandBuildWrapper.java:279) 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:1744) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374) Sauce Connect using v3(Jenkins Console): Starting Sauce Connect on master node using identifier: my-tun2 Launching Sauce Connect on Akash *** Support for Sauce Connect v3 is scheduled to end on 19 August 2015 *** *** Please update your settings to use Sauce Connect v4 *** Sauce Connect 3.1-r32, build 50 * Debug messages will be sent to sauce_connect.log 2015-05-30 12:26:28.124:INFO::jetty-7.x.y-SNAPSHOT 2015-05-30 12:26:29.791:INFO::Started SelectChannelConnector@0.0.0.0:60743 .---------------------------------------------------. | Have questions or need help with Sauce Connect? | | Contact us: http://support.saucelabs.com/forums | | Terms of Service: http://saucelabs.com/tos | ----------------------------------------------------- 2015-05-30 12:26:30,638 - / Starting \ 2015-05-30 12:26:30,733 - Please wait for "You may start your tests" to start your tests. 2015-05-30 12:26:30,766 - Forwarding: None:['80'] -> 127.0.0.1:['60743'] 2015-05-30 12:26:30,911 - Succesfully connected to local server 127.0.0.1:60743 in 133ms 2015-05-30 12:26:32,453 - {"tunnel_identifier":"my-tun2","metadata":{"OwnerHost":"127.0.0.1","Platform":"Java-1.8.0_45-Java_HotSpot-TM-_64-Bit_Server_VM,_25.45-b02,_Oracle_Corporation-on-Windows_8.1-6.3-amd64","PythonVersion":"2.5.1","Ports":["80"],"ScriptRelease":50,"OwnerPorts":["60743"],"Build":"50","ScriptName":"sauce_connect","Release":"3.1-r32"},"ssh_port":443,"squid_config":null,"use_caching_proxy":true,"no_ssl_bump_domains":null,"use_kgp":true,"domain_names":[],"direct_domains":null,"vm_version":"","fast_fail_regexps":null,"shared_tunnel":false} 2015-05-30 12:26:37,595 - Tunnel remote VM is provisioned (0257bb33cf9d4e5585b909630c5ecbe0) 2015-05-30 12:26:39,104 - Tunnel remote VM is booting .. 2015-05-30 12:26:45,944 - Tunnel remote VM is running at maki79134.miso.saucelabs.com 2015-05-30 12:26:46,045 - Succesfully connected to local server 127.0.0.1:60743 in 0ms 2015-05-30 12:26:46,056 - Starting connection to tunnel host... 2015-05-30 12:26:46,061 - Connecting to tunnel host maki79134.miso.saucelabs.com as akashbhardwaj 2015-05-30 12:26:46,778 - Forwarding Selenium with ephemeral port 60749 2015-05-30 12:26:46.782:INFO::jetty-7.x.y-SNAPSHOT 2015-05-30 12:26:46.794:INFO::Started SelectChannelConnector@0.0.0.0:4445 2015-05-30 12:26:46,798 - Selenium HTTP proxy listening on port 4445 2015-05-30 12:26:48,270 - Successful handshake with Sauce Connect server 2015-05-30 12:26:48,318 - Tunnel host version: 0.1.0, remote endpoint ID: af51f4769e524692827af6d81f6099de 2015-05-30 12:26:48,321 - Connected! You may start your tests. Sauce Connect 3.1.26 now launched for: my-tun2 Incremented process count for my-tun2, now 1 Can you resolve this ASAP as SauceLabs are going to deprecate Sauce Connect v3 soon..
    via by akash sharma,
  • 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 :).
    via by Andrei Costescu,
  • I am unable to set-up Sauce Connect using v4 and logs are also not created automatically. I always get timeout exception "Time out while waiting for Sauce Connect to start, please check the Sauce Connect log". Since logs are not created, I am unable to know reason for failure. Although I have enabled verbose logging but reason for failure is not known. But I can successfully execute my tests using Sauce Connect v3 and logs are also automatically created. I am attaching Jenkins console output for v4 and v3. Sauce Connect using v4(Jenkins Console): Starting Sauce Connect on master node using identifier: my-tun2 Launching Sauce Connect on Akash 30 May 11:31:58 - Error opening sc_my-tun2.log: No such file or directory Time out while waiting for Sauce Connect to start, please check the Sauce Connect log Flushing Sauce Connect Input Stream Flushing Sauce Connect Error Stream Closing Sauce Connect process FATAL: Time out while waiting for Sauce Connect to start, please check the Sauce Connect log com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager$SauceConnectDidNotStartException: Time out while waiting for Sauce Connect to start, please check the Sauce Connect log at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:337) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$SauceConnectHandler.call(SauceOnDemandBuildWrapper.java:824) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper.setUp(SauceOnDemandBuildWrapper.java:279) 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:1744) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374) Sauce Connect using v3(Jenkins Console): Starting Sauce Connect on master node using identifier: my-tun2 Launching Sauce Connect on Akash *** Support for Sauce Connect v3 is scheduled to end on 19 August 2015 *** *** Please update your settings to use Sauce Connect v4 *** Sauce Connect 3.1-r32, build 50 * Debug messages will be sent to sauce_connect.log 2015-05-30 12:26:28.124:INFO::jetty-7.x.y-SNAPSHOT 2015-05-30 12:26:29.791:INFO::Started SelectChannelConnector@0.0.0.0:60743 .---------------------------------------------------. | Have questions or need help with Sauce Connect? | | Contact us: http://support.saucelabs.com/forums | | Terms of Service: http://saucelabs.com/tos | ----------------------------------------------------- 2015-05-30 12:26:30,638 - / Starting \ 2015-05-30 12:26:30,733 - Please wait for "You may start your tests" to start your tests. 2015-05-30 12:26:30,766 - Forwarding: None:['80'] -> 127.0.0.1:['60743'] 2015-05-30 12:26:30,911 - Succesfully connected to local server 127.0.0.1:60743 in 133ms 2015-05-30 12:26:32,453 - {"tunnel_identifier":"my-tun2","metadata":{"OwnerHost":"127.0.0.1","Platform":"Java-1.8.0_45-Java_HotSpot-TM-_64-Bit_Server_VM,_25.45-b02,_Oracle_Corporation-on-Windows_8.1-6.3-amd64","PythonVersion":"2.5.1","Ports":["80"],"ScriptRelease":50,"OwnerPorts":["60743"],"Build":"50","ScriptName":"sauce_connect","Release":"3.1-r32"},"ssh_port":443,"squid_config":null,"use_caching_proxy":true,"no_ssl_bump_domains":null,"use_kgp":true,"domain_names":[],"direct_domains":null,"vm_version":"","fast_fail_regexps":null,"shared_tunnel":false} 2015-05-30 12:26:37,595 - Tunnel remote VM is provisioned (0257bb33cf9d4e5585b909630c5ecbe0) 2015-05-30 12:26:39,104 - Tunnel remote VM is booting .. 2015-05-30 12:26:45,944 - Tunnel remote VM is running at maki79134.miso.saucelabs.com 2015-05-30 12:26:46,045 - Succesfully connected to local server 127.0.0.1:60743 in 0ms 2015-05-30 12:26:46,056 - Starting connection to tunnel host... 2015-05-30 12:26:46,061 - Connecting to tunnel host maki79134.miso.saucelabs.com as akashbhardwaj 2015-05-30 12:26:46,778 - Forwarding Selenium with ephemeral port 60749 2015-05-30 12:26:46.782:INFO::jetty-7.x.y-SNAPSHOT 2015-05-30 12:26:46.794:INFO::Started SelectChannelConnector@0.0.0.0:4445 2015-05-30 12:26:46,798 - Selenium HTTP proxy listening on port 4445 2015-05-30 12:26:48,270 - Successful handshake with Sauce Connect server 2015-05-30 12:26:48,318 - Tunnel host version: 0.1.0, remote endpoint ID: af51f4769e524692827af6d81f6099de 2015-05-30 12:26:48,321 - Connected! You may start your tests. Sauce Connect 3.1.26 now launched for: my-tun2 Incremented process count for my-tun2, now 1 Can you resolve this ASAP as SauceLabs are going to deprecate Sauce Connect v3 soon..
    via by akash sharma,
    • com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager$SauceConnectDidNotStartException: Error launching Sauce Connect at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:335) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$SauceConnectHandler.call(SauceOnDemandBuildWrapper.java:918) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper.setUp(SauceOnDemandBuildWrapper.java:373) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:655) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1741) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)
    No Bugmate found.