-
Incident report
-
Resolution: Unresolved
-
Trivial
-
None
-
7.2.3
-
None
-
Zabbix Server 7.2.3 on Debian 12
Zabbix Agent 2 6.0.9 on SLES15 SP1
Steps to reproduce:
- Have a Zabbix Server in 7.2
- Create an item zabbix[host,active_agent,available] on a SLES15 host with Zabbix Agent 2 6.0
Result:
Zabbix active agent availability : not available (0)
And here is the log :
2025/02/11 13:39:19.001130 [101] active check configuration update from host [hostname] started to fail 2025/02/11 13:41:20.009046 [101] active check configuration update from [zabbixFQDN:10051] is working again 2025/02/11 13:46:26.415281 [101] cannot connect to [zabbixFQDN:10051]: read tcp X.X.X.X:29043->X.X.X.X:10051: read: connection reset by peer 2025/02/11 13:46:26.415348 [101] history upload to [zabbixFQDN:10051] [hostname] started to fail 2025/02/11 13:46:27.416971 [101] cannot connect to [zabbixFQDN:10051]: dial tcp :0->X.X.X.X:10051: connect: connection refused 2025/02/11 13:46:27.417003 [101] history upload to [zabbixFQDN:10051] [hostname] started to fail 2025/02/11 13:47:01.198902 [101] history upload to [zabbixFQDN:10051] [hostname] is working again 2025/02/11 13:49:31.093415 [101] cannot connect to [zabbixFQDN:10051]: read tcp X.X.X.X:55387->X.X.X.X:10051: read: connection reset by peer 2025/02/11 13:49:31.093455 [101] history upload to [zabbixFQDN:10051] [hostname] started to fail 2025/02/11 13:49:32.098587 [101] history upload to [zabbixFQDN:10051] [hostname] is working again
This is the only issue with the 6.0 Agent2; everything else is working correctly.
The problem arises because we cannot deploy an agent newer than 6.0, as our SLES15 SP1 has GLIBC_2.26 instead of GLIBC_2.28.