[Bug 1756081] [NEW] journald is unable to attribute messages incoming from processes that exited their cgroup

ChristianEhrhardt 1756081 at bugs.launchpad.net
Thu Mar 15 13:59:21 UTC 2018


Public bug reported:

This is mostly an FYI and a tracker to link Upstream to Ubuntu.

Background:
I wondered why some of my services are missing just the most interesting "last" messages before dying.
Unfortunately I found this is a known race and there seems to be no good fix yet.

But I think this is important, so I wanted to make you aware.
Especially the last few messages before a service is dying are important.

If you see any way to fix this in Ubuntu as an interim solution until
upstream has found "the right thing" to eventually solve it that would
be great.

Upstream issue (many dups onto this): https://github.com/systemd/systemd/issues/2913
One approach that was tried (but not accepted): https://lwn.net/Articles/580150/

** Affects: systemd
     Importance: Unknown
         Status: Unknown

** Affects: systemd (Ubuntu)
     Importance: Undecided
         Status: New

** Bug watch added: github.com/systemd/systemd/issues #2913
   https://github.com/systemd/systemd/issues/2913

** Also affects: systemd via
   https://github.com/systemd/systemd/issues/2913
   Importance: Unknown
       Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1756081

Title:
  journald is unable to attribute messages incoming from processes that
  exited their cgroup

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  New

Bug description:
  This is mostly an FYI and a tracker to link Upstream to Ubuntu.

  Background:
  I wondered why some of my services are missing just the most interesting "last" messages before dying.
  Unfortunately I found this is a known race and there seems to be no good fix yet.

  But I think this is important, so I wanted to make you aware.
  Especially the last few messages before a service is dying are important.

  If you see any way to fix this in Ubuntu as an interim solution until
  upstream has found "the right thing" to eventually solve it that would
  be great.

  Upstream issue (many dups onto this): https://github.com/systemd/systemd/issues/2913
  One approach that was tried (but not accepted): https://lwn.net/Articles/580150/

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1756081/+subscriptions



More information about the foundations-bugs mailing list