jenkins slave on mac failing at startup

I am trying to start jenkins slave on mac mini with following /Library/LaunchDaemons/com.jenkins.ci.plist

    <?xml version="1.0" encoding="UTF-8"?>

    <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

    <plist version="1.0">

    <dict>

        <key>Label</key>

        <string>com.jenkins.ci</string>

        <key>UserName</key>

        <string>jenkins</string>

        <key>SessionCreate</key>

        <true/>

        <key>ProgramArguments</key>

        <array>

            <string>/usr/bin/java</string>

            <string>-Djava.awt.headless=true</string>

            <string>-jar</string>

            <string>/Users/jenkins/agent.jar</string>

            <string>-jnlpUrl</string>

            <string>http://jenkins2.domain.net:8080/computer/jenkins-mac/slave-agent.jnlp</string>

            <string>-secret</string>

            <string>23erft6yhujnhyujnbftyujbvcdrtyhbvcxswedaw</string>

            <string>-workDir</string>

            <string>"/Users/jenkins/jenkins_slave/"</string>

        </array>

        <key>RunAtLoad</key>

        <true/>

        <key>KeepAlive</key>

        <true/>

        <key>StandardErrorPath</key>

        <string>/Users/jenkins/error.log</string>

        <key>StandardOutPath</key>

        <string>/Users/jenkins/stdout.log</string>

    </dict>

    </plist>

Then
sudo launchctl load /Library/LaunchDaemons/com.jenkins.ci.plist

But in the /Users/jenkins/error.log

I see

    Exception in thread "main" java.io.IOException: The specified working directory should be fully accessible to the remoting executable (RWX): "/Users/jenkins/jenkins_slave/"

        at org.jenkinsci.remoting.engine.WorkDirManager.verifyDirectory(WorkDirManager.java:249)

        at org.jenkinsci.remoting.engine.WorkDirManager.initializeWorkDir(WorkDirManager.java:202)

        at hudson.remoting.Launcher.run(Launcher.java:300)

        at hudson.remoting.Launcher.main(Launcher.java:283)

I have opened up /Users/jenkins/jenkins_slave/ with 777 still getting this error.

If I run following on mac as jenkins user, it works

/usr/bin/java -Djava.awt.headless=true -jar /Users/jenkins/agent.jar -jnlpUrl http://jenkins2.domain.net:8080/computer/jenkins-mac/slave-agent.jnlp -secret 23erft6yhujnhyujnbftyujbvcdrtyhbvcxswedaw -workDir "/Users/jenkins/jenkins_slave/"

Anyone knows what's wrong here ?

I am on :

ProductName: Mac OS X

ProductVersion: 10.14.1

BuildVersion: 18B75

edited Dec 6 '18 at 22:13

asked Nov 19 '18 at 19:42

roy

1,27862972

have you looked into this stackoverflow.com/questions/39794811/…... Mostly it looks like a permission issue, just do a chown.
– rohit thomas
Nov 26 '18 at 3:02

I tried whatever solution mentioned on this, but didn't fix the issue I am having
– roy
Nov 26 '18 at 14:24

add a comment |

I am trying to start jenkins slave on mac mini with following /Library/LaunchDaemons/com.jenkins.ci.plist

    <?xml version="1.0" encoding="UTF-8"?>

    <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

    <plist version="1.0">

    <dict>

        <key>Label</key>

        <string>com.jenkins.ci</string>

        <key>UserName</key>

        <string>jenkins</string>

        <key>SessionCreate</key>

        <true/>

        <key>ProgramArguments</key>

        <array>

            <string>/usr/bin/java</string>

            <string>-Djava.awt.headless=true</string>

            <string>-jar</string>

            <string>/Users/jenkins/agent.jar</string>

            <string>-jnlpUrl</string>

            <string>http://jenkins2.domain.net:8080/computer/jenkins-mac/slave-agent.jnlp</string>

            <string>-secret</string>

            <string>23erft6yhujnhyujnbftyujbvcdrtyhbvcxswedaw</string>

            <string>-workDir</string>

            <string>"/Users/jenkins/jenkins_slave/"</string>

        </array>

        <key>RunAtLoad</key>

        <true/>

        <key>KeepAlive</key>

        <true/>

        <key>StandardErrorPath</key>

        <string>/Users/jenkins/error.log</string>

        <key>StandardOutPath</key>

        <string>/Users/jenkins/stdout.log</string>

    </dict>

    </plist>

Then
sudo launchctl load /Library/LaunchDaemons/com.jenkins.ci.plist

But in the /Users/jenkins/error.log

I see

    Exception in thread "main" java.io.IOException: The specified working directory should be fully accessible to the remoting executable (RWX): "/Users/jenkins/jenkins_slave/"

        at org.jenkinsci.remoting.engine.WorkDirManager.verifyDirectory(WorkDirManager.java:249)

        at org.jenkinsci.remoting.engine.WorkDirManager.initializeWorkDir(WorkDirManager.java:202)

        at hudson.remoting.Launcher.run(Launcher.java:300)

        at hudson.remoting.Launcher.main(Launcher.java:283)

I have opened up /Users/jenkins/jenkins_slave/ with 777 still getting this error.

If I run following on mac as jenkins user, it works

Anyone knows what's wrong here ?

I am on :

ProductName: Mac OS X

ProductVersion: 10.14.1

BuildVersion: 18B75

edited Dec 6 '18 at 22:13

asked Nov 19 '18 at 19:42

roy

1,27862972

have you looked into this stackoverflow.com/questions/39794811/…... Mostly it looks like a permission issue, just do a chown.
– rohit thomas
Nov 26 '18 at 3:02

I tried whatever solution mentioned on this, but didn't fix the issue I am having
– roy
Nov 26 '18 at 14:24

add a comment |

I am trying to start jenkins slave on mac mini with following /Library/LaunchDaemons/com.jenkins.ci.plist

    <?xml version="1.0" encoding="UTF-8"?>

    <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

    <plist version="1.0">

    <dict>

        <key>Label</key>

        <string>com.jenkins.ci</string>

        <key>UserName</key>

        <string>jenkins</string>

        <key>SessionCreate</key>

        <true/>

        <key>ProgramArguments</key>

        <array>

            <string>/usr/bin/java</string>

            <string>-Djava.awt.headless=true</string>

            <string>-jar</string>

            <string>/Users/jenkins/agent.jar</string>

            <string>-jnlpUrl</string>

            <string>http://jenkins2.domain.net:8080/computer/jenkins-mac/slave-agent.jnlp</string>

            <string>-secret</string>

            <string>23erft6yhujnhyujnbftyujbvcdrtyhbvcxswedaw</string>

            <string>-workDir</string>

            <string>"/Users/jenkins/jenkins_slave/"</string>

        </array>

        <key>RunAtLoad</key>

        <true/>

        <key>KeepAlive</key>

        <true/>

        <key>StandardErrorPath</key>

        <string>/Users/jenkins/error.log</string>

        <key>StandardOutPath</key>

        <string>/Users/jenkins/stdout.log</string>

    </dict>

    </plist>

Then
sudo launchctl load /Library/LaunchDaemons/com.jenkins.ci.plist

But in the /Users/jenkins/error.log

I see

    Exception in thread "main" java.io.IOException: The specified working directory should be fully accessible to the remoting executable (RWX): "/Users/jenkins/jenkins_slave/"

        at org.jenkinsci.remoting.engine.WorkDirManager.verifyDirectory(WorkDirManager.java:249)

        at org.jenkinsci.remoting.engine.WorkDirManager.initializeWorkDir(WorkDirManager.java:202)

        at hudson.remoting.Launcher.run(Launcher.java:300)

        at hudson.remoting.Launcher.main(Launcher.java:283)

I have opened up /Users/jenkins/jenkins_slave/ with 777 still getting this error.

If I run following on mac as jenkins user, it works

Anyone knows what's wrong here ?

I am on :

ProductName: Mac OS X

ProductVersion: 10.14.1

BuildVersion: 18B75

edited Dec 6 '18 at 22:13

asked Nov 19 '18 at 19:42

roy

1,27862972

I am trying to start jenkins slave on mac mini with following /Library/LaunchDaemons/com.jenkins.ci.plist

    <?xml version="1.0" encoding="UTF-8"?>

    <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

    <plist version="1.0">

    <dict>

        <key>Label</key>

        <string>com.jenkins.ci</string>

        <key>UserName</key>

        <string>jenkins</string>

        <key>SessionCreate</key>

        <true/>

        <key>ProgramArguments</key>

        <array>

            <string>/usr/bin/java</string>

            <string>-Djava.awt.headless=true</string>

            <string>-jar</string>

            <string>/Users/jenkins/agent.jar</string>

            <string>-jnlpUrl</string>

            <string>http://jenkins2.domain.net:8080/computer/jenkins-mac/slave-agent.jnlp</string>

            <string>-secret</string>

            <string>23erft6yhujnhyujnbftyujbvcdrtyhbvcxswedaw</string>

            <string>-workDir</string>

            <string>"/Users/jenkins/jenkins_slave/"</string>

        </array>

        <key>RunAtLoad</key>

        <true/>

        <key>KeepAlive</key>

        <true/>

        <key>StandardErrorPath</key>

        <string>/Users/jenkins/error.log</string>

        <key>StandardOutPath</key>

        <string>/Users/jenkins/stdout.log</string>

    </dict>

    </plist>

Then
sudo launchctl load /Library/LaunchDaemons/com.jenkins.ci.plist

But in the /Users/jenkins/error.log

I see

    Exception in thread "main" java.io.IOException: The specified working directory should be fully accessible to the remoting executable (RWX): "/Users/jenkins/jenkins_slave/"

        at org.jenkinsci.remoting.engine.WorkDirManager.verifyDirectory(WorkDirManager.java:249)

        at org.jenkinsci.remoting.engine.WorkDirManager.initializeWorkDir(WorkDirManager.java:202)

        at hudson.remoting.Launcher.run(Launcher.java:300)

        at hudson.remoting.Launcher.main(Launcher.java:283)

I have opened up /Users/jenkins/jenkins_slave/ with 777 still getting this error.

If I run following on mac as jenkins user, it works

Anyone knows what's wrong here ?

I am on :

ProductName: Mac OS X

ProductVersion: 10.14.1

BuildVersion: 18B75

macos unix jenkins jenkins-slave launchctl

edited Dec 6 '18 at 22:13

asked Nov 19 '18 at 19:42

roy

1,27862972

edited Dec 6 '18 at 22:13

asked Nov 19 '18 at 19:42

roy

1,27862972

edited Dec 6 '18 at 22:13

asked Nov 19 '18 at 19:42

roy

1,27862972

asked Nov 19 '18 at 19:42

roy

1,27862972

asked Nov 19 '18 at 19:42

roy

1,27862972

have you looked into this stackoverflow.com/questions/39794811/…... Mostly it looks like a permission issue, just do a chown.
– rohit thomas
Nov 26 '18 at 3:02

I tried whatever solution mentioned on this, but didn't fix the issue I am having
– roy
Nov 26 '18 at 14:24

add a comment |

have you looked into this stackoverflow.com/questions/39794811/…... Mostly it looks like a permission issue, just do a chown.
– rohit thomas
Nov 26 '18 at 3:02

I tried whatever solution mentioned on this, but didn't fix the issue I am having
– roy
Nov 26 '18 at 14:24

have you looked into this stackoverflow.com/questions/39794811/…... Mostly it looks like a permission issue, just do a chown.
– rohit thomas
Nov 26 '18 at 3:02

I tried whatever solution mentioned on this, but didn't fix the issue I am having
– roy
Nov 26 '18 at 14:24

add a comment |

1 Answer
1

active

oldest

votes

+25

So the reason it works for "jenkins" user is because Jenkins creates a Application account with jenkins user which has permissions to run/access Jenkins(and its folders- in your case -workDir "/Users/jenkins/jenkins_slave/"). That is why jenkins can run the command but when you try to run it with sudo it fails.

Why does it fail with sudo ?

That's mainly because there is directory higher in the tree where you do not have execute permission, so even with 777, you will still not be able to run it.

Instead do a chown or usermod on the directory to the user that you wish to get access

sudo usermod -a -G rohit git

for more information https://askubuntu.com/questions/812513/permission-denied-in-777-folder

answered Nov 27 '18 at 2:57

rohit thomas

1,871518

I can open up /Users/jenkins/ with 777, but I don't think that's appropriate here. If jenkins slave starting as jenkins user, then why its not able to access /Users/jenkins/jenkins_slave/ ?
– roy
Nov 28 '18 at 16:06

You shouldn't give full access to any folder/directory instead give permission to own the directory which the above answer does... As for the slave issue have you confirmed that you are using the same user ?? there is also an option "Run as user who Triggered build" for a more detailed explanation stackoverflow.com/questions/44453529/jenkins-slave-runs-as-user
– rohit thomas
Nov 29 '18 at 2:06

I am getting mentioned error when jenkins slave start on Mac Mini. Not at the time of build. Also in com.jenkins.ci.plist file I am specifying UserName with which user to start the slave process.
– roy
Nov 29 '18 at 20:51

Have you tried login into the server with this "UserName" and tried running the command directly ?? Most probably the user will not have access.
– rohit thomas
Nov 30 '18 at 3:09

Yes I have mentioned this into my original post above.
– roy
Nov 30 '18 at 14:59

add a comment |

Your Answer

StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53381576%2fjenkins-slave-on-mac-failing-at-startup%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

+25

Why does it fail with sudo ?

That's mainly because there is directory higher in the tree where you do not have execute permission, so even with 777, you will still not be able to run it.

Instead do a chown or usermod on the directory to the user that you wish to get access

sudo usermod -a -G rohit git

for more information https://askubuntu.com/questions/812513/permission-denied-in-777-folder

answered Nov 27 '18 at 2:57

rohit thomas

1,871518

I can open up /Users/jenkins/ with 777, but I don't think that's appropriate here. If jenkins slave starting as jenkins user, then why its not able to access /Users/jenkins/jenkins_slave/ ?
– roy
Nov 28 '18 at 16:06

You shouldn't give full access to any folder/directory instead give permission to own the directory which the above answer does... As for the slave issue have you confirmed that you are using the same user ?? there is also an option "Run as user who Triggered build" for a more detailed explanation stackoverflow.com/questions/44453529/jenkins-slave-runs-as-user
– rohit thomas
Nov 29 '18 at 2:06

I am getting mentioned error when jenkins slave start on Mac Mini. Not at the time of build. Also in com.jenkins.ci.plist file I am specifying UserName with which user to start the slave process.
– roy
Nov 29 '18 at 20:51

Have you tried login into the server with this "UserName" and tried running the command directly ?? Most probably the user will not have access.
– rohit thomas
Nov 30 '18 at 3:09

Yes I have mentioned this into my original post above.
– roy
Nov 30 '18 at 14:59

add a comment |

+25

Why does it fail with sudo ?

That's mainly because there is directory higher in the tree where you do not have execute permission, so even with 777, you will still not be able to run it.

Instead do a chown or usermod on the directory to the user that you wish to get access

sudo usermod -a -G rohit git

for more information https://askubuntu.com/questions/812513/permission-denied-in-777-folder

answered Nov 27 '18 at 2:57

rohit thomas

1,871518

I can open up /Users/jenkins/ with 777, but I don't think that's appropriate here. If jenkins slave starting as jenkins user, then why its not able to access /Users/jenkins/jenkins_slave/ ?
– roy
Nov 28 '18 at 16:06

You shouldn't give full access to any folder/directory instead give permission to own the directory which the above answer does... As for the slave issue have you confirmed that you are using the same user ?? there is also an option "Run as user who Triggered build" for a more detailed explanation stackoverflow.com/questions/44453529/jenkins-slave-runs-as-user
– rohit thomas
Nov 29 '18 at 2:06

I am getting mentioned error when jenkins slave start on Mac Mini. Not at the time of build. Also in com.jenkins.ci.plist file I am specifying UserName with which user to start the slave process.
– roy
Nov 29 '18 at 20:51

Have you tried login into the server with this "UserName" and tried running the command directly ?? Most probably the user will not have access.
– rohit thomas
Nov 30 '18 at 3:09

Yes I have mentioned this into my original post above.
– roy
Nov 30 '18 at 14:59

add a comment |

+25

Why does it fail with sudo ?

That's mainly because there is directory higher in the tree where you do not have execute permission, so even with 777, you will still not be able to run it.

Instead do a chown or usermod on the directory to the user that you wish to get access

sudo usermod -a -G rohit git

for more information https://askubuntu.com/questions/812513/permission-denied-in-777-folder

answered Nov 27 '18 at 2:57

rohit thomas

1,871518

Why does it fail with sudo ?

That's mainly because there is directory higher in the tree where you do not have execute permission, so even with 777, you will still not be able to run it.

Instead do a chown or usermod on the directory to the user that you wish to get access

sudo usermod -a -G rohit git

for more information https://askubuntu.com/questions/812513/permission-denied-in-777-folder

answered Nov 27 '18 at 2:57

rohit thomas

1,871518

answered Nov 27 '18 at 2:57

rohit thomas

1,871518

answered Nov 27 '18 at 2:57

rohit thomas

1,871518

answered Nov 27 '18 at 2:57

rohit thomas

1,871518

I can open up /Users/jenkins/ with 777, but I don't think that's appropriate here. If jenkins slave starting as jenkins user, then why its not able to access /Users/jenkins/jenkins_slave/ ?
– roy
Nov 28 '18 at 16:06

You shouldn't give full access to any folder/directory instead give permission to own the directory which the above answer does... As for the slave issue have you confirmed that you are using the same user ?? there is also an option "Run as user who Triggered build" for a more detailed explanation stackoverflow.com/questions/44453529/jenkins-slave-runs-as-user
– rohit thomas
Nov 29 '18 at 2:06

I am getting mentioned error when jenkins slave start on Mac Mini. Not at the time of build. Also in com.jenkins.ci.plist file I am specifying UserName with which user to start the slave process.
– roy
Nov 29 '18 at 20:51

Have you tried login into the server with this "UserName" and tried running the command directly ?? Most probably the user will not have access.
– rohit thomas
Nov 30 '18 at 3:09

Yes I have mentioned this into my original post above.
– roy
Nov 30 '18 at 14:59

add a comment |

I can open up /Users/jenkins/ with 777, but I don't think that's appropriate here. If jenkins slave starting as jenkins user, then why its not able to access /Users/jenkins/jenkins_slave/ ?
– roy
Nov 28 '18 at 16:06

You shouldn't give full access to any folder/directory instead give permission to own the directory which the above answer does... As for the slave issue have you confirmed that you are using the same user ?? there is also an option "Run as user who Triggered build" for a more detailed explanation stackoverflow.com/questions/44453529/jenkins-slave-runs-as-user
– rohit thomas
Nov 29 '18 at 2:06

I am getting mentioned error when jenkins slave start on Mac Mini. Not at the time of build. Also in com.jenkins.ci.plist file I am specifying UserName with which user to start the slave process.
– roy
Nov 29 '18 at 20:51

Have you tried login into the server with this "UserName" and tried running the command directly ?? Most probably the user will not have access.
– rohit thomas
Nov 30 '18 at 3:09

Yes I have mentioned this into my original post above.
– roy
Nov 30 '18 at 14:59

I can open up /Users/jenkins/ with 777, but I don't think that's appropriate here. If jenkins slave starting as jenkins user, then why its not able to access /Users/jenkins/jenkins_slave/ ?
– roy
Nov 28 '18 at 16:06

You shouldn't give full access to any folder/directory instead give permission to own the directory which the above answer does... As for the slave issue have you confirmed that you are using the same user ?? there is also an option "Run as user who Triggered build" for a more detailed explanation stackoverflow.com/questions/44453529/jenkins-slave-runs-as-user
– rohit thomas
Nov 29 '18 at 2:06

I am getting mentioned error when jenkins slave start on Mac Mini. Not at the time of build. Also in com.jenkins.ci.plist file I am specifying UserName with which user to start the slave process.
– roy
Nov 29 '18 at 20:51

Have you tried login into the server with this "UserName" and tried running the command directly ?? Most probably the user will not have access.
– rohit thomas
Nov 30 '18 at 3:09

Yes I have mentioned this into my original post above.
– roy
Nov 30 '18 at 14:59

add a comment |

draft saved

draft discarded

Thanks for contributing an answer to Stack Overflow!

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

Some of your past answers have not been well-received, and you're in danger of being blocked from answering.

Please pay close attention to the following guidance:

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

Search This Blog

Ufyukyu