Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-17687

Sauce-ondemand times out every time

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Incomplete
    • Icon: Major Major
    • sauce-ondemand-plugin
    • None
    • Jenkins 1.505 on Tomcat 6 on Red hat.

      Whenever I try to run a build it times out like:

      Starting Sauce OnDemand SSH tunnel on master node
Launching Sauce Connect on gw-stg-ci-01
Time out while waiting for Sauce Connect to start, attempting to continue
Sauce Connect now launched

      I'm able to start the sauce connect application just fine when I manually start it as the tomcat user.

          [JENKINS-17687] Sauce-ondemand times out every time

          Ross Rowe added a comment -

          Hi Bram, my apologies for taking so long to get back to you on this issue, could you tell me if it's still occurring? If so, could you send me an email at rossjrowe at gmail dot com with the Jenkins system log attached?

          Thanks,

          Ross

          Ross Rowe added a comment - Hi Bram, my apologies for taking so long to get back to you on this issue, could you tell me if it's still occurring? If so, could you send me an email at rossjrowe at gmail dot com with the Jenkins system log attached? Thanks, Ross

          David Brochu added a comment -

          I also see the same issue in my environment

          David Brochu added a comment - I also see the same issue in my environment

          Ross Rowe added a comment -

          Hi David, thanks for letting me know...would you be able to send me your Jenkins log so that I check to see if there were any errors (rossjrowe at gmail dot com)?

          Cheers,

          Ross

          Ross Rowe added a comment - Hi David, thanks for letting me know...would you be able to send me your Jenkins log so that I check to see if there were any errors (rossjrowe at gmail dot com)? Cheers, Ross

          hinling yeung added a comment -

          This may be a bit old bug but we are running to this now:

          [EnvInject] - Loading node environment variables.
Building on master in workspace /var/lib/jenkins/jobs/testng-fe-ie10.xml/workspace
Fetching changes from the remote Git repository
Fetching upstream changes from ssh://git@stash.sv2.trulia.com:7999/qa/test-automation.git
Checking out Revision 6d18749c0423c3d44b63dc65f101d163df89f090 (origin/master)
No emails were triggered.
Starting Sauce OnDemand SSH tunnel on master node
Launching Sauce Connect on se2.sv2.trulia.com
Time out while waiting for Sauce Connect to start, attempting to continue
Sauce Connect now launched
Incremented process count for selenium, now 1
[Gradle] - Launching build.
[workspace] $ /usr/share/gradle/bin/gradle -Dtest_site_env=http://livestage.trulia.com -DtestngFile=consumer_funnel/smoke/testng-fe-ie10.xml -PtestngFile=consumer_funnel/smoke/testng-fe-ie10.xml -Ptest_site_env=http://livestage.trulia.com --debug testNG
12:41:47.636 [INFO] [org.gradle.BuildLogger] Starting Build

          After we upgraded to the latest sauce-connect plugin (1.83), this happens whenever there are two jobs running at the same time and trying to connect to the tunnel.

          hinling yeung added a comment - This may be a bit old bug but we are running to this now: [EnvInject] - Loading node environment variables. Building on master in workspace / var /lib/jenkins/jobs/testng-fe-ie10.xml/workspace Fetching changes from the remote Git repository Fetching upstream changes from ssh: //git@stash.sv2.trulia.com:7999/qa/test-automation.git Checking out Revision 6d18749c0423c3d44b63dc65f101d163df89f090 (origin/master) No emails were triggered. Starting Sauce OnDemand SSH tunnel on master node Launching Sauce Connect on se2.sv2.trulia.com Time out while waiting for Sauce Connect to start, attempting to continue Sauce Connect now launched Incremented process count for selenium, now 1 [Gradle] - Launching build. [workspace] $ /usr/share/gradle/bin/gradle -Dtest_site_env=http: //livestage.trulia.com -DtestngFile=consumer_funnel/smoke/testng-fe-ie10.xml -PtestngFile=consumer_funnel/smoke/testng-fe-ie10.xml -Ptest_site_env=http://livestage.trulia.com --debug testNG 12:41:47.636 [INFO] [org.gradle.BuildLogger] Starting Build After we upgraded to the latest sauce-connect plugin (1.83), this happens whenever there are two jobs running at the same time and trying to connect to the tunnel.

          Ross Rowe added a comment -

          The latest release of the Jenkins plugin (v 1.93) enables verbose logging by default, which will output the Sauce Connect log messages to the Jenkins job console output. In addition, the latest version treats Sauce Connect timeouts as errors which will cause the build to fail.

          Ross Rowe added a comment - The latest release of the Jenkins plugin (v 1.93) enables verbose logging by default, which will output the Sauce Connect log messages to the Jenkins job console output. In addition, the latest version treats Sauce Connect timeouts as errors which will cause the build to fail.

          hinling yeung added a comment -

          just updated to the latest version and now i got this log:

          Starting Sauce OnDemand SSH tunnel on master node
Launching Sauce Connect on se2.sv2.trulia.com
Time out while waiting for Sauce Connect to start, please check the Sauce Connect log
FATAL: com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager$SauceConnectDidNotStartException: Time out while waiting for Sauce Connect to start, please check the Sauce Connect log
com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager$SauceConnectException: 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:284)
	at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$SauceConnectStarter.call(SauceOnDemandBuildWrapper.java:562)
	at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper.setUp(SauceOnDemandBuildWrapper.java:164)
	at hudson.model.Build$BuildExecution.doRun(Build.java:154)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:535)
	at hudson.model.Run.execute(Run.java:1732)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:234)
Caused by: 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:272)
	... 8 more

          hinling yeung added a comment - just updated to the latest version and now i got this log: Starting Sauce OnDemand SSH tunnel on master node Launching Sauce Connect on se2.sv2.trulia.com Time out while waiting for Sauce Connect to start, please check the Sauce Connect log FATAL: com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager$SauceConnectDidNotStartException: Time out while waiting for Sauce Connect to start, please check the Sauce Connect log com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager$SauceConnectException: 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:284) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$SauceConnectStarter.call(SauceOnDemandBuildWrapper.java:562) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper.setUp(SauceOnDemandBuildWrapper.java:164) at hudson.model.Build$BuildExecution.doRun(Build.java:154) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:535) at hudson.model.Run.execute(Run.java:1732) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:234) Caused by: 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:272) ... 8 more

          Ross Rowe added a comment -

          The latest version of the plugin will detect if Sauce Connect failed to start and if so, will throw an error which causes the build to fail. Would you be able raise a support ticket with Sauce Labs, and attach your Sauce Connect log (which is located in /tmp/sc.log by default)?

          Thanks,

          Ross

          Ross Rowe added a comment - The latest version of the plugin will detect if Sauce Connect failed to start and if so, will throw an error which causes the build to fail. Would you be able raise a support ticket with Sauce Labs, and attach your Sauce Connect log (which is located in /tmp/sc.log by default)? Thanks, Ross

          Ben Cai added a comment -

          I was had same issue. But I think i figured out the issue. Hopefully this helps:
          When running sc as a local user it will create /tmp/sc.log with limited access. Later on when running sc as a different user(or jenkins), it will attempt to open the /tmp/sc.log and get denied. To get around this just make /tmp/sc.log with escalated permissions and i believe this will fix the sc issue.

          Ben Cai added a comment - I was had same issue. But I think i figured out the issue. Hopefully this helps: When running sc as a local user it will create /tmp/sc.log with limited access. Later on when running sc as a different user(or jenkins), it will attempt to open the /tmp/sc.log and get denied. To get around this just make /tmp/sc.log with escalated permissions and i believe this will fix the sc issue.

          Tuffon Benavides added a comment -

          I'm experiencing the same issue, my Jenkins console looks very similar to hinling's. I am not having an issue with jenkins writing to sc.log because jenkins created and owns the file. After some time I wanted to add verbose logging so I added the following options "-l tuffon.sclog -v" and I got the following error:

          20150128 103526.478 [22207] Sauce Connect 4.3.6, build 1628 8a5c837
          20150128 103526.478 [22207] Error, non-option argument ''.

          The workaround for me was that I removed all the custom command line options and it no longer had issues timing out. I hope that helps.

          Tuffon Benavides added a comment - I'm experiencing the same issue, my Jenkins console looks very similar to hinling's. I am not having an issue with jenkins writing to sc.log because jenkins created and owns the file. After some time I wanted to add verbose logging so I added the following options "-l tuffon.sclog -v" and I got the following error: 20150128 103526.478 [22207] Sauce Connect 4.3.6, build 1628 8a5c837 20150128 103526.478 [22207] Error, non-option argument ''. The workaround for me was that I removed all the custom command line options and it no longer had issues timing out. I hope that helps.

          Gavin Mogan added a comment -

          I’m closing this ticket as it has been inactive for a while and it seems to have a solution. If there is still a problem feel free to re-open or contact support@saucelabs.com

          Gavin Mogan added a comment - I’m closing this ticket as it has been inactive for a while and it seems to have a solution. If there is still a problem feel free to re-open or contact support@saucelabs.com

            rossrowe Ross Rowe
            bram_rongen Bram Rongen
            Votes:
            3 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: