systemd spams the syslog about lack of native systemd unit file
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apport (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
fam (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
freeradius (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
ipfm (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
n2n (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
pfm (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
shadowsocks (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
sysfsutils (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
systemd (Debian) |
Fix Released
|
Unknown
|
|||
systemd (Ubuntu) |
Fix Released
|
Low
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
Unassigned | ||
Groovy |
Fix Released
|
Undecided
|
Unassigned | ||
virtualbox (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
xl2tpd (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
[impact]
systemd spams journal with log messages
[test case]
see journalctl output and search for msgs similar to those listed in original description below; specifically messages containing text with "below legacy directory /var/run/" or "lacks a native systemd unit file"
[regression potential]
any regession would likely result in logs incorrectly not logged when detecting a problem such as lack of native unit file, or using /var/run.
[scope]
this is needed in f/g
this is fixed upstream with commit https:/
these log messages aren't present in b or earlier so aren't needed in x/b
[original description]
systemd in hirsute spams the syslog file several times per second about services lacking native systemd unit files. Two things should happen.
1) a systemd unit file ought to be created
2) systemd should be slowed down with regards to these messages
Feb 17 02:02:48 ubuntu-devel kernel: [ 289.794825] systemd-
Feb 17 02:02:49 ubuntu-devel kernel: [ 290.165351] systemd-
Feb 17 02:02:49 ubuntu-devel kernel: [ 291.111278] systemd-
Feb 17 02:02:50 ubuntu-devel kernel: [ 291.507164] systemd-
Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386062] systemd-
Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386321] systemd-
Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386742] systemd-
Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386767] systemd-
Feb 17 02:05:57 ubuntu-devel kernel: [ 478.387281] systemd-
Feb 17 02:05:57 ubuntu-devel kernel: [ 478.388931] systemd-
Feb 17 02:05:57 ubuntu-devel kernel: [ 478.388955] systemd-
Feb 17 02:05:57 ubuntu-devel kernel: [ 478.389412] systemd-
description: | updated |
description: | updated |
Changed in systemd (Debian): | |
status: | Unknown → Confirmed |
Changed in systemd (Debian): | |
status: | Confirmed → Fix Released |
description: | updated |
description: | updated |
Hello Rolf and thanks for this bug report. I can't reproduce the issue you described neither on my laptop, which has been following Ubuntu "devel" for quite some cycles now, nor in a clean LXD container running Hirsute.
You brought freeradius as an example, but freeradius *does* ship with a systemd unit file:
/lib/ systemd/ system/ freeradius. service
So this looks like a local (mis)configuration issue to me. If you still think there's actually a bug here we need more information on how to reproduce it from a clean environment, otherwise it's difficult to confirm the problem or to begin working on it.
I'm marking this bug report as Incomplete for the moment.