Ad Widget

Collapse

database upgrade failed after upgrade to 4.4.7

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • pacholik
    Junior Member
    • Apr 2020
    • 2

    #1

    database upgrade failed after upgrade to 4.4.7

    I have trouble after upgrading Zabbix with PostgreSQL db.

    The frontend says

    Database error
    The frontend does not match Zabbix database. Current database version (mandatory/optional): 3010005/3010005. Required mandatory version: 4040000. Contact your system administrator.
    zabbix_server.log:
    Code:
      ...
      9957:20200401:150456.139 using configuration file: /etc/zabbix/zabbix_server.conf
      9957:20200401:150456.154 current database version (mandatory/optional): 03010005/03010005
      9957:20200401:150456.154 required mandatory version: 04040000
      9957:20200401:150456.154 optional patches were found
      9957:20200401:150456.154 starting automatic database upgrade
      9957:20200401:150456.155 [Z3005] query failed: [0] PGRES_FATAL_ERROR:ERROR:  relation "trigger_tag" already exists
     [create table trigger_tag (
    triggertagid bigint not null,
    triggerid bigint not null,
    tag varchar(255) default '' not null,
    value varchar(255) default '' not null,
    primary key (triggertagid)
    )]
      9957:20200401:150456.155 database upgrade failed
    How shall I proceed?
  • tim.mooney
    Senior Member
    • Dec 2012
    • 1427

    #2
    Report this as a bug in the Zabbix bugtracker.

    Comment

    • pacholik
      Junior Member
      • Apr 2020
      • 2

      #3
      Ok, I will.

      But what do I do with the broken db?

      Comment

      • tim.mooney
        Senior Member
        • Dec 2012
        • 1427

        #4
        Downgrade the versions of the Zabbix packages you have installed back to the version you were using prior to the upgrade, and before starting up the zabbix-server package, restore your database using the backup of it that you made right before you upgraded. In other words, restore your server environment to the previous version, until a solution for the upgrade issue is available and you can try the upgrade again.

        You may also want to do something to block any alerts that may be generated when you restart your zabbix-server. Depending on how your triggers are configured, it may think that many things in your environment are down, since it won't have collected any data about them for potentially hours or days.

        Comment

        Working...