How can I get journal logs in a systemd --user OnFailure unit (journalctl not working)
Systemd provides the OnFailure= mechanism for invoking actions upon failure. The most obvious use for this is to act like cron's MAILTO= and email logs when a unit fails. I tried that under Ubuntu 16.04 with this approach in a .service unit that gets started by OnFailure=
ExecStart=/bin/sh -c 'journalctl --user-unit=<my unit> -n 20 | mail -s "Unit failed" <my email address>'
This gets no output from journalctl. The exact same command, starting from /bin/sh, functions perfectly when executed from the shell prompt.
I've filed this as a bug on Ubuntu (https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1810351), but if I'm to use the systemd features that replace cron, inotify, inetd, etc. then I must have basic error reporting and I cannot wait for the bug fix. Does anyone know of a workaround for this fundamental flaw in journalctl/systemd?
ubuntu systemd systemd-journald
asked Jan 3 at 17:58
E GowE Gow
161
add a comment |
Systemd provides the OnFailure= mechanism for invoking actions upon failure. The most obvious use for this is to act like cron's MAILTO= and email logs when a unit fails. I tried that under Ubuntu 16.04 with this approach in a .service unit that gets started by OnFailure=
ExecStart=/bin/sh -c 'journalctl --user-unit=<my unit> -n 20 | mail -s "Unit failed" <my email address>'
This gets no output from journalctl. The exact same command, starting from /bin/sh, functions perfectly when executed from the shell prompt.
I've filed this as a bug on Ubuntu (https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1810351), but if I'm to use the systemd features that replace cron, inotify, inetd, etc. then I must have basic error reporting and I cannot wait for the bug fix. Does anyone know of a workaround for this fundamental flaw in journalctl/systemd?
ubuntu systemd systemd-journald
asked Jan 3 at 17:58
E GowE Gow
161
add a comment |
Systemd provides the OnFailure= mechanism for invoking actions upon failure. The most obvious use for this is to act like cron's MAILTO= and email logs when a unit fails. I tried that under Ubuntu 16.04 with this approach in a .service unit that gets started by OnFailure=
ExecStart=/bin/sh -c 'journalctl --user-unit=<my unit> -n 20 | mail -s "Unit failed" <my email address>'
This gets no output from journalctl. The exact same command, starting from /bin/sh, functions perfectly when executed from the shell prompt.
I've filed this as a bug on Ubuntu (https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1810351), but if I'm to use the systemd features that replace cron, inotify, inetd, etc. then I must have basic error reporting and I cannot wait for the bug fix. Does anyone know of a workaround for this fundamental flaw in journalctl/systemd?
ubuntu systemd systemd-journald
asked Jan 3 at 17:58
E GowE Gow
161
Systemd provides the OnFailure= mechanism for invoking actions upon failure. The most obvious use for this is to act like cron's MAILTO= and email logs when a unit fails. I tried that under Ubuntu 16.04 with this approach in a .service unit that gets started by OnFailure=
ExecStart=/bin/sh -c 'journalctl --user-unit=<my unit> -n 20 | mail -s "Unit failed" <my email address>'
This gets no output from journalctl. The exact same command, starting from /bin/sh, functions perfectly when executed from the shell prompt.
I've filed this as a bug on Ubuntu (https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1810351), but if I'm to use the systemd features that replace cron, inotify, inetd, etc. then I must have basic error reporting and I cannot wait for the bug fix. Does anyone know of a workaround for this fundamental flaw in journalctl/systemd?
ubuntu systemd systemd-journald
ubuntu systemd systemd-journald
asked Jan 3 at 17:58
E GowE Gow
161
asked Jan 3 at 17:58
E GowE Gow
161
asked Jan 3 at 17:58
E GowE Gow
161
asked Jan 3 at 17:58
E GowE Gow
161
asked Jan 3 at 17:58
E GowE Gow
161
161
add a comment |
add a comment |
0
active
oldest
votes
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
});
}
});
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%2fstackoverflow.com%2fquestions%2f54027450%2fhow-can-i-get-journal-logs-in-a-systemd-user-onfailure-unit-journalctl-not-wo%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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.
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%2fstackoverflow.com%2fquestions%2f54027450%2fhow-can-i-get-journal-logs-in-a-systemd-user-onfailure-unit-journalctl-not-wo%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
