Strange error messages

After a bit of effort I finally had a functioning 9.3 system. Everything seemed to be working until my first e-mail from logwatch. They mostly refer to “unmet conditions” whatever that might mean. The hardware is a Dell T550 server
--------------------- Kernel Begin ------------------------

WARNING: Trap int3 in these executables
traps: ibus-daemon : 1 Time(s)

WARNING: Kernel Errors Present
ACPI Error: Aborting method …: 8 Time(s)
ACPI Error: No handler for …: 4 Time(s)
ACPI Error: Region IPMI (ID …: 4 Time(s)

---------------------- Kernel End -------------------------

--------------------- LVM Begin ------------------------

Unmatched Entries
PV /dev/sda4 online, VG rl_unknownb44506fca1b6 is complete.: 4 Time(s)
PV /dev/sda6 online, VG rl_unknownb44506fca1b600 is complete.: 4 Time(s)

---------------------- LVM End -------------------------

--------------------- Smartd Begin ------------------------

Unmatched Entries
Device: /dev/bus/0 [megaraid_disk_00] [SAT], no ATA CHECK POWER STATUS support, ignoring -n Directive : 4 time(s)
Device: /dev/bus/0 [megaraid_disk_01] [SAT], no ATA CHECK POWER STATUS support, ignoring -n Directive : 4 time(s)

---------------------- Smartd End -------------------------

--------------------- SSHD Begin ------------------------

SSHD Started: 8 Times

---------------------- SSHD End -------------------------

--------------------- Systemd Begin ------------------------

ERROR: Failed state:
gnome-session-x11-services-ready.target: 5 Time(s)
org.gnome.SettingsDaemon.XSettings.service: 5 Time(s)

Unmatched Entries
Auto-connect to subsystems on FC-NVME devices found during boot was skipped because of an unmet condition check (ConditionPathExists=/sys/class/fc/fc_udev_device/nvme_discovery).: 4 Time(s)
Closed PipeWire PulseAudio.: 6 Time(s)
Commit a transient machine-id on disk was skipped because of an unmet condition check (ConditionPathIsMountPoint=/etc/machine-id).: 4 Time(s)
Create System Users was skipped because no trigger condition checks were met.: 4 Time(s)
Device-Mapper Multipath Device Controller was skipped because of an unmet condition check (ConditionPathExists=/etc/multipath.conf).: 4 Time(s)
Dispatch Password Requests to Console Directory Watch was skipped because of an unmet condition check (ConditionPathExists=!/run/plymouth/pid).: 8 Time(s)
First Boot Complete was skipped because of an unmet condition check (ConditionFirstBoot=yes).: 4 Time(s)
First Boot Wizard was skipped because of an unmet condition check (ConditionFirstBoot=yes).: 4 Time(s)
GNOME Initial Setup Copy Worker was skipped because of an unmet condition check (ConditionPathExists=!/root/.config/gnome-initial-setup-done).: 4 Time(s)
GNOME Initial Setup was skipped because of an unmet condition check (ConditionPathExists=!/root/.config/gnome-initial-setup-done).: 4 Time(s)
GNOME session X11 services is inactive.: 5 Time(s)
Hostname set to <diameters3.diameters.com>.: 4 Time(s)
Hostname set to .: 1 Time(s)
Load CPU microcode update was skipped because of an unmet condition check (ConditionPathExists=/sys/devices/system/cpu/microcode/reload).: 4 Time(s)
Login and scanning of iSCSI devices was skipped because of an unmet condition check (ConditionDirectoryNotEmpty=/var/lib/iscsi/nodes).: 4 Time(s)
Low Memory Monitor was skipped because of an unmet condition check (ConditionPathExists=/proc/pressure).: 4 Time(s)
Mark boot as successful after the user session has run 2 minutes was skipped because of an unmet condition check (ConditionUser=!@system).: 10 Time(s).

The un met condition notices are a normal part of the boot as systemd tests for certain conditions that trigger other actions if they are met. Usually the first test is to see if this is the very first boot after system install which of course is un met on subsequent boots. I don’t know what triggers the number of times each test is run per boot.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.