Ad Widget

Collapse

Zabbix migration from 5.0 to 6.0 TimescaleDB issues

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • maxi4
    Junior Member
    • Feb 2024
    • 2

    #1

    Zabbix migration from 5.0 to 6.0 TimescaleDB issues

    Some time after migration from Zabbix 5.0 to Zabbix 6.0 with TimescaleDB i have a lot off errors in zabbix-server log like :

    1762:20240219:112321.726 [Z3008] query failed due to primary key constraint: [0] PGRES_FATAL_ERROR:ERROR: duplicate key value violates unique constraint "11699_1096_history_uint_pkey"
    DETAIL: Key (itemid, clock, ns)=(211837, 1708337100, 17) already exists.

    1762:20240219:112321.727 skipped 1 duplicates
    1762:20240219:112321.737 [Z3008] query failed due to primary key constraint: [0] PGRES_FATAL_ERROR:ERROR: duplicate key value violates unique constraint "11699_1096_history_uint_pkey"
    DETAIL: Key (itemid, clock, ns)=(211837, 1708337102, 27) already exists.

    1762:20240219:112321.738 skipped 1 duplicates
    1762:20240219:112321.739 [Z3008] query failed due to primary key constraint: [0] PGRES_FATAL_ERROR:ERROR: duplicate key value violates unique constraint "11699_1096_history_uint_pkey"
    DETAIL: Key (itemid, clock, ns)=(211837, 1708337102, 28) already exists.

    1762:20240219:112321.740 skipped 1 duplicates
    1762:20240219:112321.740 [Z3008] query failed due to primary key constraint: [0] PGRES_FATAL_ERROR:ERROR: duplicate key value violates unique constraint "11699_1096_history_uint_pkey"
    DETAIL: Key (itemid, clock, ns)=(211837, 1708337102, 29) already exists.

    1762:20240219:112321.741 skipped 1 duplicates
    1762:20240219:112321.742 [Z3008] query failed due to primary key constraint: [0] PGRES_FATAL_ERROR:ERROR: duplicate key value violates unique constraint "11699_1096_history_uint_pkey"
    DETAIL: Key (itemid, clock, ns)=(211837, 1708337102, 30) already exists.

    1762:20240219:112321.743 skipped 1 duplicates
    1762:20240219:112321.743 [Z3008] query failed due to primary key constraint: [0] PGRES_FATAL_ERROR:ERROR: duplicate key value violates unique constraint "11699_1096_history_uint_pkey"
    DETAIL: Key (itemid, clock, ns)=(211837, 1708337102, 31) already exists.

    I tried to truncate tables history* but nothing

    What i can do to solve this issue?
  • maxi4
    Junior Member
    • Feb 2024
    • 2

    #2
    Any suggestions ?

    Comment

    Working...