zabbix-server.service problem!!!

[@ndres]

Hello.

I have a problem with this service in a clean installation:

Instructions:
https://www.zabbix.com/download?zabb...oracle_linux&o s_version=8&components=server_frontend_agent&db=my sql&ws=apache

Issue:

[root@Monitoreo zabbix]# pwd
/run/zabbix
[root@Monitoreo zabbix]# ll
total 4
-rw-rw-r-- 1 zabbix zabbix 4 Sep 2 13:29 zabbix_agentd.pid
srwx------ 1 zabbix zabbix 0 Sep 2 13:51 zabbix_server_rtc.sock
[root@Monitoreo zabbix]# more /etc/oracle-release
Oracle Linux Server release 8.6
[root@Monitoreo zabbix]#

[root@Monitoreo zabbix]# systemctl start zabbix-server
Job for zabbix-server.service failed because the service did not take the steps required by its unit configuration.
See "systemctl status zabbix-server.service" and "journalctl -xe" for details.
[root@Monitoreo zabbix]# systemctl status zabbix-server
● zabbix-server.service - Zabbix Server
Loaded: loaded (/usr/lib/systemd/system/zabbix-server.service; enabled; vendor preset: disabled)
Active: activating (start) since Fri 2022-09-02 13:53:00 -05; 1s ago
Main PID: 1634 (code=exited, status=1/FAILURE); Control PID: 3114 (zabbix_server)
Tasks: 2 (limit: 100492)
Memory: 2.5M
CGroup: /system.slice/zabbix-server.service
└─3114 /usr/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf

Sep 02 13:53:00 Monitoreo systemd[1]: Starting Zabbix Server...
[root@Monitoreo zabbix]#

[root@Monitoreo zabbix]# systemctl status zabbix-server.service
● zabbix-server.service - Zabbix Server
Loaded: loaded (/usr/lib/systemd/system/zabbix-server.service; enabled; vendor preset: disabled)
Active: activating (auto-restart) (Result: protocol) since Fri 2022-09-02 13:53:26 -05; 8s ago
Process: 3125 ExecStart=/usr/sbin/zabbix_server -c $CONFFILE (code=exited, status=0/SUCCESS)
Main PID: 1634 (code=exited, status=1/FAILURE)
[root@Monitoreo zabbix]#

[root@Monitoreo zabbix]# journalctl -xe
--
-- Unit zabbix-server.service has finished shutting down.
Sep 02 13:53:37 Monitoreo systemd[1]: Starting Zabbix Server...
-- Subject: Unit zabbix-server.service has begun start-up
-- Defined-By: systemd
-- Support: https://support.oracle.com
--
-- Unit zabbix-server.service has begun starting up.
Sep 02 13:53:39 Monitoreo systemd[1]: zabbix-server.service: Can't open PID file /run/zabbix/zabbix_server.pid (yet?) after start: No such file or directory
Sep 02 13:53:39 Monitoreo systemd[1]: zabbix-server.service: Failed with result 'protocol'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://support.oracle.com
--
-- The unit zabbix-server.service has entered the 'failed' state with result 'protocol'.
Sep 02 13:53:39 Monitoreo systemd[1]: Failed to start Zabbix Server.
-- Subject: Unit zabbix-server.service has failed
-- Defined-By: systemd
-- Support: https://support.oracle.com
--
-- Unit zabbix-server.service has failed.
--
-- The result is failed.
Sep 02 13:53:49 Monitoreo systemd[1]: zabbix-server.service: Service RestartSec=10s expired, scheduling restart.
Sep 02 13:53:49 Monitoreo systemd[1]: zabbix-server.service: Scheduled restart job, restart counter is at 86.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://support.oracle.com
--
-- Automatic restarting of the unit zabbix-server.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Sep 02 13:53:49 Monitoreo systemd[1]: Stopped Zabbix Server.
-- Subject: Unit zabbix-server.service has finished shutting down
-- Defined-By: systemd
-- Support: https://support.oracle.com
--
-- Unit zabbix-server.service has finished shutting down.
Sep 02 13:53:49 Monitoreo systemd[1]: Starting Zabbix Server...
-- Subject: Unit zabbix-server.service has begun start-up
-- Defined-By: systemd
-- Support: https://support.oracle.com
--
-- Unit zabbix-server.service has begun starting up.
Sep 02 13:53:51 Monitoreo systemd[1]: zabbix-server.service: Can't open PID file /run/zabbix/zabbix_server.pid (yet?) after start: No such file or directory
Sep 02 13:53:51 Monitoreo systemd[1]: zabbix-server.service: Failed with result 'protocol'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://support.oracle.com
--
-- The unit zabbix-server.service has entered the 'failed' state with result 'protocol'.
Sep 02 13:53:51 Monitoreo systemd[1]: Failed to start Zabbix Server.
-- Subject: Unit zabbix-server.service has failed
-- Defined-By: systemd
-- Support: https://support.oracle.com
--
-- Unit zabbix-server.service has failed.
--
-- The result is failed.

[root@Monitoreo zabbix]#

DB is OK

Web GUI is OK

https://i.postimg.cc/dt3bGQ87/Zabbix.png

Thank you very much!!!

[tim.mooney]

Are there log messages in /var/log/zabbix/zabbix_server.log? If so, do they point to a particular problem?

You can ignore the message about

Sep 02 13:53:51 Monitoreo systemd[1]: zabbix-server.service: Can't open PID file /run/zabbix/zabbix_server.pid (yet?) after start: No such file or directory

That is a problem, but it's a very minor one and it's very common even on otherwise-working installs.

The other message is more likely related to the problem:

Sep 02 13:53:51 Monitoreo systemd[1]: zabbix-server.service: Failed with result 'protocol'.

I'm guessing that zabbix_serverd did start up and then exit, so hopefully there's more of a clue in the zabbix_server.log

[@ndres]

Hi.

You were right. :-)

[root@Monitoreo zabbix]# ll
total 27584
-rw-rw-r-- 1 zabbix zabbix 0 Sep 4 03:42 zabbix_agentd.log
-rw-rw-r-- 1 zabbix zabbix 7009 Sep 2 13:29 zabbix_agentd.log-20220904
-rw-rw-r-- 1 zabbix zabbix 8662967 Sep 4 20:52 zabbix_server.log
-rw-rw-r-- 1 zabbix zabbix 19381912 Sep 4 03:41 zabbix_server.log-20220904
[root@Monitoreo zabbix]# clear
[root@Monitoreo zabbix]# ll
total 27584
-rw-rw-r-- 1 zabbix zabbix 0 Sep 4 03:42 zabbix_agentd.log
-rw-rw-r-- 1 zabbix zabbix 7009 Sep 2 13:29 zabbix_agentd.log-20220904
-rw-rw-r-- 1 zabbix zabbix 8666395 Sep 4 20:52 zabbix_server.log
-rw-rw-r-- 1 zabbix zabbix 19381912 Sep 4 03:41 zabbix_server.log-20220904
[root@Monitoreo zabbix]# tail -f zabbix_server.log
74194:20220904:205247.397 using configuration file: /etc/zabbix/zabbix_server.conf
74194:20220904:205247.401 Zabbix supports only "utf8_bin,utf8mb3_bin,utf8mb4_bin" collation(s). Database "zabbix" has default collation "utf8mb4_general_ci"
74194:20220904:205247.408 character set name or collation name that is not supported by Zabbix found in 481 column(s) of database "zabbix"
74194:20220904:205247.408 only character set(s) "utf8,utf8mb3,utf8mb4" and corresponding collation(s) "utf8_bin,utf8mb3_bin,utf8mb4_bin" should be used in database
74194:20220904:205247.408
74194:20220904:205247.408 Unable to start Zabbix server due to unsupported MariaDB database version (10.03.32).
74194:20220904:205247.408 Must be at least (10.05.00).
74194:20220904:205247.408 Use of supported database version is highly recommended.
74194:20220904:205247.408 Override by setting AllowUnsupportedDBVersions=1 in Zabbix server configuration file at your own risk.
74194:20220904:205247.408
74227:20220904:205259.647 Starting Zabbix Server. Zabbix 6.2.2 (revision 35455866073).
74227:20220904:205259.647 ****** Enabled features ******
74227:20220904:205259.647 SNMP monitoring: YES
74227:20220904:205259.647 IPMI monitoring: YES
74227:20220904:205259.647 Web monitoring: YES
74227:20220904:205259.647 VMware monitoring: YES
74227:20220904:205259.647 SMTP authentication: YES
74227:20220904:205259.647 ODBC: YES
74227:20220904:205259.647 SSH support: YES
74227:20220904:205259.647 IPv6 support: YES
74227:20220904:205259.647 TLS support: YES
74227:20220904:205259.647 ******************************
74227:20220904:205259.647 using configuration file: /etc/zabbix/zabbix_server.conf
74227:20220904:205259.651 Zabbix supports only "utf8_bin,utf8mb3_bin,utf8mb4_bin" collation(s). Database "zabbix" has default collation "utf8mb4_general_ci"
74227:20220904:205259.657 character set name or collation name that is not supported by Zabbix found in 481 column(s) of database "zabbix"
74227:20220904:205259.657 only character set(s) "utf8,utf8mb3,utf8mb4" and corresponding collation(s) "utf8_bin,utf8mb3_bin,utf8mb4_bin" should be used in database
74227:20220904:205259.658
74227:20220904:205259.658 Unable to start Zabbix server due to unsupported MariaDB database version (10.03.32).
74227:20220904:205259.658 Must be at least (10.05.00).
74227:20220904:205259.658 Use of supported database version is highly recommended.
74227:20220904:205259.658 Override by setting AllowUnsupportedDBVersions=1 in Zabbix server configuration file at your own risk.
74227:20220904:205259.658
74237:20220904:205311.797 Starting Zabbix Server. Zabbix 6.2.2 (revision 35455866073).
74237:20220904:205311.797 ****** Enabled features ******
74237:20220904:205311.797 SNMP monitoring: YES
74237:20220904:205311.797 IPMI monitoring: YES
74237:20220904:205311.797 Web monitoring: YES
74237:20220904:205311.797 VMware monitoring: YES
74237:20220904:205311.797 SMTP authentication: YES
74237:20220904:205311.797 ODBC: YES
74237:20220904:205311.797 SSH support: YES
74237:20220904:205311.797 IPv6 support: YES
74237:20220904:205311.797 TLS support: YES
74237:20220904:205311.797 ******************************
74237:20220904:205311.797 using configuration file: /etc/zabbix/zabbix_server.conf
74237:20220904:205311.802 Zabbix supports only "utf8_bin,utf8mb3_bin,utf8mb4_bin" collation(s). Database "zabbix" has default collation "utf8mb4_general_ci"
74237:20220904:205311.809 character set name or collation name that is not supported by Zabbix found in 481 column(s) of database "zabbix"
74237:20220904:205311.809 only character set(s) "utf8,utf8mb3,utf8mb4" and corresponding collation(s) "utf8_bin,utf8mb3_bin,utf8mb4_bin" should be used in database
74237:20220904:205311.810
74237:20220904:205311.810 Unable to start Zabbix server due to unsupported MariaDB database version (10.03.32).
74237:20220904:205311.810 Must be at least (10.05.00).
74237:20220904:205311.810 Use of supported database version is highly recommended.
74237:20220904:205311.810 Override by setting AllowUnsupportedDBVersions=1 in Zabbix server configuration file at your own risk.
74237:20220904:205311.810
74241:20220904:205323.898 Starting Zabbix Server. Zabbix 6.2.2 (revision 35455866073).
74241:20220904:205323.898 ****** Enabled features ******
74241:20220904:205323.898 SNMP monitoring: YES
74241:20220904:205323.898 IPMI monitoring: YES
74241:20220904:205323.898 Web monitoring: YES
74241:20220904:205323.898 VMware monitoring: YES
74241:20220904:205323.898 SMTP authentication: YES
74241:20220904:205323.898 ODBC: YES
74241:20220904:205323.899 SSH support: YES
74241:20220904:205323.899 IPv6 support: YES
74241:20220904:205323.899 TLS support: YES
74241:20220904:205323.899 ******************************
74241:20220904:205323.899 using configuration file: /etc/zabbix/zabbix_server.conf
74241:20220904:205323.903 Zabbix supports only "utf8_bin,utf8mb3_bin,utf8mb4_bin" collation(s). Database "zabbix" has default collation "utf8mb4_general_ci"
74241:20220904:205323.910 character set name or collation name that is not supported by Zabbix found in 481 column(s) of database "zabbix"
74241:20220904:205323.910 only character set(s) "utf8,utf8mb3,utf8mb4" and corresponding collation(s) "utf8_bin,utf8mb3_bin,utf8mb4_bin" should be used in database
74241:20220904:205323.911
74241:20220904:205323.911 Unable to start Zabbix server due to unsupported MariaDB database version (10.03.32).
74241:20220904:205323.911 Must be at least (10.05.00).
74241:20220904:205323.911 Use of supported database version is highly recommended.
74241:20220904:205323.911 Override by setting AllowUnsupportedDBVersions=1 in Zabbix server configuration file at your own risk.
74241:20220904:205323.911
74245:20220904:205336.147 Starting Zabbix Server. Zabbix 6.2.2 (revision 35455866073).
74245:20220904:205336.147 ****** Enabled features ******
74245:20220904:205336.147 SNMP monitoring: YES
74245:20220904:205336.147 IPMI monitoring: YES
74245:20220904:205336.147 Web monitoring: YES
74245:20220904:205336.147 VMware monitoring: YES
74245:20220904:205336.147 SMTP authentication: YES
74245:20220904:205336.147 ODBC: YES
74245:20220904:205336.147 SSH support: YES
74245:20220904:205336.147 IPv6 support: YES
74245:20220904:205336.147 TLS support: YES
74245:20220904:205336.147 ******************************
74245:20220904:205336.147 using configuration file: /etc/zabbix/zabbix_server.conf
74245:20220904:205336.152 Zabbix supports only "utf8_bin,utf8mb3_bin,utf8mb4_bin" collation(s). Database "zabbix" has default collation "utf8mb4_general_ci"
74245:20220904:205336.158 character set name or collation name that is not supported by Zabbix found in 481 column(s) of database "zabbix"
74245:20220904:205336.158 only character set(s) "utf8,utf8mb3,utf8mb4" and corresponding collation(s) "utf8_bin,utf8mb3_bin,utf8mb4_bin" should be used in database
74245:20220904:205336.159
74245:20220904:205336.159 Unable to start Zabbix server due to unsupported MariaDB database version (10.03.32).
74245:20220904:205336.159 Must be at least (10.05.00).
74245:20220904:205336.159 Use of supported database version is highly recommended.
74245:20220904:205336.159 Override by setting AllowUnsupportedDBVersions=1 in Zabbix server configuration file at your own risk.
74245:20220904:205336.159
74249:20220904:205348.398 Starting Zabbix Server. Zabbix 6.2.2 (revision 35455866073).
74249:20220904:205348.398 ****** Enabled features ******
74249:20220904:205348.398 SNMP monitoring: YES
74249:20220904:205348.398 IPMI monitoring: YES
74249:20220904:205348.398 Web monitoring: YES
74249:20220904:205348.398 VMware monitoring: YES
74249:20220904:205348.398 SMTP authentication: YES
74249:20220904:205348.398 ODBC: YES
74249:20220904:205348.398 SSH support: YES
74249:20220904:205348.398 IPv6 support: YES
74249:20220904:205348.398 TLS support: YES
74249:20220904:205348.398 ******************************
74249:20220904:205348.398 using configuration file: /etc/zabbix/zabbix_server.conf
74249:20220904:205348.402 Zabbix supports only "utf8_bin,utf8mb3_bin,utf8mb4_bin" collation(s). Database "zabbix" has default collation "utf8mb4_general_ci"
74249:20220904:205348.410 character set name or collation name that is not supported by Zabbix found in 481 column(s) of database "zabbix"
74249:20220904:205348.410 only character set(s) "utf8,utf8mb3,utf8mb4" and corresponding collation(s) "utf8_bin,utf8mb3_bin,utf8mb4_bin" should be used in database
74249:20220904:205348.411
74249:20220904:205348.411 Unable to start Zabbix server due to unsupported MariaDB database version (10.03.32).
74249:20220904:205348.411 Must be at least (10.05.00).
74249:20220904:205348.411 Use of supported database version is highly recommended.
74249:20220904:205348.411 Override by setting AllowUnsupportedDBVersions=1 in Zabbix server configuration file at your own risk.
74249:20220904:205348.411
74253:20220904:205400.648 Starting Zabbix Server. Zabbix 6.2.2 (revision 35455866073).
74253:20220904:205400.648 ****** Enabled features ******
74253:20220904:205400.648 SNMP monitoring: YES
74253:20220904:205400.648 IPMI monitoring: YES
74253:20220904:205400.648 Web monitoring: YES
74253:20220904:205400.648 VMware monitoring: YES
74253:20220904:205400.648 SMTP authentication: YES
74253:20220904:205400.648 ODBC: YES
74253:20220904:205400.649 SSH support: YES
74253:20220904:205400.649 IPv6 support: YES
74253:20220904:205400.649 TLS support: YES
74253:20220904:205400.649 ******************************
74253:20220904:205400.649 using configuration file: /etc/zabbix/zabbix_server.conf
74253:20220904:205400.653 Zabbix supports only "utf8_bin,utf8mb3_bin,utf8mb4_bin" collation(s). Database "zabbix" has default collation "utf8mb4_general_ci"
74253:20220904:205400.660 character set name or collation name that is not supported by Zabbix found in 481 column(s) of database "zabbix"
74253:20220904:205400.660 only character set(s) "utf8,utf8mb3,utf8mb4" and corresponding collation(s) "utf8_bin,utf8mb3_bin,utf8mb4_bin" should be used in database
74253:20220904:205400.661
74253:20220904:205400.661 Unable to start Zabbix server due to unsupported MariaDB database version (10.03.32).
74253:20220904:205400.661 Must be at least (10.05.00).
74253:20220904:205400.661 Use of supported database version is highly recommended.
74253:20220904:205400.661 Override by setting AllowUnsupportedDBVersions=1 in Zabbix server configuration file at your own risk.
74253:20220904:205400.661
74257:20220904:205412.897 Starting Zabbix Server. Zabbix 6.2.2 (revision 35455866073).
74257:20220904:205412.898 ****** Enabled features ******
74257:20220904:205412.898 SNMP monitoring: YES
74257:20220904:205412.898 IPMI monitoring: YES
74257:20220904:205412.898 Web monitoring: YES
74257:20220904:205412.898 VMware monitoring: YES
74257:20220904:205412.898 SMTP authentication: YES
74257:20220904:205412.898 ODBC: YES
74257:20220904:205412.898 SSH support: YES
74257:20220904:205412.898 IPv6 support: YES
74257:20220904:205412.898 TLS support: YES
74257:20220904:205412.898 ******************************
74257:20220904:205412.898 using configuration file: /etc/zabbix/zabbix_server.conf
74257:20220904:205412.902 Zabbix supports only "utf8_bin,utf8mb3_bin,utf8mb4_bin" collation(s). Database "zabbix" has default collation "utf8mb4_general_ci"
74257:20220904:205412.909 character set name or collation name that is not supported by Zabbix found in 481 column(s) of database "zabbix"
74257:20220904:205412.909 only character set(s) "utf8,utf8mb3,utf8mb4" and corresponding collation(s) "utf8_bin,utf8mb3_bin,utf8mb4_bin" should be used in database
74257:20220904:205412.910
74257:20220904:205412.910 Unable to start Zabbix server due to unsupported MariaDB database version (10.03.32).
74257:20220904:205412.910 Must be at least (10.05.00).
74257:20220904:205412.910 Use of supported database version is highly recommended.
74257:20220904:205412.910 Override by setting AllowUnsupportedDBVersions=1 in Zabbix server configuration file at your own risk.
74257:20220904:205412.910
74262:20220904:205425.147 Starting Zabbix Server. Zabbix 6.2.2 (revision 35455866073).
74262:20220904:205425.147 ****** Enabled features ******
74262:20220904:205425.147 SNMP monitoring: YES
74262:20220904:205425.147 IPMI monitoring: YES
74262:20220904:205425.147 Web monitoring: YES
74262:20220904:205425.147 VMware monitoring: YES
74262:20220904:205425.147 SMTP authentication: YES
74262:20220904:205425.147 ODBC: YES
74262:20220904:205425.147 SSH support: YES
74262:20220904:205425.147 IPv6 support: YES
74262:20220904:205425.147 TLS support: YES
74262:20220904:205425.147 ******************************
74262:20220904:205425.147 using configuration file: /etc/zabbix/zabbix_server.conf
74262:20220904:205425.151 Zabbix supports only "utf8_bin,utf8mb3_bin,utf8mb4_bin" collation(s). Database "zabbix" has default collation "utf8mb4_general_ci"
74262:20220904:205425.158 character set name or collation name that is not supported by Zabbix found in 481 column(s) of database "zabbix"
74262:20220904:205425.158 only character set(s) "utf8,utf8mb3,utf8mb4" and corresponding collation(s) "utf8_bin,utf8mb3_bin,utf8mb4_bin" should be used in database
74262:20220904:205425.158
74262:20220904:205425.158 Unable to start Zabbix server due to unsupported MariaDB database version (10.03.32).
74262:20220904:205425.158 Must be at least (10.05.00).
74262:20220904:205425.158 Use of supported database version is highly recommended.
74262:20220904:205425.158 Override by setting AllowUnsupportedDBVersions=1 in Zabbix server configuration file at your own risk.
74262:20220904:205425.158
74266:20220904:205437.397 Starting Zabbix Server. Zabbix 6.2.2 (revision 35455866073).
74266:20220904:205437.397 ****** Enabled features ******
74266:20220904:205437.397 SNMP monitoring: YES
74266:20220904:205437.397 IPMI monitoring: YES
74266:20220904:205437.397 Web monitoring: YES
74266:20220904:205437.397 VMware monitoring: YES
74266:20220904:205437.397 SMTP authentication: YES
74266:20220904:205437.397 ODBC: YES
74266:20220904:205437.397 SSH support: YES
74266:20220904:205437.397 IPv6 support: YES
74266:20220904:205437.397 TLS support: YES
74266:20220904:205437.397 ******************************
74266:20220904:205437.397 using configuration file: /etc/zabbix/zabbix_server.conf
74266:20220904:205437.401 Zabbix supports only "utf8_bin,utf8mb3_bin,utf8mb4_bin" collation(s). Database "zabbix" has default collation "utf8mb4_general_ci"
74266:20220904:205437.408 character set name or collation name that is not supported by Zabbix found in 481 column(s) of database "zabbix"
74266:20220904:205437.408 only character set(s) "utf8,utf8mb3,utf8mb4" and corresponding collation(s) "utf8_bin,utf8mb3_bin,utf8mb4_bin" should be used in database
74266:20220904:205437.409
74266:20220904:205437.409 Unable to start Zabbix server due to unsupported MariaDB database version (10.03.32).
74266:20220904:205437.409 Must be at least (10.05.00).
74266:20220904:205437.409 Use of supported database version is highly recommended.
74266:20220904:205437.409 Override by setting AllowUnsupportedDBVersions=1 in Zabbix server configuration file at your own risk.
74266:20220904:205437.409
74270:20220904:205449.647 Starting Zabbix Server. Zabbix 6.2.2 (revision 35455866073).
74270:20220904:205449.648 ****** Enabled features ******
74270:20220904:205449.648 SNMP monitoring: YES
74270:20220904:205449.648 IPMI monitoring: YES
74270:20220904:205449.648 Web monitoring: YES
74270:20220904:205449.648 VMware monitoring: YES
74270:20220904:205449.648 SMTP authentication: YES
74270:20220904:205449.648 ODBC: YES
74270:20220904:205449.648 SSH support: YES
74270:20220904:205449.648 IPv6 support: YES
74270:20220904:205449.648 TLS support: YES
74270:20220904:205449.648 ******************************
74270:20220904:205449.648 using configuration file: /etc/zabbix/zabbix_server.conf
74270:20220904:205449.652 Zabbix supports only "utf8_bin,utf8mb3_bin,utf8mb4_bin" collation(s). Database "zabbix" has default collation "utf8mb4_general_ci"
74270:20220904:205449.659 character set name or collation name that is not supported by Zabbix found in 481 column(s) of database "zabbix"
74270:20220904:205449.659 only character set(s) "utf8,utf8mb3,utf8mb4" and corresponding collation(s) "utf8_bin,utf8mb3_bin,utf8mb4_bin" should be used in database
74270:20220904:205449.660
74270:20220904:205449.660 Unable to start Zabbix server due to unsupported MariaDB database version (10.03.32).
74270:20220904:205449.660 Must be at least (10.05.00).
74270:20220904:205449.660 Use of supported database version is highly recommended.
74270:20220904:205449.660 Override by setting AllowUnsupportedDBVersions=1 in Zabbix server configuration file at your own risk.
74270:20220904:205449.660
^C
[root@Monitoreo zabbix]#

[Atsushi]

74194:20220904:205247.401 Zabbix supports only "utf8_bin,utf8mb3_bin,utf8mb4_bin" collation(s). Database "zabbix" has default collation "utf8mb4_general_ci"
74194:20220904:205247.408 character set name or collation name that is not supported by Zabbix found in 481 column(s) of database "zabbix"
74194:20220904:205247.408 only character set(s) "utf8,utf8mb3,utf8mb4" and corresponding collation(s) "utf8_bin,utf8mb3_bin,utf8mb4_bin" should be used in database

Check the character encoding and collation you are using in your database. Are the character encoding and collation supported by Zabbix?

https://www.zabbix.com/documentation/current/en/manual/appendix/install/db_scripts

https://www.zabbix.com/documentation/current/en/manual/appendix/install/db_charset_coll

74194:20220904:205247.408 Unable to start Zabbix server due to unsupported MariaDB database version (10.03.32).
74194:20220904:205247.408 Must be at least (10.05.00).

Use a version of MariaDB supported by Zabbix.

https://www.zabbix.com/documentation/current/en/manual/installation/requirements#third-party-external-surrounding-software

[@ndres]

Hi.

Everything is working now:




Thank you very much!!!

[Carlos_oliveira11]

Job for zabbix-server.service failed because the service did not take the steps required by its unit configuration.
See "systemctl status zabbix-server.service" and "journalctl -xe" for details.

I have the same error, but I could not fix, could you help me, I use this zabbix long time ago, but now this problem start happen 4 days ago

[Rohitmahajan701]

How did you fix the issue ? I have been facing the same issue .

[Mikaelisson]

There was the same problem with me, when looking at the compatible logs I validated that the mariaDB version was not, I reinstalled the previous version and it started working again