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

Google Groups | acam...@saucelabs.com (JIRA) | 1 year ago
  1. 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
  2. 0

    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..

    Jenkins JIRA | 2 years ago | akash sharma
    com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager$SauceConnectDidNotStartException: Time out while waiting for Sauce Connect to start, please check the Sauce Connect log
  3. 0

    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..

    Jenkins JIRA | 2 years ago | akash sharma
    com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager$SauceConnectDidNotStartException: Time out while waiting for Sauce Connect to start, please check the Sauce Connect log
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    [JIRA] [sauce-ondemand-plugin] (JENKINS-31305) SauceConnect fails to launch using the OnDemand plugin in Jenkins, failing builds.

    Google Groups | 1 year ago | hedieh....@autodesk.com (JIRA)
    com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager$SauceConnectDidNotStartException: Error launching Sauce Connect<br />
  6. 0

    GitHub comment 88#69109076

    GitHub | 2 years ago | gkushang
    com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager$SauceConnectDidNotStartException: Error launching Sauce Connect

    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:916)
      2. hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper.setUp(SauceOnDemandBuildWrapper.java:347)
      2 frames
    4. Hudson
      Executor.run
      1. hudson.model.Build$BuildExecution.doRun(Build.java:156)
      2. hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537)
      3. hudson.model.Run.execute(Run.java:1744)
      4. hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
      5. hudson.model.ResourceController.execute(ResourceController.java:98)
      6. hudson.model.Executor.run(Executor.java:374)
      6 frames