Ad Widget

Collapse

Unable to start after upgrade "The Zabbix DB version does not match requirements."

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • pinkycz
    Junior Member
    • Mar 2021
    • 4

    #1

    Unable to start after upgrade "The Zabbix DB version does not match requirements."

    Hi,
    run an update of 5.4 Zabbix installation to 6.2 today and now stuck at the start with following error.

    Code:
    Database error[LIST][*]The Zabbix database version does not match current requirements. Your database version: 6010048. Required version: 6010097. Please contact your system administrator.[/LIST]
    Zabbix server does not start
    Code:
     Unit zabbix-server.service has begun starting up.
    Jun 13 15:43:02 appliance zabbix_server[1257]: zabbix_server [1257]: unknown parameter "AllowUnsupportedDBVersion" in>
    Jun 13 15:43:02 appliance systemd[1]: zabbix-server.service: Control process exited, code=exited status=1
    Jun 13 15:43:02 appliance systemd[1]: zabbix-server.service: Failed with result 'exit-code'.
    -- Subject: Unit failed
    -- Defined-By: systemd
    -- Support: https://access.redhat.com/support
    --
    -- The unit zabbix-server.service has entered the 'failed' state with result 'exit-code'.
    Jun 13 15:43:02 appliance systemd[1]: Failed to start Zabbix Server.
    -- Subject: Unit zabbix-server.service has failed
    -- Defined-By: systemd
    and the server log shows following error -apparently the DB upgrade script fails?
    Code:
     1951:20220613:150742.488 Starting Zabbix Server. Zabbix 6.2.0rc1 (revision f82e225b617).
    1951:20220613:150742.489 ****** Enabled features ******
    1951:20220613:150742.489 SNMP monitoring: YES
    1951:20220613:150742.489 IPMI monitoring: YES
    1951:20220613:150742.489 Web monitoring: YES
    1951:20220613:150742.489 VMware monitoring: YES
    1951:20220613:150742.489 SMTP authentication: YES
    1951:20220613:150742.489 ODBC: YES
    1951:20220613:150742.489 SSH support: YES
    1951:20220613:150742.489 IPv6 support: YES
    1951:20220613:150742.489 TLS support: YES
    1951:20220613:150742.489 ******************************
    1951:20220613:150742.489 using configuration file: /etc/zabbix/zabbix_server.conf
    1951:20220613:150742.518 current database version (mandatory/optional): 06010048/06010048
    1951:20220613:150742.518 required mandatory version: 06010097
    1951:20220613:150742.518 starting automatic database upgrade
    1951:20220613:150742.519 [Z3005] query failed: [1419] You do not have the SUPER privilege and binary logging is enab
    led (you *might* want to use the less safe log_bin_trust_function_creators variable) [create trigger hosts_insert afte
    r insert on hosts
    for each row
    insert into changelog (object,objectid,operation,clock)
    values (1,new.hostid,1,unix_timestamp())]
    1951:20220613:150742.519 database upgrade failed
    I have tried setting global variable log_bin_trust_routine_creators to 1 in MySQL to no avail.

    Any ideas how to complete database upgrade and get to required DB version??
  • tim.mooney
    Senior Member
    • Dec 2012
    • 1427

    #2
    Originally posted by pinkycz
    Hi,
    run an update of 5.4 Zabbix installation to 6.2 today and now stuck at the start with following error.

    Code:
     1951:20220613:150742.488 Starting Zabbix Server. Zabbix 6.2.0rc1 (revision f82e225b617).
    1951:20220613:150742.489 ****** Enabled features ******
    1951:20220613:150742.489 SNMP monitoring: YES
    1951:20220613:150742.489 IPMI monitoring: YES
    1951:20220613:150742.489 Web monitoring: YES
    1951:20220613:150742.489 VMware monitoring: YES
    1951:20220613:150742.489 SMTP authentication: YES
    1951:20220613:150742.489 ODBC: YES
    1951:20220613:150742.489 SSH support: YES
    1951:20220613:150742.489 IPv6 support: YES
    1951:20220613:150742.489 TLS support: YES
    1951:20220613:150742.489 ******************************
    1951:20220613:150742.489 using configuration file: /etc/zabbix/zabbix_server.conf
    1951:20220613:150742.518 current database version (mandatory/optional): 06010048/06010048
    1951:20220613:150742.518 required mandatory version: 06010097
    1951:20220613:150742.518 starting automatic database upgrade
    1951:20220613:150742.519 [Z3005] query failed: [1419] You do not have the SUPER privilege and binary logging is enab
    led (you *might* want to use the less safe log_bin_trust_function_creators variable) [create trigger hosts_insert afte
    r insert on hosts
    for each row
    insert into changelog (object,objectid,operation,clock)
    values (1,new.hostid,1,unix_timestamp())]
    1951:20220613:150742.519 database upgrade failed

    Any ideas how to complete database upgrade and get to required DB version??
    6.2.0 has not been released. You've installed a release candidate (rc), which is typically better than "beta", but unless you really, really need some functionality from 6.2.0, my general recommendation is to wait until there have been a few point releases (6.2.1, 6.2.2, 6.2.3, etc.) in a series before you upgrade to it. Otherwise, you're going to run into all of the early problems with a new version.

    Regarding your specific issue, MySQL/MariaDB is telling you what the problem is in the error message:

    "You do not have the SUPER privilege and binary logging is enabled"

    You may want to review the release notes and "known issues" for 6.2.0, as it seems at least some versions of MySQL/MariaDB/Percona may require that you give your database user additional privileges OR set other configuration settings that avoid the need for additional privileges.

    What database server and exact version are you using?

    Comment

    • Atsushi
      Senior Member
      • Aug 2013
      • 2028

      #3
      If you are using MySQL 8.0, the workaround is to set the following variables as the root user on MySQL.

      Code:
      SET GLOBAL log_bin_trust_function_creators = 1;
      For better settings, I think you need to provide the type and version of database server you are using and the official instructions from Zabbix.

      Comment

      • pinkycz
        Junior Member
        • Mar 2021
        • 4

        #4
        Running CentOS 8 with MySQL 8.0.26 , upgrade attempted to 6.2rc1 indeed. I did try to setup "log bin trust func creators" as MySQL global variable to no avail (mentioned above), zabbix-server restart triggers database upgrade process that then fails with the same error, so that did not help unfortunately and at that point I hit the wall.
        I've rolled back our machine to previous snapshot and will try again, this time probably just to official release 6.0 or 6.1 - suspect tim.mooney is right that even the rc1 can have some problems which I won't be able to overcome all with my knowledge of Linux.

        Comment

        • cyber
          Senior Member
          Zabbix Certified SpecialistZabbix Certified Professional
          • Dec 2006
          • 4807

          #5
          There is no 6.1.. current latest is 6.0.5

          Comment

          • pinkycz
            Junior Member
            • Mar 2021
            • 4

            #6
            6.1.2 release in repo?


            Comment

            • cyber
              Senior Member
              Zabbix Certified SpecialistZabbix Certified Professional
              • Dec 2006
              • 4807

              #7
              That is actually 6.2 RC... :P

              Zabbix uses version number ending with even numbers for actual version and odd numbers in development... You can find there 5.5, which is actually 6.0 dev and rc versions etc.. or 5.3, which is 5.4 in dev stages..

              Comment

              • pinkycz
                Junior Member
                • Mar 2021
                • 4

                #8
                Oh, thanks for clarifying! Learning every day (again)!

                Comment

                Working...