How to view output of /usr/lib/apt/apt.systemd.daily after apt-daily.service is run by systemd?
In /usr/lib/apt/apt.systemd.daily it reads that
# APT::Periodic::Verbose "0";
# - Send report mail to root
# 0: no report (or null string)
# 1: progress report (actually any string)
# 2: + command outputs (remove -qq, remove 2>/dev/null, add -
d)
# 3: + trace on
I have set
APT::Periodic::Verbose "3";
in /etc/apt/apt.conf.d/10periodic. I have set up ssmtp
to be able to send mails, and it seems to work, but I don't seem to get mails about the script's output.
16.04 server apt email debugging
add a comment |
In /usr/lib/apt/apt.systemd.daily it reads that
# APT::Periodic::Verbose "0";
# - Send report mail to root
# 0: no report (or null string)
# 1: progress report (actually any string)
# 2: + command outputs (remove -qq, remove 2>/dev/null, add -
d)
# 3: + trace on
I have set
APT::Periodic::Verbose "3";
in /etc/apt/apt.conf.d/10periodic. I have set up ssmtp
to be able to send mails, and it seems to work, but I don't seem to get mails about the script's output.
16.04 server apt email debugging
BTW In Xenial it does not output as documented in case "APT::Periodic::Verbose 2", see bug report
– jarno
Mar 26 '18 at 6:30
add a comment |
In /usr/lib/apt/apt.systemd.daily it reads that
# APT::Periodic::Verbose "0";
# - Send report mail to root
# 0: no report (or null string)
# 1: progress report (actually any string)
# 2: + command outputs (remove -qq, remove 2>/dev/null, add -
d)
# 3: + trace on
I have set
APT::Periodic::Verbose "3";
in /etc/apt/apt.conf.d/10periodic. I have set up ssmtp
to be able to send mails, and it seems to work, but I don't seem to get mails about the script's output.
16.04 server apt email debugging
In /usr/lib/apt/apt.systemd.daily it reads that
# APT::Periodic::Verbose "0";
# - Send report mail to root
# 0: no report (or null string)
# 1: progress report (actually any string)
# 2: + command outputs (remove -qq, remove 2>/dev/null, add -
d)
# 3: + trace on
I have set
APT::Periodic::Verbose "3";
in /etc/apt/apt.conf.d/10periodic. I have set up ssmtp
to be able to send mails, and it seems to work, but I don't seem to get mails about the script's output.
16.04 server apt email debugging
16.04 server apt email debugging
edited Feb 9 at 10:46
jarno
asked Jun 2 '17 at 11:31
jarnojarno
1,81532048
1,81532048
BTW In Xenial it does not output as documented in case "APT::Periodic::Verbose 2", see bug report
– jarno
Mar 26 '18 at 6:30
add a comment |
BTW In Xenial it does not output as documented in case "APT::Periodic::Verbose 2", see bug report
– jarno
Mar 26 '18 at 6:30
BTW In Xenial it does not output as documented in case "APT::Periodic::Verbose 2", see bug report
– jarno
Mar 26 '18 at 6:30
BTW In Xenial it does not output as documented in case "APT::Periodic::Verbose 2", see bug report
– jarno
Mar 26 '18 at 6:30
add a comment |
1 Answer
1
active
oldest
votes
Mail reporting may work by cron system which was used before, but not with systemd.
The output can be seen in systemd journal
journalctl -u apt-daily.service
it seems this information is lost after reboot, is there a way to prevent that from happening?
– Plumpie
Mar 21 '18 at 14:38
@Plumpie bugs.launchpad.net/ubuntu/+source/systemd/+bug/1618188
– jarno
Mar 26 '18 at 7:19
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%2f921405%2fhow-to-view-output-of-usr-lib-apt-apt-systemd-daily-after-apt-daily-service-is%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
Mail reporting may work by cron system which was used before, but not with systemd.
The output can be seen in systemd journal
journalctl -u apt-daily.service
it seems this information is lost after reboot, is there a way to prevent that from happening?
– Plumpie
Mar 21 '18 at 14:38
@Plumpie bugs.launchpad.net/ubuntu/+source/systemd/+bug/1618188
– jarno
Mar 26 '18 at 7:19
add a comment |
Mail reporting may work by cron system which was used before, but not with systemd.
The output can be seen in systemd journal
journalctl -u apt-daily.service
it seems this information is lost after reboot, is there a way to prevent that from happening?
– Plumpie
Mar 21 '18 at 14:38
@Plumpie bugs.launchpad.net/ubuntu/+source/systemd/+bug/1618188
– jarno
Mar 26 '18 at 7:19
add a comment |
Mail reporting may work by cron system which was used before, but not with systemd.
The output can be seen in systemd journal
journalctl -u apt-daily.service
Mail reporting may work by cron system which was used before, but not with systemd.
The output can be seen in systemd journal
journalctl -u apt-daily.service
answered Jun 2 '17 at 11:49
jarnojarno
1,81532048
1,81532048
it seems this information is lost after reboot, is there a way to prevent that from happening?
– Plumpie
Mar 21 '18 at 14:38
@Plumpie bugs.launchpad.net/ubuntu/+source/systemd/+bug/1618188
– jarno
Mar 26 '18 at 7:19
add a comment |
it seems this information is lost after reboot, is there a way to prevent that from happening?
– Plumpie
Mar 21 '18 at 14:38
@Plumpie bugs.launchpad.net/ubuntu/+source/systemd/+bug/1618188
– jarno
Mar 26 '18 at 7:19
it seems this information is lost after reboot, is there a way to prevent that from happening?
– Plumpie
Mar 21 '18 at 14:38
it seems this information is lost after reboot, is there a way to prevent that from happening?
– Plumpie
Mar 21 '18 at 14:38
@Plumpie bugs.launchpad.net/ubuntu/+source/systemd/+bug/1618188
– jarno
Mar 26 '18 at 7:19
@Plumpie bugs.launchpad.net/ubuntu/+source/systemd/+bug/1618188
– jarno
Mar 26 '18 at 7:19
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%2f921405%2fhow-to-view-output-of-usr-lib-apt-apt-systemd-daily-after-apt-daily-service-is%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
BTW In Xenial it does not output as documented in case "APT::Periodic::Verbose 2", see bug report
– jarno
Mar 26 '18 at 6:30