[ZBX-15092] Active Checks not reported to Zabbix Created: 2018 Oct 30 Updated: 2018 Dec 19 Resolved: 2018 Dec 19 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Agent (G), Proxy (P) |
Affects Version/s: | 3.4.14, 4.0.2 |
Fix Version/s: | None |
Type: | Incident report | Priority: | Trivial |
Reporter: | Daniel Weber | Assignee: | Unassigned |
Resolution: | Won't fix | Votes: | 0 |
Labels: | usability | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified | ||
Environment: |
We have Zabbix Server, Zabbix Proxy and Zabbix Clients |
Description |
Steps to reproduce:
Result: Zabbix Agent Checks are there Zabbix Agent Active Checks are not displayed Log File shows: 22554:20181030:045215.477 In recv_agenthistory() Only in Debug Mode! Machine TESTMachine01.test.lds not found for sending active Checks to Zabbix
|
Comments |
Comment by Daniel Weber [ 2018 Oct 30 ] |
The Data will not be published on Zabbix, because the Name of the machine mismatches the Upper-Lower-Case of the Hostname in Zabbix. |
Comment by Aigars Kadikis [ 2018 Dec 06 ] |
Hello Daniel, version 3.4 is unsupported version https://www.zabbix.com/life_cycle_and_release_policy I checked this scenario with Zabbix server version 4.0.2 together with Zabbix agent 4.0.2 and, yes, the problem is relevant. Regarding active checks there definitely should be error message inside zabbix_agentd.log: no active checks on server [zabbix.server.domain:10051]: host [TESTMachine01.test.lds] not found I would like to name this problem as "Hostname title are not respected in case sensitive manner". |
Comment by Aigars Kadikis [ 2018 Dec 06 ] |
Hello Daniel, We need more info. Please authorize inside database client and execute these queries on to 'zabbix' database: show create database zabbix\G; show create table hosts\G; |
Comment by Aigars Kadikis [ 2018 Dec 19 ] |
Hello daniel.weber , Just concluded a summary from this problem. I had this issue on a well-lived instance too. This is very related to 'COLLATE=utf8_bin'. Either it is in database level or in table level. You can check the COLLATE situation with: show create database zabbix; # it should report: # CREATE DATABASE `zabbix` /*!40100 DEFAULT CHARACTER SET utf8 COLLATE utf8mb4_bin */ SELECT * FROM information_schema.TABLES WHERE table_schema = 'zabbix' AND table_collation != 'utf8_bin'; # it should report nothing
|