[Bug 1618188] Re: systemd journal should be persistent by default: /var/log/journal should be created; remove rsyslog from default installs
I understand it is not desirable to have duplicate logging, but there is a corner case where logging that is done during systemd shutdown is lost because rsyslog is killed. This makes shutdown look broken due to it being non-deterministic exactly when rsyslog is killed. Currently, the easiest way to get accurate logging is creating /var/log/journal. ## Sometimes shutdown logs are brief: Oct 13 18:51:07 HOST systemd[1]: Stopped target Cloud-init target. Oct 13 18:51:07 HOST systemd[1]: Starting Unattended Upgrades Shutdown... Oct 13 18:51:07 HOST systemd[1]: Stopping Session 1 of user ubuntu. Oct 13 18:51:07 HOST systemd[1]: Stopped target Graphical Interface. Oct 13 18:51:07 HOST systemd[1]: Stopping Accounts Service... Oct 13 18:51:07 HOST rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="759" x-info="http://www.rsyslog.com;] exiting on signal 15. ## Sometimes more detailed Oct 13 18:57:33 HOST systemd[1]: Stopping Session 1 of user ubuntu. Oct 13 18:57:33 HOST systemd[1]: Stopping User Manager for UID 1000... Oct 13 18:57:33 HOST systemd[1]: Stopped target Timers. Oct 13 18:57:33 HOST systemd[1]: Stopped Daily apt activities. Oct 13 18:57:33 HOST systemd[1277]: Reached target Shutdown. Oct 13 18:57:33 HOST systemd[1277]: Stopped target Default. Oct 13 18:57:33 HOST systemd[1277]: Stopped target Basic System. Oct 13 18:57:33 HOST systemd[1277]: Stopped target Timers. Oct 13 18:57:33 HOST systemd[1277]: Stopped target Sockets. Oct 13 18:57:33 HOST systemd[1277]: Starting Exit the Session... Oct 13 18:57:33 HOST systemd[1]: Stopped Daily Cleanup of Temporary Directories. Oct 13 18:57:33 HOST systemd[1277]: Stopped target Paths. Oct 13 18:57:33 HOST systemd[1]: Stopped target Graphical Interface. Oct 13 18:57:33 HOST systemd[1]: Stopped Timer to automatically refresh installed snaps. Oct 13 18:57:33 HOST systemd[1]: Stopping ACPI event daemon... Oct 13 18:57:33 HOST systemd[1]: Starting Unattended Upgrades Shutdown... Oct 13 18:57:33 HOST systemd[1]: Stopping Accounts Service... Oct 13 18:57:33 HOST systemd[1]: Closed Load/Save RF Kill Switch Status /dev/rfkill Watch. Oct 13 18:57:33 HOST systemd[1]: Stopping Virtual machine log manager... Oct 13 18:57:33 HOST systemd[1]: Stopped target Cloud-init target. Oct 13 18:57:33 HOST systemd[1277]: Received SIGRTMIN+24 from PID 1592 (kill). Oct 13 18:57:33 HOST systemd[1]: Stopped Execute cloud user/final scripts. Oct 13 18:57:33 HOST systemd[1]: Stopped Apply the settings specified in cloud-config. Oct 13 18:57:33 HOST systemd[1]: Stopped target Cloud-config availability. Oct 13 18:57:33 HOST rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="737" x-info="http://www.rsyslog.com;] exiting on signal 15. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1618188 Title: systemd journal should be persistent by default: /var/log/journal should be created; remove rsyslog from default installs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1618188/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918410] Re: isc-dhcp-client denied by apparmor
I have been doing Xenial -> Bionic -> Focal release upgrades and started
running into this apparmor issue with dhclient after reaching Focal.
I don't know the root issue, and it doesn't appear to impact
functionality (at least as far as I can tell on my hosts). However, I am
currently dealing with this by adding the following to
/etc/apparmor.d/local/sbin.dhclient:
@{PROC}/[0-9]*/task/[0-9]*/comm rw,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918410
Title:
isc-dhcp-client denied by apparmor
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1918410/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918410] Re: isc-dhcp-client denied by apparmor
Hi John, Thank you for your detailed response and education on command text. I was able to use pstree to see the thread command text behavior change before and after the AppArmor rule addition. I feel better now that I understand what is going on! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918410 Title: isc-dhcp-client denied by apparmor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1918410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1161012] Re: Clamav package adds proxy to config on install and update
I ran into this on an Xenial to Bionic upgrade. After the upgrade to Bionic was complete, freshclam started trying to download clamav database through my apt proxy. The database download attempts failed due to apt proxy being strictly for apt only. >From quick debugging... I think it might be related to update-manager's UpdateManager/Core/utils.py . utils.py has an init_proxy method to set the http(s)_proxy environment variables. Part of this method pulls the proxy settings from Acquire::https::Proxy before setting http(s)_proxy environment variables. I suspect it is this logic that is causing freshclam to start trying to download database updates from apt proxy on upgrade (a do-release- upgrade, in this case). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1161012 Title: Clamav package adds proxy to config on install and update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1161012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
