Ad Widget

Collapse

Zabbix Upgrade 5.4 - 7.4

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • ppretorius
    Junior Member
    • Dec 2025
    • 4

    #1

    Zabbix Upgrade 5.4 - 7.4

    HI guys

    Im stuck in a loop ... Hoping someone can shed some light?

    Trying to do an upgrade of an old Zabbix that we have. Annoyingly when i start the server service, the server logs show : Unknown column 'ha_failover_delay'

    2708:20251201:140308.778 current database version (mandatory/optional): 05050077/05050077
    2708:20251201:140308.779 required mandatory version: 07040000
    2708:20251201:140308.780 mandatory patches were found
    2708:20251201:140308.784 [Z3005] query failed: [1054] Unknown column 'ha_failover_delay' in 'SELECT' [select unix_timestamp(),ha_failover_delay from config]
    2708:20251201:140308.784 cannot retrieve database time
    2708:20251201:140308.785 Zabbix Server stopped. Zabbix 7.4.5 (revision c525822dce0).

    So i try to add it ... and then i get ...

    2735:20251201:142645.792 starting automatic database upgrade
    2735:20251201:142645.803 [Z3005] query failed: [1060] Duplicate column name 'ha_failover_delay' [alter table `config` add `ha_failover_delay` varchar(32) default '1m' not null]
    2735:20251201:142645.805 database upgrade failed on patch 05050078, exiting in 10 seconds
    2735:20251201:142655.806 Zabbix Server stopped. Zabbix 7.4.5 (revision c525822dce0).​

    Seem to be going round in circles and im not sure how to get out this?

    Any help would be much appreciated - Thank you
  • cyber
    Senior Member
    Zabbix Certified SpecialistZabbix Certified Professional
    • Dec 2006
    • 4806

    #2
    How did you start.. prepared full v7.4 new server, then inserted data from old DB and then tried to start server?
    If you upgrade, you have to start with OLD DB, be it on new DB engine or whatnot... but it should enver be prepared with NEW DB schema... thats what causes you to run into issues with adding columns from patches etc...

    Comment

    • ppretorius
      Junior Member
      • Dec 2025
      • 4

      #3
      I think the issue came about from a previous upgrade attempt failure which left the backend in a bit of a state. In the end i restored back to the original 5.4 DB and then i got past the issue. I was met with other issues regarding foreign keys etc in and around v6, but with some manual intervention i was able to make it through to 7.4

      Thank you! And good luck to whoever tries the same upgrade path.

      Comment

      Working...