plist and status - “127 The specified service did not ship with the operating system”
I'm trying to get a script to run via launchd, but I keep getting a status of 127 after I load it. I've checked ownership, permissions and absolute paths etc of both plist and script. I'm running it on a mac with macos 10.13.
Here's the plist:
<dict>
<key>Label</key>
<string>com.parkridge.UrlHistory</string>
<key>StartInterval</key>
<integer>21600</integer>
<key>ProgramArguments</key>
<array>
<string>/bin/sh</string>
<string>/Users/Shared/Resources/Logs.sh</string>
</array>
<key>RunAtLoad</key>
<true/>
<key>StandardOutPath</key>
<string>/dev/null</string>
<key>StandardErrorPath</key>
<string>/dev/null</string>
</dict>
I can also run the script manually and it works.
mac launchctl plist
asked Jan 25 at 15:08
JamesJames
1
add a comment |
I'm trying to get a script to run via launchd, but I keep getting a status of 127 after I load it. I've checked ownership, permissions and absolute paths etc of both plist and script. I'm running it on a mac with macos 10.13.
Here's the plist:
<dict>
<key>Label</key>
<string>com.parkridge.UrlHistory</string>
<key>StartInterval</key>
<integer>21600</integer>
<key>ProgramArguments</key>
<array>
<string>/bin/sh</string>
<string>/Users/Shared/Resources/Logs.sh</string>
</array>
<key>RunAtLoad</key>
<true/>
<key>StandardOutPath</key>
<string>/dev/null</string>
<key>StandardErrorPath</key>
<string>/dev/null</string>
</dict>
I can also run the script manually and it works.
mac launchctl plist
asked Jan 25 at 15:08
JamesJames
1
Unfortunately, 127 can mean a host of different things, but it often comes down to paths and permissions. What are the permissions and the ownership of Logs.sh?
– MMB
Jan 29 at 2:31
Thanks MMB, The permissions are set to 644 and ownership root:wheel.
– James
Jan 30 at 14:22
That's correct. Next thing I'd check is your Logs.sh script. The path launchd gets is different from what you get. When in doubt, hardcode all paths to any executables you call within the script.
– MMB
Jan 30 at 20:58
MMB, I went back and hard coded the paths... that seems to have fix it. Thank you.
– James
Feb 4 at 15:21
add a comment |
I'm trying to get a script to run via launchd, but I keep getting a status of 127 after I load it. I've checked ownership, permissions and absolute paths etc of both plist and script. I'm running it on a mac with macos 10.13.
Here's the plist:
<dict>
<key>Label</key>
<string>com.parkridge.UrlHistory</string>
<key>StartInterval</key>
<integer>21600</integer>
<key>ProgramArguments</key>
<array>
<string>/bin/sh</string>
<string>/Users/Shared/Resources/Logs.sh</string>
</array>
<key>RunAtLoad</key>
<true/>
<key>StandardOutPath</key>
<string>/dev/null</string>
<key>StandardErrorPath</key>
<string>/dev/null</string>
</dict>
I can also run the script manually and it works.
mac launchctl plist
asked Jan 25 at 15:08
JamesJames
1
I'm trying to get a script to run via launchd, but I keep getting a status of 127 after I load it. I've checked ownership, permissions and absolute paths etc of both plist and script. I'm running it on a mac with macos 10.13.
Here's the plist:
<dict>
<key>Label</key>
<string>com.parkridge.UrlHistory</string>
<key>StartInterval</key>
<integer>21600</integer>
<key>ProgramArguments</key>
<array>
<string>/bin/sh</string>
<string>/Users/Shared/Resources/Logs.sh</string>
</array>
<key>RunAtLoad</key>
<true/>
<key>StandardOutPath</key>
<string>/dev/null</string>
<key>StandardErrorPath</key>
<string>/dev/null</string>
</dict>
I can also run the script manually and it works.
mac launchctl plist
mac launchctl plist
asked Jan 25 at 15:08
JamesJames
1
asked Jan 25 at 15:08
JamesJames
1
asked Jan 25 at 15:08
JamesJames
1
asked Jan 25 at 15:08
JamesJames
1
asked Jan 25 at 15:08
JamesJames
1
1
Unfortunately, 127 can mean a host of different things, but it often comes down to paths and permissions. What are the permissions and the ownership of Logs.sh?
– MMB
Jan 29 at 2:31
Thanks MMB, The permissions are set to 644 and ownership root:wheel.
– James
Jan 30 at 14:22
That's correct. Next thing I'd check is your Logs.sh script. The path launchd gets is different from what you get. When in doubt, hardcode all paths to any executables you call within the script.
– MMB
Jan 30 at 20:58
MMB, I went back and hard coded the paths... that seems to have fix it. Thank you.
– James
Feb 4 at 15:21
add a comment |
Unfortunately, 127 can mean a host of different things, but it often comes down to paths and permissions. What are the permissions and the ownership of Logs.sh?
– MMB
Jan 29 at 2:31
Thanks MMB, The permissions are set to 644 and ownership root:wheel.
– James
Jan 30 at 14:22
That's correct. Next thing I'd check is your Logs.sh script. The path launchd gets is different from what you get. When in doubt, hardcode all paths to any executables you call within the script.
– MMB
Jan 30 at 20:58
MMB, I went back and hard coded the paths... that seems to have fix it. Thank you.
– James
Feb 4 at 15:21
Unfortunately, 127 can mean a host of different things, but it often comes down to paths and permissions. What are the permissions and the ownership of Logs.sh?
– MMB
Jan 29 at 2:31
Unfortunately, 127 can mean a host of different things, but it often comes down to paths and permissions. What are the permissions and the ownership of Logs.sh?
– MMB
Jan 29 at 2:31
Thanks MMB, The permissions are set to 644 and ownership root:wheel.
– James
Jan 30 at 14:22
Thanks MMB, The permissions are set to 644 and ownership root:wheel.
– James
Jan 30 at 14:22
That's correct. Next thing I'd check is your Logs.sh script. The path launchd gets is different from what you get. When in doubt, hardcode all paths to any executables you call within the script.
– MMB
Jan 30 at 20:58
That's correct. Next thing I'd check is your Logs.sh script. The path launchd gets is different from what you get. When in doubt, hardcode all paths to any executables you call within the script.
– MMB
Jan 30 at 20:58
MMB, I went back and hard coded the paths... that seems to have fix it. Thank you.
– James
Feb 4 at 15:21
MMB, I went back and hard coded the paths... that seems to have fix it. Thank you.
– James
Feb 4 at 15:21
add a comment |
1 Answer
1
active
oldest
votes
Unfortunately, 127 can mean a host of different things, but it often comes down to paths and permissions. The script should be owned by root:wheel and set to 644.
As for paths, launchd has PATH settings different than you, so the simplest solution is to hardcode all the paths to executables within your script.
answered Feb 5 at 8:39
MMBMMB
45326
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1398410%2fplist-and-status-127-the-specified-service-did-not-ship-with-the-operating-sy%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Unfortunately, 127 can mean a host of different things, but it often comes down to paths and permissions. The script should be owned by root:wheel and set to 644.
As for paths, launchd has PATH settings different than you, so the simplest solution is to hardcode all the paths to executables within your script.
answered Feb 5 at 8:39
MMBMMB
45326
add a comment |
Unfortunately, 127 can mean a host of different things, but it often comes down to paths and permissions. The script should be owned by root:wheel and set to 644.
As for paths, launchd has PATH settings different than you, so the simplest solution is to hardcode all the paths to executables within your script.
answered Feb 5 at 8:39
MMBMMB
45326
add a comment |
Unfortunately, 127 can mean a host of different things, but it often comes down to paths and permissions. The script should be owned by root:wheel and set to 644.
As for paths, launchd has PATH settings different than you, so the simplest solution is to hardcode all the paths to executables within your script.
answered Feb 5 at 8:39
MMBMMB
45326
Unfortunately, 127 can mean a host of different things, but it often comes down to paths and permissions. The script should be owned by root:wheel and set to 644.
As for paths, launchd has PATH settings different than you, so the simplest solution is to hardcode all the paths to executables within your script.
answered Feb 5 at 8:39
MMBMMB
45326
answered Feb 5 at 8:39
MMBMMB
45326
answered Feb 5 at 8:39
MMBMMB
45326
answered Feb 5 at 8:39
MMBMMB
45326
45326
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- 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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1398410%2fplist-and-status-127-the-specified-service-did-not-ship-with-the-operating-sy%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Unfortunately, 127 can mean a host of different things, but it often comes down to paths and permissions. What are the permissions and the ownership of Logs.sh?
– MMB
Jan 29 at 2:31
Thanks MMB, The permissions are set to 644 and ownership root:wheel.
– James
Jan 30 at 14:22
That's correct. Next thing I'd check is your Logs.sh script. The path launchd gets is different from what you get. When in doubt, hardcode all paths to any executables you call within the script.
– MMB
Jan 30 at 20:58
MMB, I went back and hard coded the paths... that seems to have fix it. Thank you.
– James
Feb 4 at 15:21