Hi everyone!
When I returned to the office after a 5 week illness, I found that the zabbix-server was not running. Although the web interface is accessible, it only shows that the server is not running.
Every attempt to start the server failed.
It is also important to note that during my absence the server had written the hard disk full of mysql log files. I then enlarged the disk (LVM under Ubuntu 22.04). Obviously there are problems with the consistency of the database?
The error messages at startup:
● zabbix-server.service - Zabbix Server
Loaded: loaded (/lib/systemd/system/zabbix-server.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: protocol) since Mon 2023-01-09 10:32:25 CET; 9s ago
Process: 125283 ExecStart=/usr/sbin/zabbix_server -c $CONFFILE (code=exited, status=0/SUCCESS)
CPU: 23ms
zabbix_server.log says:
125309:20230109:103349.689 Starting Zabbix Server. Zabbix 6.0.12 (revision 126aa2f53e9).
125309:20230109:103349.690 ****** Enabled features ******
125309:20230109:103349.690 SNMP monitoring: YES
125309:20230109:103349.690 IPMI monitoring: YES
125309:20230109:103349.690 Web monitoring: YES
125309:20230109:103349.690 VMware monitoring: YES
125309:20230109:103349.690 SMTP authentication: YES
125309:20230109:103349.690 ODBC: YES
125309:20230109:103349.690 SSH support: YES
125309:20230109:103349.690 IPv6 support: YES
125309:20230109:103349.690 TLS support: YES
125309:20230109:103349.690 ******************************
125309:20230109:103349.690 using configuration file: /etc/zabbix/zabbix_server.conf
125309:20230109:103349.707 current database version (mandatory/optional): 06000000/06000010
125309:20230109:103349.707 required mandatory version: 06000000
125309:20230109:103349.707 optional patches were found
125309:20230109:103349.707 starting automatic database upgrade
125309:20230109:103349.708 [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)]
125309:20230109:103349.709 database upgrade failed
125309:20230109:103349.711 database could be upgraded to use primary keys in history tables
I would appreciate any advice on how to get the server up and running again
Best regards!
poessibility
When I returned to the office after a 5 week illness, I found that the zabbix-server was not running. Although the web interface is accessible, it only shows that the server is not running.
Every attempt to start the server failed.
It is also important to note that during my absence the server had written the hard disk full of mysql log files. I then enlarged the disk (LVM under Ubuntu 22.04). Obviously there are problems with the consistency of the database?
The error messages at startup:
● zabbix-server.service - Zabbix Server
Loaded: loaded (/lib/systemd/system/zabbix-server.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: protocol) since Mon 2023-01-09 10:32:25 CET; 9s ago
Process: 125283 ExecStart=/usr/sbin/zabbix_server -c $CONFFILE (code=exited, status=0/SUCCESS)
CPU: 23ms
zabbix_server.log says:
125309:20230109:103349.689 Starting Zabbix Server. Zabbix 6.0.12 (revision 126aa2f53e9).
125309:20230109:103349.690 ****** Enabled features ******
125309:20230109:103349.690 SNMP monitoring: YES
125309:20230109:103349.690 IPMI monitoring: YES
125309:20230109:103349.690 Web monitoring: YES
125309:20230109:103349.690 VMware monitoring: YES
125309:20230109:103349.690 SMTP authentication: YES
125309:20230109:103349.690 ODBC: YES
125309:20230109:103349.690 SSH support: YES
125309:20230109:103349.690 IPv6 support: YES
125309:20230109:103349.690 TLS support: YES
125309:20230109:103349.690 ******************************
125309:20230109:103349.690 using configuration file: /etc/zabbix/zabbix_server.conf
125309:20230109:103349.707 current database version (mandatory/optional): 06000000/06000010
125309:20230109:103349.707 required mandatory version: 06000000
125309:20230109:103349.707 optional patches were found
125309:20230109:103349.707 starting automatic database upgrade
125309:20230109:103349.708 [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)]
125309:20230109:103349.709 database upgrade failed
125309:20230109:103349.711 database could be upgraded to use primary keys in history tables
I would appreciate any advice on how to get the server up and running again
Best regards!
poessibility
Comment