-
Problem report
-
Resolution: Duplicate
-
Trivial
-
None
-
6.2.7
-
None
-
Debian 11
I had a properly functioning zabbix-agent2 on a debian 11 vm until 30th of January. On that date the systemd.unit.get started failing with dbus errors reported in a log file.
zabbix-agent2 logs (shown only for lm-sensors.service, but applies to all other services as well).
First call after service restart:
2023/02/11 05:38:19.016755 received passive check request: 'systemd.unit.get["lm-sensors.service"]' from '192.168.10.12' 2023/02/11 05:38:19.016804 [1] processing update request (1 requests) 2023/02/11 05:38:19.016809 [1] registering new client 2023/02/11 05:38:19.016814 Calling C function "new_global_regexp()" 2023/02/11 05:38:19.016827 [1] adding new request for key: 'systemd.unit.get["lm-sensors.service"]' 2023/02/11 05:38:19.016837 [1] created direct exporter task for plugin 'Systemd' itemid:0 key 'systemd.unit.get["lm-sensors.service"]' 2023/02/11 05:38:19.016861 executing direct exporter task for key 'systemd.unit.get["lm-sensors.service"]' 2023/02/11 05:38:19.019604 failed to execute direct exporter task for key 'systemd.unit.get["lm-sensors.service"]' error: 'Cannot get unit property: dbus: wire format error: unexpected EOF' 2023/02/11 05:38:19.019648 sending passive check response: ZBX_NOTSUPPORTED: 'Cannot get unit property: dbus: wire format error: unexpected EOF' to '192.168.10.12'
Subsequent calls:
2023/02/11 05:39:09.328583 received passive check request: 'systemd.unit.get["lm-sensors.service"]' from '192.168.10.12' 2023/02/11 05:39:09.328622 [1] processing update request (1 requests) 2023/02/11 05:39:09.328641 [1] adding new request for key: 'systemd.unit.get["lm-sensors.service"]' 2023/02/11 05:39:09.328650 [1] created direct exporter task for plugin 'Systemd' itemid:0 key 'systemd.unit.get["lm-sensors.service"]' 2023/02/11 05:39:09.328687 executing direct exporter task for key 'systemd.unit.get["lm-sensors.service"]' 2023/02/11 05:39:09.328705 failed to execute direct exporter task for key 'systemd.unit.get["lm-sensors.service"]' error: 'Cannot get unit property: dbus: connection closed by user' 2023/02/11 05:39:09.328729 sending passive check response: ZBX_NOTSUPPORTED: 'Cannot get unit property: dbus: connection closed by user' to '192.168.10.12'
The issue started on 30th of January, shortly after performing apt upgrade:
Start-Date: 2023-01-30 21:32:01
Commandline: /usr/bin/apt-get -y -o Dpkg::Options::=--force-confdef -o Dpkg::Options::=--force-confold upgrade --with-new-pkgs --auto-remove
Upgrade: containerd.io:amd64 (1.6.15-1, 1.6.16-1), udev:amd64 (251.3-1~bpo11+1, 252.4-1~bpo11+1), bind9-host:amd64 (1:9.16.33-1~deb11u1, 1:9.16.37-1~deb11u1), systemd-timesyncd:amd64 (251.3-1~bpo11+1, 252.4-1~bp
o11+1), libpam-systemd:amd64 (251.3-1~bpo11+1, 252.4-1~bpo11+1), libtiff5:amd64 (4.2.0-1+deb11u1, 4.2.0-1+deb11u3), libsystemd0:amd64 (251.3-1~bpo11+1, 252.4-1~bpo11+1), libnss-systemd:amd64 (251.3-1~bpo11+1, 25
2.4-1~bpo11+1), systemd:amd64 (251.3-1~bpo11+1, 252.4-1~bpo11+1), libudev1:amd64 (251.3-1~bpo11+1, 252.4-1~bpo11+1), bind9-libs:amd64 (1:9.16.33-1~deb11u1, 1:9.16.37-1~deb11u1), libsystemd-shared:amd64 (251.3-1~
bpo11+1, 252.4-1~bpo11+1), systemd-sysv:amd64 (251.3-1~bpo11+1, 252.4-1~bpo11+1)
End-Date: 2023-01-30 21:32:49
Due to similarity to ZBX-21845, I've also checked dbus version installed (although it was installed on 2022-10-07):
dpkg -l|grep dbus
ii dbus 1.12.24-0+deb11u1 amd64 simple interprocess messaging system (daemon and utilities)
ii dbus-user-session 1.12.24-0+deb11u1 amd64 simple interprocess messaging system (systemd --user integration)
ii libdbus-1-3:amd64 1.12.24-0+deb11u1 amd64 simple interprocess messaging system (library)
ii python3-dbus 1.2.16-5 amd64 simple interprocess messaging system (Python 3 interface)
It does seem quite old to have an effect here. Some dbus triggers were executed on 30th of Jan, though.
SELinux is disabled on this system.
Problem looks similar to: ZBX-22281
Potentially related to: ZBX-21845
- duplicates
-
-
- Closed
-