Bug#929655: Obscure "Failed to set invocation ID for unit: File exists" error

[Kathryn Tolsen]

Package: systemd
Version: 241-3
Severity: Serious

All systemd services are failing to start, best guess is, this is related
to:

https://github.com/systemd/systemd/issues/11810

https://github.com/poettering/systemd/commit/1c53d4a070edbec8ad2d384ba0014d0eb6bae077#diff-445fb9f3aa0c047d97ba6544e8a4575dR69

all logs on this issue are available here: http://kbt.ddns.net/

I will be leaving this site up until the issue is resolved. I am unable to
start any services and get errors spewed from systemd on any and all apt
operations, my mosh logins are especially laggy, and I'm afraid to even try
rebooting to possibly straighten this out, as if it can't start services it
may not even boot.

If this issue is the above related upstream issue, it effects a large
subset of users with AMD cpus, and renders systemd unusable, so I have
marked this as serious. This should be considered a release-critical bug.

The error message is not only vague but is misleading, as if I am right
about the source of this problem, it has nothing to do with some mysterious
"file" existing.

Other ideas tossed around were some kind of OOM condition, I have less than
250MB of 4GB ram in use, and over 3GB free on the rootfs which is on the
8GB m.2 SSD, so thats definitely not the issue here.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20190527/206038b6/attachment.html>