Retry connect/disconnect after timeout?

[geekdave]

Sometimes SauceConnect just hangs, non-responsive on either the connection or disconnection process. Would it be possible to set a timeout, and retry the connect/disconnect process if no response received?

[bermi]

I hear your frustration with timeouts but it is going to be really hard for us to to guess when sc is responsive or not without false positives.

Have you had a chance to investigate how to detect when things are timing out?

[geekdave]

One common case is when I get this in the console output:

22 Dec 17:06:55 - GET https://saucelabs.com/rest/v1/jdoe/tunnels/4d8667d53bec41a99374e62b48dd924e: Timeout was reached.
22 Dec 17:06:55 - Error bringing up tunnel VM.

Would it be possible to detect this message in the output and retry if found?

[aearly]

I just published v0.10.3 which should handle that error output properly. You then could use something like async.retry to try again if that error occurs.

async.retry(3, launchSauceConnect.bind(null, scOptions), function (err) {
  if (err) {
    throw new Error("Sauce Connect failed to launch after 3 retries, error: " + err.message);
  }
  // sauce connect ready
})

[geekdave]

Still seeing one more instance of an unhandled error:

Starting Selenium listener...
Establishing secure TLS connection to tunnel...
Failed to start Selenium listener (exit code 2).
Please check logfile for more information.
Sauce Connect could not establish a connection.

This one happens rarely, but often enough to be noticeable, when running multiple tunnels. PR incoming...