[ZBXNEXT-9138] zabbix fails to work with recent versions of mysql_aurora - "content_type" column name is reserved Created: 2024 Apr 19 Updated: 2024 Sep 03 Resolved: 2024 May 06 |
|
Status: | Closed |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | API (A), Frontend (F), Server (S) |
Affects Version/s: | 5.0.42 |
Fix Version/s: | 7.0.0rc1, 7.0 (plan) |
Type: | New Feature Request | Priority: | Major |
Reporter: | Oleksii Zagorskyi | Assignee: | Alexander Vladishev |
Resolution: | Fixed | Votes: | 0 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Attachments: | frontend-error.png | ||||||||||||||||||||
Issue Links: |
|
||||||||||||||||||||
Epic Link: | Zabbix 7.0 | ||||||||||||||||||||
Team: | Team A | ||||||||||||||||||||
Sprint: | S24-W16/17, S24-W18/19 | ||||||||||||||||||||
Story Points: | 1 |
Description |
Zabbix server produces error: 34385:20240419:074505.215 [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 'content_type,script,timeout,process_tags from media_type where mediatypeid=1' at line 1 [select mediatypeid,type,smtp_server,smtp_helo,smtp_email,exec_path,gsm_modem,username,passwd,smtp_port,smtp_security,smtp_verify_peer,smtp_verify_host,smtp_authentication,exec_params,maxsessions,maxattempts,attempt_interval,content_type,script,timeout,process_tags from media_type where mediatypeid=1] The same error is when test from command line. Frontend also shows an error "Cannot find specified media type" when manually test it, see screenshot. This error appeared after upgrading DB engine from 5.7.mysql_aurora.2.11.4 to 8.0.mysql_aurora.3.06.0 Related discussion is https://github.com/znuny/Znuny/issues/548 Not sure how this can/should be addressed in zabbix. Should be discussed. |
Comments |
Comment by Alexander Vladishev [ 2024 Apr 22 ] |
Officially, we do not support this distribution of MySQL and cannot consider it as a bug report. I'm moving this to the ZBXNEXT project. |
Comment by Stefano Ghelfi [ 2024 Apr 22 ] |
Just to provide more context, we have 2 ZBX infrastructures in AWS (PROD & DEV) that are composed by: ZBX FE: Running in ECS (Prod & Dev) ZBX Server: Running in EC2 (Prod & Dev - c4.xlarge RHÂ 7.9) ZBX DB: Running in Aurora MySQL:
|
Comment by Alexander Vladishev [ 2024 May 03 ] |
Available in version:
Updated 7.0 API documentation: Updated 7.0 documentation: |