[ZBX-13777] Error zabbix-proxy on MySQL 8.0.11 Created: 2018 Apr 20  Updated: 2018 Apr 20  Resolved: 2018 Apr 20

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Proxy (P)
Affects Version/s: 3.4.8
Fix Version/s: None

Type: Incident report Priority: Critical
Reporter: Mikhail Grigorev Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: error, mysql, sql
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Oracle Linux Server release 6.9

Issue Links:
Duplicate
duplicates ZBXNEXT-4569 "groups" (8.0.2) and "function" (8.0.... Closed

 Description   

I use zabbix-proxy 3.4.8 on Oracle Linux Server release 6.9

I updated MySQL 5.7.21 to 8.0.11 and start zabbix-proxy.
I got this error message (among many similar ones):

/var/log/zabbix/zabbix_proxy.log
[Z3005] query failed: [1064] You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'groups' at line 1 [select groupid from groups]

Full log:

/var/log/zabbix/zabbix_proxy.log
  7679:20180420:141439.736 Starting Zabbix Proxy (active) [proxy-zabbix]. Zabbix 3.4.8 (revision 79252).
  7679:20180420:141439.736 **** Enabled features ****
  7679:20180420:141439.736 SNMP monitoring:       YES
  7679:20180420:141439.736 IPMI monitoring:       YES
  7679:20180420:141439.736 Web monitoring:        YES
  7679:20180420:141439.736 VMware monitoring:     YES
  7679:20180420:141439.736 ODBC:                  YES
  7679:20180420:141439.736 SSH2 support:          YES
  7679:20180420:141439.736 IPv6 support:          YES
  7679:20180420:141439.736 TLS support:           YES
  7679:20180420:141439.736 **************************
  7679:20180420:141439.736 using configuration file: /etc/zabbix/zabbix_proxy.conf
  7679:20180420:141439.882 current database version (mandatory/optional): 03040000/03040007
  7679:20180420:141439.882 required mandatory version: 03040000
  7679:20180420:141440.604 [Z3005] query failed: [1064] You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'groups' at line 1 [select groupid,name from groups]
  7679:20180420:141440.605 proxy #0 started [main process]
  7681:20180420:141440.606 proxy #1 started [configuration syncer #1]
  7682:20180420:141440.606 proxy #2 started [heartbeat sender #1]
  7683:20180420:141440.606 proxy #3 started [data sender #1]
  7684:20180420:141440.607 proxy #4 started [housekeeper #1]
  7685:20180420:141440.607 proxy #5 started [http poller #1]
  7686:20180420:141440.608 proxy #6 started [http poller #2]
  7687:20180420:141440.608 proxy #7 started [discoverer #1]
  7689:20180420:141440.609 proxy #9 started [history syncer #1]
  7690:20180420:141440.609 proxy #10 started [history syncer #2]
  7688:20180420:141440.609 proxy #8 started [discoverer #2]
  7692:20180420:141440.610 proxy #11 started [history syncer #3]
  7694:20180420:141440.610 proxy #12 started [history syncer #4]
  7697:20180420:141440.610 proxy #13 started [self-monitoring #1]
  7698:20180420:141440.611 proxy #14 started [task manager #1]
  7699:20180420:141440.611 proxy #15 started [poller #1]
  7700:20180420:141440.612 proxy #16 started [poller #2]
  7701:20180420:141440.612 proxy #17 started [poller #3]
  7702:20180420:141440.613 proxy #18 started [poller #4]
  7703:20180420:141440.613 proxy #19 started [poller #5]
  7704:20180420:141440.613 proxy #20 started [poller #6]
  7705:20180420:141440.614 proxy #21 started [unreachable poller #1]
  7706:20180420:141440.614 proxy #22 started [unreachable poller #2]
  7707:20180420:141440.615 proxy #23 started [trapper #1]
  7708:20180420:141440.615 proxy #24 started [trapper #2]
  7709:20180420:141440.615 proxy #25 started [trapper #3]
  7710:20180420:141440.616 proxy #26 started [trapper #4]
  7711:20180420:141440.616 proxy #27 started [trapper #5]
  7712:20180420:141440.616 proxy #28 started [icmp pinger #1]
  7681:20180420:141443.232 received configuration data from server at "YYY.YYY.YYY.YYY", datalen 2134877
  7681:20180420:141444.011 [Z3005] query failed: [1064] You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'groups' at line 1 [select groupid from groups]
  7681:20180420:141444.076 failed to update local proxy configuration copy: database error
  7709:20180420:141509.986 cannot send list of active checks to "127.0.0.1": host [XXXXXXX] not found
  7681:20180420:141545.535 received configuration data from server at "YYY.YYY.YYY.YYY", datalen 2134877
  7681:20180420:141546.053 [Z3005] query failed: [1064] You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'groups' at line 1 [select groupid from groups]
  7681:20180420:141546.112 failed to update local proxy configuration copy: database error
  7679:20180420:141614.769 Got signal [signal:15(SIGTERM),sender_pid:9035,sender_uid:0,reason:0]. Exiting ...
  7679:20180420:141616.771 syncing history data...
  7679:20180420:141616.771 syncing history data done
  7679:20180420:141616.771 Zabbix Proxy stopped. Zabbix 3.4.8 (revision 79252).

How can I fix this problem?

 Comments   
Comment by richlv [ 2018 Apr 20 ]

Oh, an interesting one. groups was added as a reserved keyword in 8.0.2. This probably makes MySQL 8.0 unsupported.

GROUPS (R) added in 8.0.2 (reserved)

https://dev.mysql.com/doc/refman/8.0/en/keywords.html

Comment by Mikhail Grigorev [ 2018 Apr 20 ]

When will Zabbix developers be able to add support for MySQL 8.0?

Can I expect this in the next release?

Comment by Andris Mednis [ 2018 Apr 20 ]

https://blogs.oracle.com/mysql/announcing-general-availability-of-mysql-80 announced MySQL 8.0 General Availability on Thursday, April 19, 2018 (yesterday)

Comment by Vladislavs Sokurenko [ 2018 Apr 20 ]

Thank you for your report, closing as duplicate.

Generated at Thu Apr 25 23:33:20 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.