DBUS daemon starting under standard username on SSH login
This is a question relating to SSH logins and DBUS config. We have a monitoring product that performs an SSH login every few minutes to its monitored hosts, including itself (on the lo address).
Intermittently and infrequently, this times out and returns "no data" on certain OL8.4 hosts (including localhost, so the network appears not to be the cause).
.. I'm sure this is normal; these are standard OL8.4 builds. But it's been reported to me that on OL8 hosts where this doesn't happen, ie where the "no data" error does not arise - there is no dbus-daemon process running under the SSH login username while it's logged in.
Intermittently and infrequently, this times out and returns "no data" on certain OL8.4 hosts (including localhost, so the network appears not to be the cause).
It's evident that on the OL8 hosts where this is the case, a DBUS daemon is spawned by the SSH session like this:
sshtst 2512488 2512421 0 09:53 ? 00:00:00 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
.. I'm sure this is normal; these are standard OL8.4 builds. But it's been reported to me that on OL8 hosts where this doesn't happen, ie where the "no data" error does not arise - there is no dbus-daemon process running under the SSH login username while it's logged in.
Tagged:
0