-
Patch request
-
Resolution: Fixed
-
Major
-
4.2.5
-
None
-
Sprint 56 (Sep 2019), Sprint 55 (Aug 2019)
-
0.25
This is partially caused by ZBX-16510
After upgrade to 4.2.5 if you happen to have a forgotten Zabbix proxy 3.2 or earlier, you will start to get these errors in the log:
3469:20190814:091418.139 unknown request received [host availability]
This is of course caused by misconfiguration, as different major versions for proxies are not supported. But the error itself is very undescriptive and it's very hard to find the rogue proxy from Zabbix itself, if it's been removed from the frontend. Increasing the debug level can help to guess, where it's coming from, but still doesn't contain an address:
3464:20190814:093225.841 zbx_setproctitle() title:'trapper #2 [processing data]' 3464:20190814:093225.841 trapper got '{"request":"host availability","host":"test proxy","data":[{"hostid":10105,"available":2,"error":"Received empty response from Zabbix Agent at [127.0.0.1]. Assuming that agent dropped connection because of access permissions.","snmp_available":0,"snmp_error":"","ipmi_available":0,"ipmi_error":"","jmx_available":0,"jmx_error":""}]}' 3464:20190814:093225.842 unknown request received [host availability]
The error is created from src/zabbix_server/trapper/trapper.c line 1166
else zabbix_log(LOG_LEVEL_WARNING, "unknown request received [%s]", value);
Please add at least IP address of the host, that sends this data.
- caused by
-
-
- Closed
-
