R. Tyler Croy created JENKINS-13207: ---------------------------------------
Summary: Sauce OnDemand fails to start up Key: JENKINS-13207 URL: https://issues.jenkins-ci.org/browse/JENKINS-13207 Project: Jenkins Issue Type: Bug Components: sauce-ondemand Reporter: R. Tyler Croy Assignee: Ross Rowe {code} * Debug messages will be sent to sauce_connect.log Exception in thread "MainThread" Traceback (most recent call last): File "<string>", line 1, in <module> File "__pyclasspath__/sauce_connect.py", line 649, in setup_logging File "/var/lib/jenkins/plugins/sauce-ondemand/WEB-INF/lib/sauce-connect-3.0.18.jar/Lib/logging/handlers.py", line 109, in __init__ File "/var/lib/jenkins/plugins/sauce-ondemand/WEB-INF/lib/sauce-connect-3.0.18.jar/Lib/logging/handlers.py", line 61, in __init__ File "/var/lib/jenkins/plugins/sauce-ondemand/WEB-INF/lib/sauce-connect-3.0.18.jar/Lib/logging/__init__.py", line 770, in __init__ IOError: (13, 'Permission denied', 'sauce_connect.log') {code} Not sure where this is being thrown, the Jenkins process can definitely access /var/lib/jenkins on the *master* (that's its home directory) Ideally this shouldn't break the connector like this, but my hunch is that some how the slave is starting the tunnel and using a current working directory from the master ({{/var/lib/jenkins}} doesn't exist on the slaves). Check out the {{FilePath}} class which should help generate safe paths on slaves -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira