[ZBX-16511] Undescriptive error in log - unknown request received [host availability] Created: 2019 Aug 14  Updated: 2024 Apr 10  Resolved: 2019 Sep 16

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Server (S)
Affects Version/s: 4.2.5
Fix Version/s: 4.2.7rc1, 4.4.0alpha3, 4.4 (plan)

Type: Patch request Priority: Major
Reporter: Edgars Melveris Assignee: Andrejs Tumilovics
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Causes
caused by ZBX-16510 Backwards compatibility for older pro... Closed
Duplicate
Team: Team C
Team: Team C
Sprint: Sprint 56 (Sep 2019), Sprint 55 (Aug 2019)
Story Points: 0.25

 Description   

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.

 Comments   
Comment by Andrejs Tumilovics [ 2019 Sep 12 ]

Fixed in:

  • 4.2.7rc1 6a5a0c4216
  • 4.4.0alpha3 (master) 6a5a0c4216
Generated at Sat Apr 20 05:49:17 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.