Diagnostic code
ZBX-E0301
can't reach the systemd user manager over D-Bus
- Kind
- error
- Blame
- environment
- Exit code
- 2 (125 in zbx run)
What it means
zbx puts each container in its own cgroup, a transient systemd "scope" of the user's systemd manager, and asks for it over the user's D-Bus socket ($DBUS_SESSION_BUS_ADDRESS, or $XDG_RUNTIME_DIR/bus). It could not get there: nothing set the address, the socket is missing or refuses connections, the address is not a unix:path= one, or the bus has no systemd on it.
The cause says which. The usual one is a login with no systemd user session: ssh without PAM's systemd module, su, or sudo -u. Log in through a systemd session, or keep the manager running with "loginctl enable-linger $USER". "zbx doctor" runs the same probe.
Offline
The same text, without a network:
zbx explain E0301