Metricset system: users and service

Elastic Stack Beats
,
1

Hi,
I'm running metricbeat on container and i have found this error:

{"level":"error","timestamp":"2022-03-27T16:12:45.481Z","logger":"reload","caller":"cfgfile/list.go:99","message":"Error creating runner from config: 2 errors: error connecting to dbus: read unix @->/run/systemd/private: read: connection reset by peer; error connecting to dbus: error authenticating: dbus: authentication failed"}

I have found out that only 2 metricsets generate this error: Users and Service.
In this guide System users metricset it's recommended to:

By default, the metricset will look in /var/run/dbus/ for a system socket, although a new path can be selected with DBUS_SYSTEM_BUS_ADDRESS .

Is there any recommendation how to do it? Or a simple guide to follow?
I'm using centos7 and the running command of the container has this volumes:

  • --volume="/var/run/dbus/system_bus_socket:/var/run/dbus/system_bus_socket"
  • --volume="/run/systemd/private:/run/systemd/private:ro"
  • --volume="/var/run/dbus/:/var/run/dbus/"
2

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