Ad Widget

Collapse

Проблема при обновлении с 5.2.6 до 5.4

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • teploint
    Junior Member
    • Jun 2021
    • 1

    #1

    Проблема при обновлении с 5.2.6 до 5.4

    debian 10.9
    mysql Ver 15.1 Distrib 10.5.10-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2
    nginx version: nginx/1.14.2

    Весь процесс обновление проходит отлично, но при старте выдает следующие

    HTML Code:
    26717:20210601:164107.088 [Z3005] query failed: [1091] Can't DROP FOREIGN KEY `c_items_3`; check that it exists [alter table items drop foreign key c_items_3]
    26717:20210601:164107.088 database upgrade failed
    completed 22% of database upgrade 26720:20210601:164117.172 Starting Zabbix Server. Zabbix 5.4.0 (revision 5059e20a75).
    26720:20210601:164117.172 ****** Enabled features ******
    26720:20210601:164117.172 SNMP monitoring: YES
    26720:20210601:164117.172 IPMI monitoring: YES
    26720:20210601:164117.172 Web monitoring: YES
    26720:20210601:164117.172 VMware monitoring: YES
    26720:20210601:164117.172 SMTP authentication: YES
    26720:20210601:164117.172 ODBC: YES
    26720:20210601:164117.172 SSH support: YES
    26720:20210601:164117.173 IPv6 support: YES
    26720:20210601:164117.173 TLS support: YES
    26720:20210601:164117.173 ******************************
    26720:20210601:164117.173 using configuration file: /etc/zabbix/zabbix_server.conf
    26720:20210601:164117.177 current database version (mandatory/optional): 05030044/05030044
    26720:20210601:164117.177 required mandatory version: 05040000
    26720:20210601:164117.177 starting automatic database upgrade
    26720:20210601:164117.178 [Z3005] query failed: [1091] Can't DROP FOREIGN KEY `c_items_3`; check that it exists [alter table items drop foreign key c_items_3]
    26720:20210601:164117.178 database upgrade failed
    26724:20210601:164127.419 Starting Zabbix Server. Zabbix 5.4.0 (revision 5059e20a75).
  • wins
    Senior Member
    • Sep 2014
    • 307

    #2
    Апну тему, поймал +\- тотже баг
    Апгрейд с 5.2.6 - > 5.4.1 (archlinux, postgresql +timescaledb 2.3)

    HTML Code:
    Jun 19 09:36:04 oxygen postgres[12251]: 2021-06-19 09:36:04.700 MSK [12251] ERROR: column "dashboard_pageid" of relation "widget" already exists
    Jun 19 09:36:04 oxygen postgres[12251]: 2021-06-19 09:36:04.700 MSK [12251] STATEMENT: alter table widget add dashboard_pageid bigint
    Jun 19 09:36:04 oxygen zabbix_server[12246]: [Z3005] query failed: [0] PGRES_FATAL_ERROR:ERROR: column "dashboard_pageid" of relation "widget" already exists
    [alter table widget add dashboard_pageid bigint]
    Попробовал обмануть судьбу:
    HTML Code:
    zabbix=# CREATE TABLE dashboard_page (
    dashboard_pageid bigint NOT NULL,
    dashboardid bigint NOT NULL,
    name varchar(255) DEFAULT '' NOT NULL,
    display_period integer DEFAULT '0' NOT NULL,
    sortorder integer DEFAULT '0' NOT NULL,
    PRIMARY KEY (dashboard_pageid)
    );
    CREATE TABLE
    zabbix=# CREATE INDEX dashboard_page_1 ON dashboard_page (dashboardid);
    CREATE INDEX
    zabbix=# ALTER TABLE ONLY dashboard_page ADD CONSTRAINT c_dashboard_page_1 FOREIGN KEY (dashboardid) REFERENCES dashboard (dashboardid) ON DELETE CASCADE;
    ALTER TABLE
    zabbix=# ALTER TABLE ONLY widget ADD dashboard_pageid bigint;
    ALTER TABLE
    zabbix=# ALTER TABLE ONLY widget ADD CONSTRAINT c_widget_1 FOREIGN KEY (dashboard_pageid) REFERENCES dashboard_page (dashboard_pageid) ON DELETE CASCADE;
    ALTER TABLE
    Не помогло:

    HTML Code:
    Jun 19 09:34:22 oxygen zabbix_server[11699]: [Z3005] query failed: [0] PGRES_FATAL_ERROR:ERROR: relation "dashboard_page" already exists
    [create table dashboard_page (
    dashboard_pageid bigint not null,
    dashboardid bigint not null,
    name varchar(255) default '' not null,
    display_period integer default '0' not null,
    sortorder integer default '0' not null,
    primary key (dashboard_pageid)
    )]






    Comment

    • wins
      Senior Member
      • Sep 2014
      • 307

      #3
      воркараундом в моем случае являлось:
      запустить апдейт бд, подождать ошибки, далее
      ALTER TABLE ONLY widget ADD CONSTRAINT c_widget_1 FOREIGN KEY (dashboard_pageid) REFERENCES dashboard_page (dashboard_pageid) ON DELETE CASCADE;
      и далее опять штатный апдейт.
      колхоз конечно, но сработало :\
      Last edited by wins; 12-07-2021, 22:40.

      Comment

      Working...