Zabbix 5.4 > 6.0 mysql database upgrade error

[garryavx]

...so it's working fine in the GUI after the upgrade but I get this spam in the log:

27791:20230213:220845.879 database upgrade failed
 27791:20230213:220845.882 database could be upgraded to use primary keys in history tables
 27795:20230213:220858.107 Starting Zabbix Server. Zabbix 6.0.13 (revision fdfa8cef9ce).
 27795:20230213:220858.108 ****** Enabled features ******
 27795:20230213:220858.108 SNMP monitoring:           YES
 27795:20230213:220858.108 IPMI monitoring:           YES
 27795:20230213:220858.108 Web monitoring:            YES
 27795:20230213:220858.108 VMware monitoring:         YES
 27795:20230213:220858.108 SMTP authentication:       YES
 27795:20230213:220858.108 ODBC:                      YES
 27795:20230213:220858.108 SSH support:               YES
 27795:20230213:220858.108 IPv6 support:              YES
 27795:20230213:220858.108 TLS support:               YES
 27795:20230213:220858.108 ******************************
 27795:20230213:220858.108 using configuration file: /etc/zabbix/zabbix_server.conf
 27795:20230213:220858.125 current database version (mandatory/optional): 06000000/06000010
 27795:20230213:220858.125 required mandatory version: 06000000
 27795:20230213:220858.125 optional patches were found
 27795:20230213:220858.125 starting automatic database upgrade
 27795:20230213:220858.126 [Z3005] query failed: [1419] You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable) [create trigger hosts_name_upper_insert
before insert on hosts for each row
set new.name_upper=upper(new.name)]
 27795:20230213:220858.126 database upgrade failed
 27795:20230213:220858.129 database could be upgraded to use primary keys in history tables​

not sure what to make of it since the front end seems blissfully unaware of any problems.

on centos stream 8, mysql + nginx zabbix_server install

what other info can I give to help?

[garryavx]

oh, JK I get this message on the GUI, so yeah it's borked then.

[garryavx]

nvm found a post on this forum about a similiar issue:

https://www.zabbix.com/forum/zabbix-troubleshooting-and-problems/447359-unable-to-initialize-mysql-database-in-6-2-per-documentation

followed the steps to set the flag:
I've just had the same issue with MySQL 8.0.29.
For future reference, this is what I did.

When checking the database, I found "log_bin_trust_function_creators" was set to "Off".
Code:

mysql> SHOW VARIABLES LIKE 'log_bin_trust_function_creators'; +---------------------------------+-------+ | Variable_name | Value | +---------------------------------+-------+ | log_bin_trust_function_creators | OFF | +---------------------------------+-------+
Therefore, as suggested by Atsushi , we can simply set it to "On" (1).
Code:

mysql> SET GLOBAL log_bin_trust_function_creators = 1;
T