systemd: nach Update auf systemd-250.4 Fehlermeldungen im Log

Oceanwaves · 2. April 2022

Hallo!

Nach dem Update auf systemd-2.50-4 habe ich bei jedem Boot die folgenden Meldungen im Systemd-Log. Sollte ich mir da Gedanken machen oder kann ich die einfach ignorieren?

Code

~ # journalctl | grep "failed condition check"
Apr 02 07:53:37 frodo systemd[1]: Dispatch Password Requests to Console Directory Watch was skipped because of a failed condition check (ConditionPathExists=!/run/plymouth/pid).
Apr 02 07:53:37 frodo systemd[1]: OSTree Prepare OS/ was skipped because of a failed condition check (ConditionKernelCommandLine=ostree).
Apr 02 07:53:38 frodo systemd[1]: Tell haveged about new root was skipped because of a failed condition check (ConditionKernelVersion=<5.6).
Apr 02 07:53:38 frodo systemd[1]: OSTree Prepare OS/ was skipped because of a failed condition check (ConditionKernelCommandLine=ostree).
Apr 02 07:53:38 frodo systemd[1]: Apply Kernel Variables for 5.16.15-1-default from /boot was skipped because of a failed condition check (ConditionPathExists=!/usr/lib/modules/5.16.15-1-default/sysctl.conf).
Apr 02 07:53:38 frodo systemd[1]: One time configuration for iscsid.service was skipped because of a failed condition check (ConditionPathExists=!/etc/iscsi/initiatorname.iscsi).
Apr 02 07:53:38 frodo systemd[1]: First Boot Wizard was skipped because of a failed condition check (ConditionFirstBoot=yes).
Apr 02 07:53:38 frodo systemd[1]: Rebuild Hardware Database was skipped because of a failed condition check (ConditionNeedsUpdate=/etc).
Apr 02 07:53:38 frodo systemd[1]: Create System Users was skipped because of a failed condition check (ConditionNeedsUpdate=/etc).
Apr 02 07:53:38 frodo systemd[1]: Virtual Machine and Container Storage (Compatibility) was skipped because of a failed condition check (ConditionPathExists=/var/lib/machines.raw).
Apr 02 07:53:38 frodo systemd[1]: Lock Directory was skipped because of a failed condition check (ConditionPathIsSymbolicLink=!/var/lock).
Apr 02 07:53:38 frodo systemd[1]: Runtime Directory was skipped because of a failed condition check (ConditionPathIsSymbolicLink=!/var/run).
Apr 02 07:53:38 frodo systemd[1]: First Boot Complete was skipped because of a failed condition check (ConditionFirstBoot=yes).
Apr 02 07:53:38 frodo systemd[1]: Store a System Token in an EFI Variable was skipped because of a failed condition check (ConditionPathExists=/sys/firmware/efi/efivars/LoaderFeatures-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f).
Apr 02 07:53:38 frodo systemd[1]: Commit a transient machine-id on disk was skipped because of a failed condition check (ConditionPathIsMountPoint=/etc/machine-id).
Apr 02 07:53:38 frodo systemd[1]: Rebuild Journal Catalog was skipped because of a failed condition check (ConditionNeedsUpdate=/var).
Apr 02 07:53:39 frodo systemd[1]: Store a System Token in an EFI Variable was skipped because of a failed condition check (ConditionPathExists=/sys/firmware/efi/efivars/LoaderFeatures-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f).
Apr 02 07:53:39 frodo systemd[1]: First Boot Wizard was skipped because of a failed condition check (ConditionFirstBoot=yes).
Apr 02 07:53:39 frodo systemd[1]: First Boot Complete was skipped because of a failed condition check (ConditionFirstBoot=yes).
Apr 02 07:53:39 frodo systemd[1]: Rebuild Hardware Database was skipped because of a failed condition check (ConditionNeedsUpdate=/etc).
Apr 02 07:53:39 frodo systemd[1]: Rebuild Journal Catalog was skipped because of a failed condition check (ConditionNeedsUpdate=/var).
Apr 02 07:53:39 frodo systemd[1]: Commit a transient machine-id on disk was skipped because of a failed condition check (ConditionPathIsMountPoint=/etc/machine-id).
Apr 02 07:53:39 frodo systemd[1]: Create System Users was skipped because of a failed condition check (ConditionNeedsUpdate=/etc).
Apr 02 07:53:39 frodo systemd[1]: Store a System Token in an EFI Variable was skipped because of a failed condition check (ConditionPathExists=/sys/firmware/efi/efivars/LoaderFeatures-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f).
Apr 02 07:53:39 frodo systemd[1]: First Boot Wizard was skipped because of a failed condition check (ConditionFirstBoot=yes).
Apr 02 07:53:39 frodo systemd[1]: First Boot Complete was skipped because of a failed condition check (ConditionFirstBoot=yes).
Apr 02 07:53:39 frodo systemd[1]: Rebuild Hardware Database was skipped because of a failed condition check (ConditionNeedsUpdate=/etc).
Apr 02 07:53:39 frodo systemd[1]: Rebuild Journal Catalog was skipped because of a failed condition check (ConditionNeedsUpdate=/var).
Apr 02 07:53:39 frodo systemd[1]: Commit a transient machine-id on disk was skipped because of a failed condition check (ConditionPathIsMountPoint=/etc/machine-id).
Apr 02 07:53:39 frodo systemd[1]: Create System Users was skipped because of a failed condition check (ConditionNeedsUpdate=/etc).
Apr 02 07:53:39 frodo systemd[1]: Store a System Token in an EFI Variable was skipped because of a failed condition check (ConditionPathExists=/sys/firmware/efi/efivars/LoaderFeatures-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f).
Apr 02 07:53:39 frodo systemd[1]: First Boot Wizard was skipped because of a failed condition check (ConditionFirstBoot=yes).
Apr 02 07:53:39 frodo systemd[1]: First Boot Complete was skipped because of a failed condition check (ConditionFirstBoot=yes).
Apr 02 07:53:39 frodo systemd[1]: Rebuild Hardware Database was skipped because of a failed condition check (ConditionNeedsUpdate=/etc).
Apr 02 07:53:39 frodo systemd[1]: Rebuild Journal Catalog was skipped because of a failed condition check (ConditionNeedsUpdate=/var).
Apr 02 07:53:39 frodo systemd[1]: Commit a transient machine-id on disk was skipped because of a failed condition check (ConditionPathIsMountPoint=/etc/machine-id).
Apr 02 07:53:39 frodo systemd[1]: Create System Users was skipped because of a failed condition check (ConditionNeedsUpdate=/etc).
Apr 02 07:53:40 frodo systemd[1]: Manage Sound Card State (restore and store) was skipped because of a failed condition check (ConditionPathExists=/etc/alsa/state-daemon.conf).
Apr 02 07:53:40 frodo systemd[1]: Synchronize AppStream metadata from repositories into AS-cache was skipped because of a failed condition check (ConditionDirectoryNotEmpty=!/var/cache/app-info/xmls).
Apr 02 07:53:40 frodo systemd[1]: Auto-connect to subsystems on FC-NVME devices found during boot was skipped because of a failed condition check (ConditionPathExists=/sys/class/fc/fc_udev_device/nvme_discovery).
Apr 02 07:53:40 frodo systemd[1]: Purge old kernels was skipped because of a failed condition check (ConditionPathExists=/boot/do_purge_kernels).

Alles anzeigen

Sauerland · 2. April 2022

Evtl.:

Bug 1197967 – dracut creates initrd where group ownership is lost

oder:

Bug 1197968 – systemd 250 seems to change handling of unreadable networkd

Ansonsten:

Bugreport

Oceanwaves · 2. April 2022

Denke nicht, dass es mit dem Bug etwas zu tun hat. Vermute inzwischen, dass es weniger Fehler- als vielmehr Info-Meldungen sind. Hatte nach dem Post ein dup laufen lassen und dabei ein Kernel-Update (5.17.1) installiert. Nach dem Neustart tauchte die Zeile

Code

systemd[1]: Purge old kernels was skipped because of a failed condition check (ConditionPathExists=/boot/do_purge_kernels).

nicht in journalctl auf. Stattdessen gab es tatsächlich vor dem Neustart eine Datei /boot/do_purge_kernels, die nach dem Neustart dann weg war.

Ich vermute, dass systemd beim Start bestimmte Bedingungen überprüft und ab v2.50 eine entsprechende Meldung schreibt, wenn die Bedingung nicht erfüllt ist. Dann werde ich einfach in /etc/logwatch/conf/ignore.conf ein entspr. Pattern einfügen, damit mir die Meldungen nicht ständig angezeigt werden.

Sauerland · 3. April 2022

Zitat

stattdessen gab es tatsächlich vor dem Neustart eine Datei /boot/do_purge_kernels, die nach dem Neustart dann weg war.

Info:

Wenn ein neuer Kernel installiert wird, wird in /boot eine Datei mit Namen do_purge_kernels erstellt.

Bei jedem Start wird immer der Service purge-kernels.service ausgeführt, welcher ein Script aufruft, das in /boot nach der Datei do_purge_kernels schaut, wenn vorhanden wird lt. /etc/zypp/zypp.conf die überflüssigen Kernels sowie natürlich die Datei do_purge_kernels gelöscht, wenn die Datei nicht vorhanden ist, wird das Script abgebrochen.

Code

grep -iA3 'multiversion' /etc/zypp/zypp.conf

## Comma separated list of kernel packages to keep installed in parallel, if the
## above multiversion variable is set. Packages can be specified as
## 2.6.32.12-0.7 - Exact version to keep
## latest        - Keep kernel with the highest version number
## latest-N      - Keep kernel with the Nth highest version number
--
## Default: Do not delete any kernels if multiversion = provides:multiversion(kernel) is set
multiversion.kernels = latest,latest-1,latest-2,running

Oceanwaves · 3. April 2022

Genau. Und wenn der Service purge-kernels.service die Datei in /boot nicht findet, gibt Systemd ab v2.50 eine entsprechende Meldung aus (skipped because of a failed condition check). Bis 2.49 hat Systemd dann wohl nichts getan, aber auch nicht gemeldet, warum nichts getan wurde. Und ab 2.50 ist Systemd da etwas gesprächiger.

Oceanwaves · 3. April 2022

Und da ich es eben vergessen habe noch ein Eintrag, um das Thema auf erledigt zu setzen.

systemd: nach Update auf systemd-250.4 Fehlermeldungen im Log

Probleme mit dem Ausdruck von pdf-Dateien über Okular

Eclipse (Java IDE) crash

Veracrypt Einhängepunkt

Neuinstallation leap 15.5: init Prozess scheitert beim Booten - Kernel Panik

latex & kpathsea in Betrieb nehmen

Kukulkan

vpn

Nidrnox

hudel

uli11

Teilen

Tags