You are not logged in.

#1 2025-08-06 14:37:50

scruffidog
Member
Registered: 2010-01-10
Posts: 28

dbus related journal spam entries

Been getting these mesgs in journalctl, don't believe any of them to be critical.

Aug 05 08:07:40 locutus dbus-broker-launch[692]: Caught SIGHUP, trigger reload.
    Aug 05 08:07:40 locutus systemd[1]: Reloading D-Bus System Message Bus…
    Aug 05 08:07:40 locutus dbus-broker-launch[692]: Looking up NSS user entry for ‘gdm’…
    Aug 05 08:07:40 locutus dbus-broker-launch[692]: NSS returned no entry for ‘gdm’
    Aug 05 08:07:40 locutus dbus-broker-launch[692]: Looking up NSS user entry for ‘sddm’…
    Aug 05 08:07:40 locutus dbus-broker-launch[692]: NSS returned no entry for ‘sddm’
    Aug 05 08:07:40 locutus dbus-broker-launch[692]: Looking up NSS user entry for ‘lightdm’…
    Aug 05 08:07:40 locutus dbus-broker-launch[692]: NSS returned no entry for ‘lightdm’
    Aug 05 08:07:40 locutus dbus-broker-launch[692]: Looking up NSS user entry for ‘lxdm’…
    Aug 05 08:07:40 locutus dbus-broker-launch[692]: NSS returned no entry for ‘lxdm’
    Aug 05 08:07:40 locutus dbus-broker-launch[692]: Deprecated policy context in /usr/share/dbus-1/system.d/connman-nmcompat.conf +8. The ‘at_console’ context is deprecated and will be ignored in the future.
    Aug 05 08:07:40 locutus systemd[1]: Reloaded D-Bus System Message Bus.

The connman related one is most likely an upcoming artifact in: /usr/share/dbus-1/system.d/connman-nmcompat.conf.
Maybe the entry should be removed/commented out  ? My personal fix happen to be a NoExtract/NoUpgrade, as I don't run NetManager, but YMMV.

The other mesgs can probably be fixed by a better post-install processing to account for user/pkg presence, which raises a question that is probably beyond the scope of this post. As I understand it, when user entries are created as part of a pkg install, the UID choice is somewhat random. This is not necessarily great if I'm building a bunch of hosts to manage together. In the old days of sysadm-ing, we generally like information consistency and use central management system like NIS, LDAP, etc, etc. I'm manually fixing inconsistencies between hosts as the scale is still small. Has any thought been given to have a central registry for system/application accounts like the /etc/services file ?

Offline

#2 2025-08-06 21:30:47

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 69,056

Offline

Board footer

Powered by FluxBB