[systemd] failed to get d-bus session:
dragan1979 opened this issue · 7 comments
output from zabbix agent
[systemd] failed to get d-bus session: Failed to connect to socket /run/dbus/system_bus_socket: Permission denied
Please provide agent logs - https://github.com/cavaliercoder/zabbix-module-systemd#debugging
and your SELinux configuration - https://github.com/cavaliercoder/zabbix-module-systemd#selinux, OS/systemd versions, ... Generally, all information which will help to replicate your issue.
I disabled SELinux and then got processes in zabbix, only for 6 services getting exclamation mark (Cannot open cpuacct.stat file/Cannot open memory.stat file) under monitor-latest data
[systemd] cannot open metric file: '/sys/fs/cgroup/memory/system.slice/irqbalance.service/memory.stat'
14852:20180821:220840.725 [systemd] cannot open metric file: '/sys/fs/cgroup/cpu,cpuacct/system.slice/kdump.service/cpuacct.stat'
14853:20180821:220844.007 [systemd] cannot open metric file: '/sys/fs/cgroup/cpu,cpuacct/system.slice/irqbalance.service/cpuacct.stat'
14853:20180821:220851.309 [systemd] cannot open metric file: '/sys/fs/cgroup/memory/system.slice/getty@tty1.service/memory.stat'
14852:20180821:221802.714 [systemd] cannot open metric file: '/sys/fs/cgroup/cpu,cpuacct/system.slice/getty@tty1.service/cpuacct.stat'
14853:20180821:221810.083 [systemd] cannot open metric file: '/sys/fs/cgroup/cpu,cpuacct/system.slice/kdump.service/cpuacct.stat'
14854:20180821:221814.101 [systemd] cannot open metric file: '/sys/fs/cgroup/cpu,cpuacct/system.slice/irqbalance.service/cpuacct.stat'
14854:20180821:221821.358 [systemd] cannot open metric file: '/sys/fs/cgroup/memory/system.slice/getty@tty1.service/memory.stat'
14852:20180821:221829.482 [systemd] cannot open metric file: '/sys/fs/cgroup/memory/system.slice/kdump.service/memory.stat'
14854:20180821:221833.588 [systemd] cannot open metric file: '/sys/fs/cgroup/memory/system.slice/irqbalance.service/memory.stat'
sorry, don't follow, all above files don't exist on my system, not sure what should i do to get rid of above message-to disable those items ?
See #12 => that's already reported issue. If you want to resolve it, then you need to.make your hand dirty, because this issue is still not resolved => you will need to code it or wait for resolution provided by someone else.
ok, thanks,last question:
in systems where SELinux is ON (enforced)
how to add exception to get rid of
[systemd] failed to get d-bus session: Failed to connect to socket /run/dbus/system_bus_socket: Permission denied
stupid me, sorry didn't see SELinux link, will try and open new issue if face errors, thanks a lot for this template !!