Should I be aware of these journalctl log error messages?

General system Newbie
1

I was reading some other posts and I’ve decided to check my journalctl log to see how my system is working and I’ve noticed these errors and warnings:

mar 25 09:28:18 eos pipewire[887]: mod.rt: RTKit error: org.freedesktop.DBus.Error.ServiceUnknown
mar 25 09:28:18 eos pipewire-pulse[889]: mod.rt: RTKit error: org.freedesktop.DBus.Error.ServiceUnknown
mar 25 09:28:18 eos pipewire-media-session[888]: mod.rt: RTKit error: org.freedesktop.DBus.Error.ServiceUnknown
mar 25 09:28:18 eos pipewire-pulse[889]: mod.rt: RTKit error: org.freedesktop.DBus.Error.ServiceUnknown
mar 25 09:28:18 eos pipewire[887]: mod.rt: RTKit error: org.freedesktop.DBus.Error.ServiceUnknown
mar 25 09:28:18 eos pipewire-media-session[888]: mod.rt: RTKit error: org.freedesktop.DBus.Error.ServiceUnknown
mar 25 09:28:18 eos pipewire-media-session[888]: mod.rt: RTKit error: org.freedesktop.DBus.Error.ServiceUnknown
mar 25 09:28:18 eos pipewire[887]: mod.rt: RTKit error: org.freedesktop.DBus.Error.ServiceUnknown
mar 25 09:28:18 eos pipewire[887]: mod.rt: RTKit error: org.freedesktop.DBus.Error.ServiceUnknown
mar 25 09:28:19 eos pipewire-pulse[889]: mod.rt: RTKit error: org.freedesktop.DBus.Error.ServiceUnknown
mar 25 09:28:19 eos pipewire-pulse[889]: mod.rt: RTKit error: org.freedesktop.DBus.Error.ServiceUnknown
mar 25 09:40:10 eos qmmp[2392]: QmmpPluginCache: error: No se puede cargar la biblioteca /usr/lib/qmmp-2.0/Input/libopus.so: (libopusfile.so.0: no se puede abrir el fichero del objeto compartido: No existe el fichero o el directorio)
mar 25 09:40:10 eos qmmp[2392]: QmmpPluginCache: error: No se puede cargar la biblioteca /usr/lib/qmmp-2.0/Input/libsid.so: (libsidplayfp.so.6: no se puede abrir el fichero del objeto compartido: No existe el fichero o el directorio)
                                            Module libgpg-error.so.0 with build-id 82524ee3d1c4c2244d7cfdcc1e6eea5f9855f6c6
...
mar 25 10:28:21 eos evolution-sourc[1156]: secret_monitor_scan_secrets_thread: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.secrets was not provided by any .service files
...
mar 25 09:28:22 eos cinnamon-session[770]: WARNING: t+4.31559s: Detected that screensaver has appeared on the bus
mar 25 09:28:52 eos cinnamon-session[770]: WARNING: t+34.32338s: Detected that screensaver has left the bus
...
mar 25 09:28:10 eos systemd[1]: File System Check on Root Device was skipped because of a failed condition check (ConditionPathIsReadWrite=!/).
mar 25 09:28:10 eos systemd[1]: Repartition Root Disk was skipped because all trigger condition checks failed.
mar 25 09:28:10 eos systemd[1]: First Boot Wizard was skipped because of a failed condition check (ConditionFirstBoot=yes).
mar 25 09:28:10 eos systemd[1]: Rebuild Hardware Database was skipped because of a failed condition check (ConditionNeedsUpdate=/etc).
mar 25 09:28:10 eos systemd[1]: Create System Users was skipped because of a failed condition check (ConditionNeedsUpdate=/etc).
mar 25 09:28:10 eos kernel: vboxdrv: module verification failed: signature and/or required key missing - tainting kernel
mar 25 09:28:10 eos systemd[1]: Virtual Machine and Container Storage (Compatibility) was skipped because of a failed condition check (ConditionPathExists=/var/lib/machines.raw).
mar 25 09:28:11 eos systemd[1]: First Boot Complete was skipped because of a failed condition check (ConditionFirstBoot=yes).
mar 25 09:28:11 eos systemd-udevd[267]: cfg80211: Process '/usr/bin/set-wireless-regdom' failed with exit code 1.
mar 25 09:28:11 eos systemd[1]: First Boot Wizard was skipped because of a failed condition check (ConditionFirstBoot=yes).
mar 25 09:28:11 eos systemd[1]: First Boot Complete was skipped because of a failed condition check (ConditionFirstBoot=yes).
mar 25 09:28:11 eos systemd[1]: File System Check on Root Device was skipped because of a failed condition check (ConditionPathIsReadWrite=!/).
mar 25 09:28:11 eos systemd[1]: Rebuild Hardware Database was skipped because of a failed condition check (ConditionNeedsUpdate=/etc).
mar 25 09:28:11 eos systemd[1]: Repartition Root Disk was skipped because all trigger condition checks failed.
mar 25 09:28:11 eos systemd[1]: Create System Users was skipped because of a failed condition check (ConditionNeedsUpdate=/etc).
mar 25 09:28:12 eos systemd[1]: First Boot Wizard was skipped because of a failed condition check (ConditionFirstBoot=yes).
mar 25 09:28:12 eos systemd[1]: First Boot Complete was skipped because of a failed condition check (ConditionFirstBoot=yes).
mar 25 09:28:12 eos systemd[1]: File System Check on Root Device was skipped because of a failed condition check (ConditionPathIsReadWrite=!/).
mar 25 09:28:12 eos systemd[1]: Rebuild Hardware Database was skipped because of a failed condition check (ConditionNeedsUpdate=/etc).
mar 25 09:28:12 eos systemd[1]: Repartition Root Disk was skipped because all trigger condition checks failed.
mar 25 09:28:12 eos systemd[1]: Create System Users was skipped because of a failed condition check (ConditionNeedsUpdate=/etc).
mar 25 09:28:15 eos systemd[1]: Rebuild Dynamic Linker Cache was skipped because all trigger condition checks failed.
mar 25 09:28:15 eos systemd[1]: Set Up Additional Binary Formats was skipped because all trigger condition checks failed.
mar 25 09:28:15 eos 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).
mar 25 09:28:15 eos systemd[1]: Commit a transient machine-id on disk was skipped because of a failed condition check (ConditionPathIsMountPoint=/etc/machine-id).
mar 25 09:28:15 eos systemd[1]: Rebuild Journal Catalog was skipped because of a failed condition check (ConditionNeedsUpdate=/var).
mar 25 09:28:15 eos systemd[1]: Update is Completed was skipped because all trigger condition checks failed.
mar 25 09:28:15 eos systemd[1]: Manage Sound Card State (restore and store) was skipped because of a failed condition check (ConditionPathExists=/etc/alsa/state-daemon.conf).
mar 25 09:28:15 eos audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=shadow comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
mar 25 09:28:16 eos wpa_supplicant[717]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface.P2PDevice dbus_property=P2PDeviceConfig getter failed
mar 25 09:28:17 eos dbus-daemon[522]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
mar 25 09:28:17 eos dbus-daemon[522]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
mar 25 09:28:17 eos audit[748]: CRED_ACQ pid=748 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=? acct="triby" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
mar 25 09:28:17 eos kernel: audit: type=1103 audit(1648222097.508:61): pid=748 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=? acct="triby" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
mar 25 09:28:18 eos dbus-daemon[522]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found.
mar 25 09:28:19 eos dbus-daemon[522]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found.
mar 25 09:28:19 eos dbus-daemon[522]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found.
mar 25 09:31:11 eos dbus-daemon[522]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
mar 25 09:39:20 eos dbus-daemon[522]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
mar 25 09:40:44 eos dbus-daemon[522]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service not found.

I’ve used grep to extract these messages. So, should I be aware of all of these messages and, if so, how can I fix them?

Thanks in advance.

Links for more info:

2

You can check error in logs by → 

journalctl -p 3 -xb

This will generate the lists of logs which had identified errors.

To know critical logs use → 

journalctl -p 2 -xb

I only know about these two to check errors in logs; except these, rest are logs of the current sessions.
Experienced users please correct me if I am going wrong.

3 Likes
3

Thank you, very much. Knowing that those are not critical errors, I can live with them.

1 Like
4

In future, if you face critical error in logs, then change of Kernel version solves the issue. If you are facing issue from 5.16, then switching to either LTS or testing version can solve the issue.

1 Like
5

There are few more things to know;
➤ journalctl -p 1 -xb

This lists issues which are needed to be solved immediately.

➤ journalctl -p 0 -xb

This lists unusable entries.

2 Likes
6

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