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

Duplicate entry key 'trends_uint.PRIMARY' when stopping Zabbix server

XMLWordPrintable

    • S25-W36/37, S25-W38/39, S25-W40/41
    • 1

      Following can occur in rare scenarios if all trends has synced but some new values arrived afterwards:

      3027875:20250902:133910.496 query [txnlev:1] [insert into trends_uint (itemid,clock,num,value_min,value_avg,value_max) values (1,1756807200,1,0,0,0);.]
      ...
      3027875:20250902:134014.276 query [txnlev:1] [insert into trends_uint (itemid,clock,num,value_min,value_avg,value_max) values (1,1756810800,1,0,0,0);.]
      ...
      3027861:20250902:134023.404 query [txnlev:1] [insert into trends_uint (itemid,clock,num,value_min,value_avg,value_max) values (1,1756810800,1,0,0,0);.]
      3027861:20250902:134023.404 [Z3008] query failed due to primary key constraint: [1062] Duplicate entry '1-1756810800' for key 'trends_uint.PRIMARY'
      3027861:20250902:134023.404 query [insert into trends_uint (itemid,clock,num,value_min,value_avg,value_max) values (1,1756810800,1,0,0,0);.] failed, setting transaction as failed
      

            vso Vladislavs Sokurenko
            vso Vladislavs Sokurenko
            Team A
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - Not Specified
                Not Specified
                Logged:
                Time Spent - 6.5h
                6.5h