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

Failed update from 3.4 to 4.0

XMLWordPrintable

    • Icon: Incident report Incident report
    • Resolution: Won't fix
    • Icon: Trivial Trivial
    • None
    • 4.0.0
    • None
    • Ubuntu 16.04

      Steps to reproduce:

      1. Update from 3.4 to 4.0

      Result:

       3874:20181006:205914.902 database upgrade failed
        3900:20181006:205925.143 Starting Zabbix Server. Zabbix 4.0.0 (revision 85308).
        3900:20181006:205925.143 ****** Enabled features ******
        3900:20181006:205925.143 SNMP monitoring:           YES
        3900:20181006:205925.143 IPMI monitoring:           YES
        3900:20181006:205925.144 Web monitoring:            YES
        3900:20181006:205925.145 VMware monitoring:         YES
        3900:20181006:205925.145 SMTP authentication:       YES
        3900:20181006:205925.145 Jabber notifications:      YES
        3900:20181006:205925.145 Ez Texting notifications:  YES
        3900:20181006:205925.145 ODBC:                      YES
        3900:20181006:205925.145 SSH2 support:              YES
        3900:20181006:205925.145 IPv6 support:              YES
        3900:20181006:205925.145 TLS support:               YES
        3900:20181006:205925.145 ******************************
        3900:20181006:205925.145 using configuration file: /etc/zabbix/zabbix_server.conf
        3900:20181006:205925.152 current database version (mandatory/optional): 03050061/03050061
        3900:20181006:205925.152 required mandatory version: 04000000
        3900:20181006:205925.152 starting automatic database upgrade
        3900:20181006:205925.153 [Z3005] query failed: [1060] Duplicate column name 'verify_host' [alter table `items` add `verify_host` integer default '0' not null]
        3900:20181006:205925.153 database upgrade failed
      

            Unassigned Unassigned
            dexsternn Dmitry
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: