[ZBX-9272] Zabbix proxy error when server are sending configuration data Created: 2015 Feb 02 Updated: 2017 May 30 Resolved: 2015 Feb 20 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Proxy (P), Server (S) |
Affects Version/s: | 2.4.0, 2.4.3 |
Fix Version/s: | None |
Type: | Incident report | Priority: | Trivial |
Reporter: | Marius | Assignee: | Unassigned |
Resolution: | Won't fix | Votes: | 0 |
Labels: | database | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified | ||
Environment: |
— Server: — — Proxy: — |
Attachments: |
![]() ![]() ![]() ![]() |
Description |
I've installed zabbix proxy server (with load of schema.sql to DB and zabbix_proxy.conf configuration). Proxy was added on server side (with one host for monitoring). Then I've got error on proxy: 17659:20150202:115503.220 received configuration data from server, datalen 2816 |
Comments |
Comment by Alexander Vladishev [ 2015 Feb 03 ] |
Could you please attach proxy log file with debug level 4 (between "trapper got '<configuration data>'" and "End of recv_proxyconfig()") and dump of the server database schema. Thank you. |
Comment by Marius [ 2015 Feb 06 ] |
There are attached files 1. zabbix proxy debug (level 4)":zabbix_proxy_debug4.txt 2. Zabbix server database schema dump: zabbix_server_dbschema_dump.txt |
Comment by Igors Homjakovs (Inactive) [ 2015 Feb 13 ] |
Marius, Could you please send us the content of the tables config and groups from your server's database? |
Comment by Marius [ 2015 Feb 13 ] |
Tables "config" and "groups" from our server's database. |
Comment by Igors Homjakovs (Inactive) [ 2015 Feb 16 ] |
Marius, In your database discovery_groupid in the config table is 0, but the table groups has no row with this groupid. First, this is strange because there is a constraint to avoid that: CONSTRAINT `c_config_2` FOREIGN KEY (`discovery_groupid`) REFERENCES `groups` (`groupid`). Second, there shouldn’t be a group with id equal to zero. One of the possible reasons is the corruption of the database. You can either try to make a dump of your database, create a new database and then load the data to the new database or change the discovery_groupid to the appropriate value. However, if the database is corrupted you might face other problems after some time. |
Comment by Alexander Vladishev [ 2015 Feb 20 ] |
It seems the problem in a broken database. I close the issue. Feel free to reopen this problem if you have any news. |
Comment by Julius [ 2015 Apr 16 ] |
Administration->General->Group for discovered hosts selected different host group and updated |