Ad Widget

Collapse

[Z3005] query failed: [1054] Unknown column 'ha_failover_delay' in 'field list'

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Majkelus
    Junior Member
    • May 2022
    • 3

    #1

    [Z3005] query failed: [1054] Unknown column 'ha_failover_delay' in 'field list'

    Hi
    I have a problem after migrating from Zabbix server version 5 on Linux CentOS 7 to Zabbix server version 6.0.3 on Linux CentOS 8.
    I import database to Zabbix server v 6.0.3 and after that I have an error like this below:
    1147473:20220525:064457.336 Starting Zabbix Server. Zabbix 6.0.3 (revision 506e2b51e2).
    1147473:20220525:064457.336 ****** Enabled features ******
    1147473:20220525:064457.336 SNMP monitoring: YES
    1147473:20220525:064457.336 IPMI monitoring: YES
    1147473:20220525:064457.336 Web monitoring: YES
    1147473:20220525:064457.336 VMware monitoring: YES
    1147473:20220525:064457.336 SMTP authentication: YES
    1147473:20220525:064457.336 ODBC: YES
    1147473:20220525:064457.336 SSH support: YES
    1147473:20220525:064457.336 IPv6 support: YES
    1147473:20220525:064457.336 TLS support: YES
    1147473:20220525:064457.336 ******************************
    1147473:20220525:064457.336 using configuration file: /etc/zabbix/zabbix_server.conf
    1147473:20220525:064457.363 current database version (mandatory/optional): 06000000/06000004
    1147473:20220525:064457.363 required mandatory version: 06000000
    1147474:20220525:064457.371 starting HA manager
    1147474:20220525:064457.373 [Z3005] query failed: [1054] Unknown column 'ha_failover_delay' in 'field list' [select ha_failover_delay,auditlog_enabled from config]
    1147473:20220525:064457.373 cannot start server: database error
    1147474:20220525:064457.374 HA manager has been stopped
    1147473:20220525:064457.376 Zabbix Server stopped. Zabbix 6.0.3 (revision 506e2b51e2).

    Could you help me with this problem
    Thanks in advance.
  • Atsushi
    Senior Member
    • Aug 2013
    • 2028

    #2
    How did you perform the database upgrade? If you manually change the database version, you will not be able to start Zabbix 6.0 on that database. If you dumped and restored the database for Zabbix 5.0, connect the Zabbix 6.0 server to that database and the upgrade process will be automatically executed to the database for 6.0.

    Comment

    • Majkelus
      Junior Member
      • May 2022
      • 3

      #3
      Hi
      Thank you for the answer. I change it manually.
      Once more I restore database from Zabbix 5.0. Now I had this error:
      2098:20220525:094755.803 Starting Zabbix Server. Zabbix 6.0.3 (revision 506e2b51e2).
      2098:20220525:094755.803 ****** Enabled features ******
      2098:20220525:094755.803 SNMP monitoring: YES
      2098:20220525:094755.803 IPMI monitoring: YES
      2098:20220525:094755.803 Web monitoring: YES
      2098:20220525:094755.803 VMware monitoring: YES
      2098:20220525:094755.803 SMTP authentication: YES
      2098:20220525:094755.803 ODBC: YES
      2098:20220525:094755.803 SSH support: YES
      2098:20220525:094755.803 IPv6 support: YES
      2098:20220525:094755.803 TLS support: YES
      2098:20220525:094755.803 ******************************
      2098:20220525:094755.803 using configuration file: /etc/zabbix/zabbix_server.conf
      2098:20220525:094755.834 current database version (mandatory/optional): 05010001/05010001
      2098:20220525:094755.834 required mandatory version: 06000000
      2098:20220525:094755.834 starting automatic database upgrade
      2098:20220525:094755.835 [Z3005] query failed: [1406] Data too long for column 'lang' at row 1 [update users set lang='default',theme='default' where alias='guest']
      2098:20220525:094755.835 database upgrade failed

      I exacute this command:
      alter table users modify column lang varchar(32);

      and now have this error:
      2819:20220525:102413.802 Starting Zabbix Server. Zabbix 6.0.3 (revision 506e2b51e2).
      2819:20220525:102413.803 ****** Enabled features ******
      2819:20220525:102413.803 SNMP monitoring: YES
      2819:20220525:102413.803 IPMI monitoring: YES
      2819:20220525:102413.803 Web monitoring: YES
      2819:20220525:102413.803 VMware monitoring: YES
      2819:20220525:102413.803 SMTP authentication: YES
      2819:20220525:102413.803 ODBC: YES
      2819:20220525:102413.803 SSH support: YES
      2819:20220525:102413.803 IPv6 support: YES
      2819:20220525:102413.803 TLS support: YES
      2819:20220525:102413.803 ******************************
      2819:20220525:102413.803 using configuration file: /etc/zabbix/zabbix_server.conf
      2819:20220525:102413.831 current database version (mandatory/optional): 05010036/05010036
      2819:20220525:102413.831 required mandatory version: 06000000
      2819:20220525:102413.831 starting automatic database upgrade
      2819:20220525:102413.832 [Z3005] query failed: [1050] Table 'trigger_queue' already exists [create table trigger_queue (
      `objectid` bigint unsigned not null,
      `type` integer default '0' not null,
      `clock` integer default '0' not null,
      `ns` integer default '0' not null
      ) engine=innodb]
      2819:20220525:102413.832 database upgrade failed

      Thanks in advance.

      Comment

      • Majkelus
        Junior Member
        • May 2022
        • 3

        #4
        Hi
        I drop several tables and everything upgrade to version 6. Thank you for the tip to don't change database manualy.
        Best Regards

        Comment

        • carnotan
          Junior Member
          • Mar 2025
          • 7

          #5
          INFO: Server RHEL 8.2, DB MySQL 8.0.34, PHP 8.0.


          I'm having exactly the same problem but upgrading from 5.0.x to 7.0.x. I strictly follow the instructions in https://www.zabbix.com/documentation.../packages/rhel but when it comes the time to start the zabbix-server, it fails with this message:

          125290:20250724:102228.863 Starting Zabbix Server. Zabbix 7.0.17 (revision 77c670937ef).
          125290:20250724:102228.863 ****** Enabled features ******
          125290:20250724:102228.863 SNMP monitoring: YES
          125290:20250724:102228.863 IPMI monitoring: YES
          125290:20250724:102228.863 Web monitoring: YES
          125290:20250724:102228.863 VMware monitoring: YES
          125290:20250724:102228.863 SMTP authentication: YES
          125290:20250724:102228.863 ODBC: YES
          125290:20250724:102228.863 SSH support: YES
          125290:20250724:102228.863 IPv6 support: YES
          125290:20250724:102228.863 TLS support: YES
          125290:20250724:102228.863 ******************************
          125290:20250724:102228.863 using configuration file: /etc/zabbix/zabbix_server.conf
          125290:20250724:102228.877 current database version (mandatory/optional): 05000000/05000007
          125290:20250724:102228.877 required mandatory version: 07000000
          125290:20250724:102228.877 mandatory patches were found
          125290:20250724:102228.878 [Z3005] query failed: [1054] Unknown column 'ha_failover_delay' in 'field list' [select unix_timestamp(),ha_failover_delay from config]
          125290:20250724:102228.878 cannot retrieve database time

          Can anyone provide any help?

          Comment

          • ppretorius
            Junior Member
            • Dec 2025
            • 4

            #6
            Originally posted by carnotan
            INFO: Server RHEL 8.2, DB MySQL 8.0.34, PHP 8.0.


            I'm having exactly the same problem but upgrading from 5.0.x to 7.0.x. I strictly follow the instructions in https://www.zabbix.com/documentation.../packages/rhel but when it comes the time to start the zabbix-server, it fails with this message:

            125290:20250724:102228.863 Starting Zabbix Server. Zabbix 7.0.17 (revision 77c670937ef).
            125290:20250724:102228.863 ****** Enabled features ******
            125290:20250724:102228.863 SNMP monitoring: YES
            125290:20250724:102228.863 IPMI monitoring: YES
            125290:20250724:102228.863 Web monitoring: YES
            125290:20250724:102228.863 VMware monitoring: YES
            125290:20250724:102228.863 SMTP authentication: YES
            125290:20250724:102228.863 ODBC: YES
            125290:20250724:102228.863 SSH support: YES
            125290:20250724:102228.863 IPv6 support: YES
            125290:20250724:102228.863 TLS support: YES
            125290:20250724:102228.863 ******************************
            125290:20250724:102228.863 using configuration file: /etc/zabbix/zabbix_server.conf
            125290:20250724:102228.877 current database version (mandatory/optional): 05000000/05000007
            125290:20250724:102228.877 required mandatory version: 07000000
            125290:20250724:102228.877 mandatory patches were found
            125290:20250724:102228.878 [Z3005] query failed: [1054] Unknown column 'ha_failover_delay' in 'field list' [select unix_timestamp(),ha_failover_delay from config]
            125290:20250724:102228.878 cannot retrieve database time

            Can anyone provide any help?

            Hi Carnotan - Did you ever get this sorted ? Im having the same trouble trying to go from 5.4 to 7.4

            Comment


            • carnotan
              carnotan commented
              Editing a comment
              I am probably way too late to answer (sorry, I missed this reply) but in my case it was the same as with other people. Some tables are there that I cannot reasonably explain how they ended up there, but they are not part of Zabbix 5, so they can simply be dropped .I restored a previous backup which doesn't have that problem and then proceeded with the upgrade.
          • tim.mooney
            Senior Member
            • Dec 2012
            • 1427

            #7
            Lots of people have reported the exact same issue over the past couple years.

            This thread might help, but it doesn't completely answer what the issue is: https://www.zabbix.com/forum/zabbix-...%E2%86%927-2-4

            Comment

            • ppretorius
              Junior Member
              • Dec 2025
              • 4

              #8
              So in my case, i found that previous attempts at upgrade had left the data in a bit of state. I restored a fresh backup of the DB and started again - That resolved the initial error i had Unknown column 'ha_failover_delay', but then i ran into a bunch of other Data related issues (Dropping / Adding foreign keys) manual intervention, managed to get me through. Good luck to anyone else trying to get from 5 to 7

              Comment

              Working...