Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-11279

Upgrade Database fails from 3.0 to 3.2

XMLWordPrintable

    • Icon: Incident report Incident report
    • Resolution: Duplicate
    • Icon: Major Major
    • None
    • 3.2.0
    • Server (S)
    • Upgrade Database fails from 3.0 to 3.2

      Hello,

      i have consider the upgrade instucions by 3.2
      when i start the zabbix server i become by the log the folling error

      34040:20160928:202257.867 ****** Enabled features ******
      34040:20160928:202257.867 SNMP monitoring: YES
      34040:20160928:202257.868 IPMI monitoring: YES
      34040:20160928:202257.868 Web monitoring: YES
      34040:20160928:202257.868 VMware monitoring: YES
      34040:20160928:202257.868 SMTP authentication: YES
      34040:20160928:202257.868 Jabber notifications: YES
      34040:20160928:202257.868 Ez Texting notifications: YES
      34040:20160928:202257.868 ODBC: YES
      34040:20160928:202257.868 SSH2 support: YES
      34040:20160928:202257.868 IPv6 support: YES
      34040:20160928:202257.868 TLS support: YES
      34040:20160928:202257.868 ******************************
      34040:20160928:202257.868 using configuration file: /etc/zabbix/zabbix_server.conf
      34040:20160928:202257.878 current database version (mandatory/optional): 03010005/03010005
      34040:20160928:202257.878 required mandatory version: 03020000
      34040:20160928:202257.878 starting automatic database upgrade
      34040:20160928:202257.879 [Z3005] query failed: [1050] Table 'trigger_tag' already exists [create $
      triggertagid bigint unsigned not null,
      triggerid bigint unsigned not null,
      tag varchar(255) default '' not null,
      value varchar(255) default '' not null,
      primary key (triggertagid)
      ) engine=innodb]
      34040:20160928:202257.879 database upgrade failed

            Unassigned Unassigned
            pierrehinz Pierre Hinz
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: