Failed to get properties: No such interface '' in Ubuntu 16.04.3 LTS
I Created this Unit file tdk-api.service in the /etc/systemd/system folder with this permissions: -rwxr-xr-x
with this content:
[Unit]
Description = tdk API daemon
[Service]
Type = simple
ExecStart = /usr/local/bin/start-tdk-api.sh
ExecStop = /usr/local/bin/stop-tdk-api.sh
ExecReload = /usr/local/bin/reload-tdk-api.sh
[Install]
WantedBy = multi-user.target
But I have an error when starting:
root@localhost:/etc/systemd/system# sudo systemctl start tdk-api
Failed to start tdk-api.service: Unknown unit: tdk-api.service
See system logs and 'systemctl status tdk-api.service' for details.
root@localhost:/etc/systemd/system# systemctl status tdk-api.service
Failed to get properties: No such interface ''
root@localhost:/etc/systemd/system#
I also tried to reload systemd daemon, as suggested
systemctl daemon-reload
I also tried:
root@localhost:/etc/systemd/system# systemctl enable tdk-api.service
Configuration file /etc/systemd/system/tdk-api.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Created symlink /etc/systemd/system/multi-user.target.wants/tdk-api.service, pointing to /etc/systemd/system/tdk-api.service.
root@localhost:/etc/systemd/system# sudo systemctl start tdk-api
Failed to start tdk-api.service: Unknown unit: tdk-api.service
See system logs and 'systemctl status tdk-api.service' for details.
root@localhost:/etc/systemd/system# systemctl status tdk-api.service
Failed to get properties: No such interface ''
16.04 services
asked Jan 5 at 17:24
Nuñito de la CalzadaNuñito de la Calzada
687
add a comment |
I Created this Unit file tdk-api.service in the /etc/systemd/system folder with this permissions: -rwxr-xr-x
with this content:
[Unit]
Description = tdk API daemon
[Service]
Type = simple
ExecStart = /usr/local/bin/start-tdk-api.sh
ExecStop = /usr/local/bin/stop-tdk-api.sh
ExecReload = /usr/local/bin/reload-tdk-api.sh
[Install]
WantedBy = multi-user.target
But I have an error when starting:
root@localhost:/etc/systemd/system# sudo systemctl start tdk-api
Failed to start tdk-api.service: Unknown unit: tdk-api.service
See system logs and 'systemctl status tdk-api.service' for details.
root@localhost:/etc/systemd/system# systemctl status tdk-api.service
Failed to get properties: No such interface ''
root@localhost:/etc/systemd/system#
I also tried to reload systemd daemon, as suggested
systemctl daemon-reload
I also tried:
root@localhost:/etc/systemd/system# systemctl enable tdk-api.service
Configuration file /etc/systemd/system/tdk-api.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Created symlink /etc/systemd/system/multi-user.target.wants/tdk-api.service, pointing to /etc/systemd/system/tdk-api.service.
root@localhost:/etc/systemd/system# sudo systemctl start tdk-api
Failed to start tdk-api.service: Unknown unit: tdk-api.service
See system logs and 'systemctl status tdk-api.service' for details.
root@localhost:/etc/systemd/system# systemctl status tdk-api.service
Failed to get properties: No such interface ''
16.04 services
asked Jan 5 at 17:24
Nuñito de la CalzadaNuñito de la Calzada
687
1
the systemctl file works, the error is in to the sh scripts. I try out the same systemctl file with some script just perform an echo and it works.
– AtomiX84
Jan 9 at 12:36
add a comment |
I Created this Unit file tdk-api.service in the /etc/systemd/system folder with this permissions: -rwxr-xr-x
with this content:
[Unit]
Description = tdk API daemon
[Service]
Type = simple
ExecStart = /usr/local/bin/start-tdk-api.sh
ExecStop = /usr/local/bin/stop-tdk-api.sh
ExecReload = /usr/local/bin/reload-tdk-api.sh
[Install]
WantedBy = multi-user.target
But I have an error when starting:
root@localhost:/etc/systemd/system# sudo systemctl start tdk-api
Failed to start tdk-api.service: Unknown unit: tdk-api.service
See system logs and 'systemctl status tdk-api.service' for details.
root@localhost:/etc/systemd/system# systemctl status tdk-api.service
Failed to get properties: No such interface ''
root@localhost:/etc/systemd/system#
I also tried to reload systemd daemon, as suggested
systemctl daemon-reload
I also tried:
root@localhost:/etc/systemd/system# systemctl enable tdk-api.service
Configuration file /etc/systemd/system/tdk-api.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Created symlink /etc/systemd/system/multi-user.target.wants/tdk-api.service, pointing to /etc/systemd/system/tdk-api.service.
root@localhost:/etc/systemd/system# sudo systemctl start tdk-api
Failed to start tdk-api.service: Unknown unit: tdk-api.service
See system logs and 'systemctl status tdk-api.service' for details.
root@localhost:/etc/systemd/system# systemctl status tdk-api.service
Failed to get properties: No such interface ''
16.04 services
asked Jan 5 at 17:24
Nuñito de la CalzadaNuñito de la Calzada
687
I Created this Unit file tdk-api.service in the /etc/systemd/system folder with this permissions: -rwxr-xr-x
with this content:
[Unit]
Description = tdk API daemon
[Service]
Type = simple
ExecStart = /usr/local/bin/start-tdk-api.sh
ExecStop = /usr/local/bin/stop-tdk-api.sh
ExecReload = /usr/local/bin/reload-tdk-api.sh
[Install]
WantedBy = multi-user.target
But I have an error when starting:
root@localhost:/etc/systemd/system# sudo systemctl start tdk-api
Failed to start tdk-api.service: Unknown unit: tdk-api.service
See system logs and 'systemctl status tdk-api.service' for details.
root@localhost:/etc/systemd/system# systemctl status tdk-api.service
Failed to get properties: No such interface ''
root@localhost:/etc/systemd/system#
I also tried to reload systemd daemon, as suggested
systemctl daemon-reload
I also tried:
root@localhost:/etc/systemd/system# systemctl enable tdk-api.service
Configuration file /etc/systemd/system/tdk-api.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Created symlink /etc/systemd/system/multi-user.target.wants/tdk-api.service, pointing to /etc/systemd/system/tdk-api.service.
root@localhost:/etc/systemd/system# sudo systemctl start tdk-api
Failed to start tdk-api.service: Unknown unit: tdk-api.service
See system logs and 'systemctl status tdk-api.service' for details.
root@localhost:/etc/systemd/system# systemctl status tdk-api.service
Failed to get properties: No such interface ''
16.04 services
16.04 services
asked Jan 5 at 17:24
Nuñito de la CalzadaNuñito de la Calzada
687
asked Jan 5 at 17:24
Nuñito de la CalzadaNuñito de la Calzada
687
asked Jan 5 at 17:24
Nuñito de la CalzadaNuñito de la Calzada
687
asked Jan 5 at 17:24
Nuñito de la CalzadaNuñito de la Calzada
687
asked Jan 5 at 17:24
Nuñito de la CalzadaNuñito de la Calzada
687
687
1
the systemctl file works, the error is in to the sh scripts. I try out the same systemctl file with some script just perform an echo and it works.
– AtomiX84
Jan 9 at 12:36
add a comment |
1
the systemctl file works, the error is in to the sh scripts. I try out the same systemctl file with some script just perform an echo and it works.
– AtomiX84
Jan 9 at 12:36
1
1
the systemctl file works, the error is in to the sh scripts. I try out the same systemctl file with some script just perform an echo and it works.
– AtomiX84
Jan 9 at 12:36
the systemctl file works, the error is in to the sh scripts. I try out the same systemctl file with some script just perform an echo and it works.
– AtomiX84
Jan 9 at 12:36
add a comment |
1 Answer
1
active
oldest
votes
The error is in start-tdk-api.sh. I'm guessing either an environment variable is not set (like PATH) or you're not executing in the directory you think you're in.
You can set environment variables in the service file or update the PATH variable in the script (probably the easiest).
You can also set the working directory for the script in the service file:
[Service]
WorkingDirectory=/directory/to/run/from
answered Jan 11 at 15:28
Ed KingEd King
1861
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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%2faskubuntu.com%2fquestions%2f1107227%2ffailed-to-get-properties-no-such-interface-in-ubuntu-16-04-3-lts%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
The error is in start-tdk-api.sh. I'm guessing either an environment variable is not set (like PATH) or you're not executing in the directory you think you're in.
You can set environment variables in the service file or update the PATH variable in the script (probably the easiest).
You can also set the working directory for the script in the service file:
[Service]
WorkingDirectory=/directory/to/run/from
answered Jan 11 at 15:28
Ed KingEd King
1861
add a comment |
The error is in start-tdk-api.sh. I'm guessing either an environment variable is not set (like PATH) or you're not executing in the directory you think you're in.
You can set environment variables in the service file or update the PATH variable in the script (probably the easiest).
You can also set the working directory for the script in the service file:
[Service]
WorkingDirectory=/directory/to/run/from
answered Jan 11 at 15:28
Ed KingEd King
1861
add a comment |
The error is in start-tdk-api.sh. I'm guessing either an environment variable is not set (like PATH) or you're not executing in the directory you think you're in.
You can set environment variables in the service file or update the PATH variable in the script (probably the easiest).
You can also set the working directory for the script in the service file:
[Service]
WorkingDirectory=/directory/to/run/from
answered Jan 11 at 15:28
Ed KingEd King
1861
The error is in start-tdk-api.sh. I'm guessing either an environment variable is not set (like PATH) or you're not executing in the directory you think you're in.
You can set environment variables in the service file or update the PATH variable in the script (probably the easiest).
You can also set the working directory for the script in the service file:
[Service]
WorkingDirectory=/directory/to/run/from
answered Jan 11 at 15:28
Ed KingEd King
1861
answered Jan 11 at 15:28
Ed KingEd King
1861
answered Jan 11 at 15:28
Ed KingEd King
1861
answered Jan 11 at 15:28
Ed KingEd King
1861
1861
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- 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%2faskubuntu.com%2fquestions%2f1107227%2ffailed-to-get-properties-no-such-interface-in-ubuntu-16-04-3-lts%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
1
the systemctl file works, the error is in to the sh scripts. I try out the same systemctl file with some script just perform an echo and it works.
– AtomiX84
Jan 9 at 12:36