[Touch-packages] [Bug 1660316] Re: apparmor denial of CUPS
Looks like the same error in ubuntu 20.04: Jun 5 00:00:07 cmdesk01 kernel: [4025941.209572] audit: type=1400 audit(1591304407.264:388): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=1792223 comm="cups-browsed" capability=23 capname="sys_nice" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1660316 Title: apparmor denial of CUPS Status in cups package in Ubuntu: Expired Bug description: Printing is enabled when doing sudo aa-complain cupsd Here is an extract of /var/log/syslog: Jan 30 12:41:59 dag-TS-P500 kernel: [ 868.929457] audit: type=1400 audit(1485776519.269:37): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=6932 comm="apparmor_parser" Jan 30 12:41:59 dag-TS-P500 kernel: [ 868.929744] audit: type=1400 audit(1485776519.269:38): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=6932 comm="apparmor_parser" Jan 30 12:41:59 dag-TS-P500 kernel: [ 868.945422] audit: type=1400 audit(1485776519.285:39): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=6932 comm="apparmor_parser" Jan 30 12:42:10 dag-TS-P500 kernel: [ 879.817070] audit: type=1400 audit(1485776530.158:40): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=6941 comm="apparmor_parser" Jan 30 12:42:10 dag-TS-P500 kernel: [ 879.817342] audit: type=1400 audit(1485776530.158:41): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=6941 comm="apparmor_parser" Jan 30 12:42:10 dag-TS-P500 kernel: [ 879.837254] audit: type=1400 audit(1485776530.178:42): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=6941 comm="apparmor_parser" Jan 30 12:42:16 dag-TS-P500 zeitgeist-datah[3706]: downloads-directory-provider.vala:120: Couldn't process /home/dag/.glvndcEQzqA: Error when getting information for file '/home/dag/.glvndcEQzqA': No such file or directory Jan 30 12:42:23 dag-TS-P500 dbus[996]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' Jan 30 12:42:23 dag-TS-P500 systemd[1]: Starting Hostname Service... Jan 30 12:42:24 dag-TS-P500 dbus[996]: [system] Successfully activated service 'org.freedesktop.hostname1' Jan 30 12:42:24 dag-TS-P500 systemd[1]: Started Hostname Service. Jan 30 12:42:26 dag-TS-P500 kernel: [ 895.746636] audit: type=1400 audit(1485776546.086:43): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=6967 comm="lpd" capability=12 capname="net_admin" Jan 30 12:42:54 dag-TS-P500 systemd[1]: Starting Cleanup of Temporary Directories... Jan 30 12:42:54 dag-TS-P500 systemd-tmpfiles[6973]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. Jan 30 12:42:54 dag-TS-P500 systemd[1]: Started Cleanup of Temporary Directories. Jan 30 12:44:03 dag-TS-P500 dbus-daemon[2707]: Activating service name='com.ubuntu.OneConf' Jan 30 12:44:03 dag-TS-P500 dbus-daemon[2707]: Successfully activated service 'com.ubuntu.OneConf' Jan 30 12:44:03 dag-TS-P500 com.ubuntu.OneConf[2707]: WARNING:oneconf.hosts:Error in loading other_hosts file: [Errno 2] No such file or directory: '/home/dag/.cache/oneconf/d2fc3bf30c9f4976b441a8f14de53bda/other_hosts' Jan 30 12:44:23 dag-TS-P500 dbus-daemon[2707]: Activating service name='com.ubuntu.sso' Jan 30 12:44:24 dag-TS-P500 dbus-daemon[2707]: Successfully activated service 'com.ubuntu.sso' Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.685842] audit: type=1400 audit(1485776751.028:44): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=7024 comm="apparmor_parser" Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.686099] audit: type=1400 audit(1485776751.028:45): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=7024 comm="apparmor_parser" Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.700446] audit: type=1400 audit(1485776751.044:46): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=7024 comm="apparmor_parser" Jan 30 12:45:57 dag-TS-P500 kernel: [ 1106.940891] audit: type=1400 audit(1485776757.284:47): apparmor="ALLOWED" operation="capable" profile="/usr/sbin/cupsd" pid=7031 comm="lpd" capability=12 capname="net_admin" Jan 30 12:45:57 dag-TS-P500 kernel: [ 1106.940938] audit: type=1400 audit(1485776757.284:48): apparmor="ALLOWED" operation="capable" profile="/usr/sbin/cupsd" pid=7031 comm="lpd" capability=12 capname="net_admin" ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: cups
[Touch-packages] [Bug 1852903] Re: systemd Caught , dumped core
Yes, it is our custom service: # cat /var/tmp/keepsessions.service [Unit] Description=SiteTools keep sessions Wants=network-online.target Wants=docker.service After=network-online.target After=docker.service [Service] ExecStart=/opt/sitetools/keepsessions ExecStartPost=/opt/sitetools/onstart Restart=always WatchdogSec=5m Type=simple [Install] WantedBy=multi-user.target It does usual stuff, like open/close files, connect to consul, etc. Written in python3, nothing special. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1852903 Title: systemd Caught , dumped core Status in systemd package in Ubuntu: Expired Bug description: Several days ago an ubuntu 18.04 in ec2 env updated systemd and udev to 237-3ubuntu10.31 This caused systemd to segfault and stop receiving any systemctl command (they timeout). [ 198.482652] systemd[1]: segfault at 50 ip 5630ddd60200 sp 7ffc9c3ea890 error 4 in systemd (deleted)[5630ddcc1000+14e000] [ 278.664729] systemd-journald[451]: Failed to send WATCHDOG=1 notification message: Connection refused [ 368.462136] systemd-journald[451]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected [ 458.496689] systemd-journald[451]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected I downgraded to 237-3ubuntu10.29 to no avail. Then I downgraded to 237-3ubuntu10: apt install udev=237-3ubuntu10 systemd=237-3ubuntu10 systemd-sysv=237-3ubuntu10 libsystemd0:amd64=237-3ubuntu10 libudev1:amd64=237-3ubuntu10 libnss-systemd:amd64=237-3ubuntu10 and that did not help either. The machine is unusable at the moment. Attaching coredump of systemd (version 237-3ubuntu10.31) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1852903/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1852903] Re: systemd Caught , dumped core
** Attachment added: "/var/crash/_lib_systemd_systemd.0.crash" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1852903/+attachment/5306190/+files/_lib_systemd_systemd.0.crash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1852903 Title: systemd Caught , dumped core Status in systemd package in Ubuntu: New Bug description: Several days ago an ubuntu 18.04 in ec2 env updated systemd and udev to 237-3ubuntu10.31 This caused systemd to segfault and stop receiving any systemctl command (they timeout). [ 198.482652] systemd[1]: segfault at 50 ip 5630ddd60200 sp 7ffc9c3ea890 error 4 in systemd (deleted)[5630ddcc1000+14e000] [ 278.664729] systemd-journald[451]: Failed to send WATCHDOG=1 notification message: Connection refused [ 368.462136] systemd-journald[451]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected [ 458.496689] systemd-journald[451]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected I downgraded to 237-3ubuntu10.29 to no avail. Then I downgraded to 237-3ubuntu10: apt install udev=237-3ubuntu10 systemd=237-3ubuntu10 systemd-sysv=237-3ubuntu10 libsystemd0:amd64=237-3ubuntu10 libudev1:amd64=237-3ubuntu10 libnss-systemd:amd64=237-3ubuntu10 and that did not help either. The machine is unusable at the moment. Attaching coredump of systemd (version 237-3ubuntu10.31) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1852903/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1852903] Re: systemd Caught , dumped core
This started happening after automatic upgrade: 2019-11-14 06:57:49 startup packages remove 2019-11-14 06:57:49 status installed linux-image-4.15.0-1051-aws:amd64 4.15.0-1051.53 2019-11-14 06:57:50 remove linux-image-4.15.0-1051-aws:amd64 4.15.0-1051.53 2019-11-14 06:57:50 status half-configured linux-image-4.15.0-1051-aws:amd64 4.15.0-1051.53 2019-11-14 06:57:50 status half-installed linux-image-4.15.0-1051-aws:amd64 4.15.0-1051.53 2019-11-14 06:57:52 status config-files linux-image-4.15.0-1051-aws:amd64 4.15.0-1051.53 2019-11-14 06:57:52 status config-files linux-image-4.15.0-1051-aws:amd64 4.15.0-1051.53 2019-11-14 06:57:52 status installed linux-modules-4.15.0-1051-aws:amd64 4.15.0-1051.53 2019-11-14 06:57:52 remove linux-modules-4.15.0-1051-aws:amd64 4.15.0-1051.53 2019-11-14 06:57:52 status half-configured linux-modules-4.15.0-1051-aws:amd64 4.15.0-1051.53 2019-11-14 06:57:52 status half-installed linux-modules-4.15.0-1051-aws:amd64 4.15.0-1051.53 2019-11-14 06:57:52 status config-files linux-modules-4.15.0-1051-aws:amd64 4.15.0-1051.53 2019-11-14 06:57:52 status config-files linux-modules-4.15.0-1051-aws:amd64 4.15.0-1051.53 2019-11-14 06:57:52 startup packages configure 2019-11-14 06:57:54 startup packages remove 2019-11-14 06:57:54 status installed linux-headers-4.15.0-1051-aws:amd64 4.15.0-1051.53 2019-11-14 06:57:54 remove linux-headers-4.15.0-1051-aws:amd64 4.15.0-1051.53 2019-11-14 06:57:54 status half-configured linux-headers-4.15.0-1051-aws:amd64 4.15.0-1051.53 2019-11-14 06:57:54 status half-installed linux-headers-4.15.0-1051-aws:amd64 4.15.0-1051.53 2019-11-14 06:57:56 status config-files linux-headers-4.15.0-1051-aws:amd64 4.15.0-1051.53 2019-11-14 06:57:56 status config-files linux-headers-4.15.0-1051-aws:amd64 4.15.0-1051.53 2019-11-14 06:57:56 status config-files linux-headers-4.15.0-1051-aws:amd64 4.15.0-1051.53 2019-11-14 06:57:56 status not-installed linux-headers-4.15.0-1051-aws:amd64 2019-11-14 06:57:56 startup packages configure 2019-11-14 06:57:59 startup archives unpack 2019-11-14 06:57:59 upgrade linux-libc-dev:amd64 4.15.0-69.78 4.15.0-70.79 2019-11-14 06:57:59 status half-configured linux-libc-dev:amd64 4.15.0-69.78 2019-11-14 06:57:59 status unpacked linux-libc-dev:amd64 4.15.0-69.78 2019-11-14 06:57:59 status half-installed linux-libc-dev:amd64 4.15.0-69.78 2019-11-14 06:57:59 status half-installed linux-libc-dev:amd64 4.15.0-69.78 2019-11-14 06:57:59 status unpacked linux-libc-dev:amd64 4.15.0-70.79 2019-11-14 06:57:59 status unpacked linux-libc-dev:amd64 4.15.0-70.79 2019-11-14 06:57:59 startup packages configure 2019-11-14 06:57:59 configure linux-libc-dev:amd64 4.15.0-70.79 2019-11-14 06:57:59 status unpacked linux-libc-dev:amd64 4.15.0-70.79 2019-11-14 06:57:59 status half-configured linux-libc-dev:amd64 4.15.0-70.79 2019-11-14 06:57:59 status installed linux-libc-dev:amd64 4.15.0-70.79 2019-11-14 06:58:01 startup archives unpack 2019-11-14 06:58:02 upgrade qemu-guest-agent:amd64 1:2.11+dfsg-1ubuntu7.15 1:2.11+dfsg-1ubuntu7.20 2019-11-14 06:58:02 status half-configured qemu-guest-agent:amd64 1:2.11+dfsg-1ubuntu7.15 2019-11-14 06:58:02 status unpacked qemu-guest-agent:amd64 1:2.11+dfsg-1ubuntu7.15 2019-11-14 06:58:02 status half-installed qemu-guest-agent:amd64 1:2.11+dfsg-1ubuntu7.15 2019-11-14 06:58:02 status triggers-pending systemd:amd64 237-3ubuntu10.29 2019-11-14 06:58:02 status triggers-pending ureadahead:amd64 0.100.0-21 2019-11-14 06:58:02 status triggers-pending man-db:amd64 2.8.3-2ubuntu0.1 2019-11-14 06:58:02 status half-installed qemu-guest-agent:amd64 1:2.11+dfsg-1ubuntu7.15 2019-11-14 06:58:28 status unpacked qemu-guest-agent:amd64 1:2.11+dfsg-1ubuntu7.20 2019-11-14 06:58:28 status unpacked qemu-guest-agent:amd64 1:2.11+dfsg-1ubuntu7.20 2019-11-14 06:58:28 startup packages configure 2019-11-14 06:58:28 trigproc ureadahead:amd64 0.100.0-21 2019-11-14 06:58:28 status half-configured ureadahead:amd64 0.100.0-21 2019-11-14 06:58:28 status installed ureadahead:amd64 0.100.0-21 2019-11-14 06:58:28 configure qemu-guest-agent:amd64 1:2.11+dfsg-1ubuntu7.20 2019-11-14 06:58:28 status unpacked qemu-guest-agent:amd64 1:2.11+dfsg-1ubuntu7.20 2019-11-14 06:58:28 status unpacked qemu-guest-agent:amd64 1:2.11+dfsg-1ubuntu7.20 2019-11-14 06:58:28 status unpacked qemu-guest-agent:amd64 1:2.11+dfsg-1ubuntu7.20 2019-11-14 06:58:28 status half-configured qemu-guest-agent:amd64 1:2.11+dfsg-1ubuntu7.20 2019-11-14 07:00:58 trigproc systemd:amd64 237-3ubuntu10.29 2019-11-14 07:00:58 status half-configured systemd:amd64 237-3ubuntu10.29 2019-11-14 07:01:23 status installed systemd:amd64 237-3ubuntu10.29 2019-11-14 07:01:23 trigproc man-db:amd64 2.8.3-2ubuntu0.1 2019-11-14 07:01:23 status half-configured man-db:amd64 2.8.3-2ubuntu0.1 2019-11-14 07:01:24 status installed man-db:amd64 2.8.3-2ubuntu0.1 I tried to identify the culprit package downgrading the packages, to no avail.. -- You received this bug notification because you are a
[Touch-packages] [Bug 1852903] Re: systemd Caught , dumped core
** Attachment added: "systemd 237-3ubuntu10.31 coredump (amd64)" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1852903/+attachment/5306050/+files/core.systemd.2982.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1852903 Title: systemd Caught , dumped core Status in systemd package in Ubuntu: New Bug description: Several days ago an ubuntu 18.04 in ec2 env updated systemd and udev to 237-3ubuntu10.31 This caused systemd to segfault and stop receiving any systemctl command (they timeout). [ 198.482652] systemd[1]: segfault at 50 ip 5630ddd60200 sp 7ffc9c3ea890 error 4 in systemd (deleted)[5630ddcc1000+14e000] [ 278.664729] systemd-journald[451]: Failed to send WATCHDOG=1 notification message: Connection refused [ 368.462136] systemd-journald[451]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected [ 458.496689] systemd-journald[451]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected I downgraded to 237-3ubuntu10.29 to no avail. Then I downgraded to 237-3ubuntu10: apt install udev=237-3ubuntu10 systemd=237-3ubuntu10 systemd-sysv=237-3ubuntu10 libsystemd0:amd64=237-3ubuntu10 libudev1:amd64=237-3ubuntu10 libnss-systemd:amd64=237-3ubuntu10 and that did not help either. The machine is unusable at the moment. Attaching coredump of systemd (version 237-3ubuntu10.31) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1852903/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1852903] [NEW] systemd Caught , dumped core
Public bug reported: Several days ago an ubuntu 18.04 in ec2 env updated systemd and udev to 237-3ubuntu10.31 This caused systemd to segfault and stop receiving any systemctl command (they timeout). [ 198.482652] systemd[1]: segfault at 50 ip 5630ddd60200 sp 7ffc9c3ea890 error 4 in systemd (deleted)[5630ddcc1000+14e000] [ 278.664729] systemd-journald[451]: Failed to send WATCHDOG=1 notification message: Connection refused [ 368.462136] systemd-journald[451]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected [ 458.496689] systemd-journald[451]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected I downgraded to 237-3ubuntu10.29 to no avail. Then I downgraded to 237-3ubuntu10: apt install udev=237-3ubuntu10 systemd=237-3ubuntu10 systemd-sysv=237-3ubuntu10 libsystemd0:amd64=237-3ubuntu10 libudev1:amd64=237-3ubuntu10 libnss-systemd:amd64=237-3ubuntu10 and that did not help either. The machine is unusable at the moment. Attaching coredump of systemd (version 237-3ubuntu10.31) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1852903 Title: systemd Caught , dumped core Status in systemd package in Ubuntu: New Bug description: Several days ago an ubuntu 18.04 in ec2 env updated systemd and udev to 237-3ubuntu10.31 This caused systemd to segfault and stop receiving any systemctl command (they timeout). [ 198.482652] systemd[1]: segfault at 50 ip 5630ddd60200 sp 7ffc9c3ea890 error 4 in systemd (deleted)[5630ddcc1000+14e000] [ 278.664729] systemd-journald[451]: Failed to send WATCHDOG=1 notification message: Connection refused [ 368.462136] systemd-journald[451]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected [ 458.496689] systemd-journald[451]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected I downgraded to 237-3ubuntu10.29 to no avail. Then I downgraded to 237-3ubuntu10: apt install udev=237-3ubuntu10 systemd=237-3ubuntu10 systemd-sysv=237-3ubuntu10 libsystemd0:amd64=237-3ubuntu10 libudev1:amd64=237-3ubuntu10 libnss-systemd:amd64=237-3ubuntu10 and that did not help either. The machine is unusable at the moment. Attaching coredump of systemd (version 237-3ubuntu10.31) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1852903/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
