[Bug 2063349] Re: systemd-coredump handler does not forward the crash to the container
This bug was fixed in the package apport - 2.29.0-0ubuntu1 --- apport (2.29.0-0ubuntu1) oracular; urgency=medium [ Benjamin Drung ] * New upstream release: - Ignore container crash reports from systemd-coredump (LP: #2063349) - apport: do not modify permission of existing /var/crash or create /var/crash with setgid permission (mode 3777) (LP: #2066995) - Fix retracing crashes on Ubuntu 24.04 (noble) (LP: #2067120) * ubuntu: fix possibly using dpkg_log_without_error before assignment * Drop python3-requests dependency * autopkgtest: add chaos-marmosets for system-tests * apport.postinst: Create /var/crash with mode 3777 (LP: #2066995) * Build-depend on mypy and python3-typeshed for type checking * Build-depend on systemd-dev to determine systemd/udev paths [ Chris Peterson ] * d/package-hooks/subiquity.py: update information collection (LP: #2067775) - Add information about snap update/refresh state - Attach logs and change key names to align with the information attached by subiquity's self-collection - Attach hardware information - Ensure bug reports are always private since there may be private information in the logs - Don't require sudo for logs collection - Add journal logs - Ensure snap revision is included in both deb and snap collection style -- Benjamin Drung Fri, 14 Jun 2024 10:18:31 +0200 ** Changed in: apport (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063349 Title: systemd-coredump handler does not forward the crash to the container To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2063349/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063349] Re: systemd-coredump handler does not forward the crash to the container
** Changed in: apport Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063349 Title: systemd-coredump handler does not forward the crash to the container To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2063349/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063349] Re: systemd-coredump handler does not forward the crash to the container
I requested to standardize forwarding crashes to containers: https://github.com/uapi-group/specifications/issues/102 ** Bug watch added: github.com/uapi-group/specifications/issues #102 https://github.com/uapi-group/specifications/issues/102 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063349 Title: systemd-coredump handler does not forward the crash to the container To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2063349/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063349] Re: systemd-coredump handler does not forward the crash to the container
** Changed in: apport Importance: Undecided => Medium ** Changed in: apport Status: New => In Progress ** Changed in: apport (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063349 Title: systemd-coredump handler does not forward the crash to the container To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2063349/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063349] Re: systemd-coredump handler does not forward the crash to the container
Apport cannot do anything useful with these crash reports, because the information about the crashed process does not contain the process number seen from inside the container and because the crashed process is already gone when Apport gets the crash from systemd-coredump. So let Apport just ignore crash reports from systemd-coredump if the crashes happened inside containers: https://github.com/canonical/apport/pull/326 ** Also affects: apport Importance: Undecided Status: New ** Changed in: apport Milestone: None => 2.29.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063349 Title: systemd-coredump handler does not forward the crash to the container To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2063349/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063349] Re: systemd-coredump handler does not forward the crash to the container
Okay. The title should be changed then -- systemd-coredump on the host attempts to forward the crash to the container, but finds that systemd- coredump is not present in the container, so it falls back to keeping it on the host. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063349 Title: systemd-coredump handler does not forward the crash to the container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2063349/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063349] Re: systemd-coredump handler does not forward the crash to the container
>Did you verify that systemd-coredump is installed in the container? It works when systemd-coredump is installed inside the container. This report is for the default noble container. My understanding is that in no case should the .crash file be on the host when a crash occurs inside a container. I guess apport should forward the crash to the container 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/2063349 Title: systemd-coredump handler does not forward the crash to the container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2063349/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063349] Re: systemd-coredump handler does not forward the crash to the container
Nick, it works if you have systemd-coredump installed in the container. If you do not have systemd-coredump installed in the container, apport on the host should do the forwarding. ** Changed in: apport (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063349 Title: systemd-coredump handler does not forward the crash to the container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2063349/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063349] Re: systemd-coredump handler does not forward the crash to the container
root@selected-slug:~# machinectl pull-raw "http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img"; noble Enqueued transfer job 1. Press C-c to continue download in background. Pulling 'http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img', saving as 'noble'. Downloading 453.0M for http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. HTTP request to http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.roothash.p7s failed with code 404. Root hash signature file could not be retrieved, proceeding without. HTTP request to http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.verity failed with code 404. Verity integrity file could not be retrieved, proceeding without. HTTP request to http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.nspawn failed with code 404. Settings file could not be retrieved, proceeding without. Downloading 833B for http://cloud-images.ubuntu.com/noble/current/SHA256SUMS.gpg. Acquired 833B. Download of http://cloud-images.ubuntu.com/noble/current/SHA256SUMS.gpg complete. HTTP request to http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.roothash failed with code 404. Root hash file could not be retrieved, proceeding without. Downloading 6.9K for http://cloud-images.ubuntu.com/noble/current/SHA256SUMS. Got 37% of http://cloud-images.ubuntu.com/noble/current/SHA256SUMS. Acquired 6.9K. Download of http://cloud-images.ubuntu.com/noble/current/SHA256SUMS complete. Got 1% of http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 2min 13s left at 3.3M/s. Got 5% of http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 41s left at 10.4M/s. Got 11% of http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 26s left at 14.9M/s. Got 16% of http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 21s left at 17.5M/s. Got 22% of http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 18s left at 19.0M/s. Got 28% of http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 16s left at 20.1M/s. Got 33% of http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 14s left at 20.6M/s. Got 39% of http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 13s left at 21.1M/s. Got 44% of http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 11s left at 21.3M/s. Got 50% of http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 10s left at 21.8M/s. Got 53% of http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 9s left at 21.3M/s. Got 58% of http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 8s left at 21.4M/s. Got 64% of http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 7s left at 21.7M/s. Got 69% of http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 6s left at 21.9M/s. Got 75% of http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 4s left at 22.2M/s. Got 81% of http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 3s left at 22.4M/s. Got 87% of http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 2s left at 22.6M/s. Got 93% of http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 1s left at 22.7M/s. Got 98% of http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 306ms left at 22.8M/s. Acquired 453.0M. Download of http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img complete. SHA256 checksum of http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img is valid. gpg: Signature made Wed Apr 24 00:22:50 2024 UTC gpg:using RSA key D2EB44626FDDC30B513D5BB71A5D6C4C7DB87C81 gpg: Good signature from "UEC Image Automatic Signing Key " [unknown] gpg: WARNING: Using untrusted key! Signature verification succeeded. Unpacking QCOW2 file. Created new local image 'noble'. Operation completed successfully. Exiting. root@selected-slug:~# machinectl start noble root@selected-slug:~# machinectl shell noble Connected to machine noble. Press ^] three times within 1s to exit session. ### In the container now ### root@ubuntu:~# apt update && apt install systemd-coredump chaos-marmosets -y Get:1 http://archive.ubuntu.com/ubuntu noble InRelease [256 kB] Get:2 http://archive.ubuntu.com/ubuntu noble-updates InRelease [89.7 kB] Get:3 http://archive.ubuntu.com/ubuntu noble-backports InRelease [90.8 kB] Hit:4 http://security.ubuntu.com/ubuntu noble-security InRelease Get:5 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages [1403 kB] Get:6 http://archive.ubuntu.com/ubuntu noble/universe amd64 Packages [15.5
[Bug 2063349] Re: systemd-coredump handler does not forward the crash to the container
Did you verify that systemd-coredump is installed in the container? ** Changed in: apport (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063349 Title: systemd-coredump handler does not forward the crash to the container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2063349/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
