[ZBX-1070] postgresql unique key constraint violation causes server to stop Created: 2009 Oct 05  Updated: 2017 May 30  Resolved: 2010 Mar 09

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Server (S)
Affects Version/s: 1.6.4
Fix Version/s: 1.8.2, 1.9.0 (alpha)

Type: Incident report Priority: Major
Reporter: svrki Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Linux 2.6.27-gentoo-r8 #1 SMP Fri Mar 13 04:38:14 CET 2009 x86_64 Intel(R) Xeon(R) CPU E5405 @ 2.00GHz GenuineIntel GNU/Linux

Issue Links:
Duplicate
duplicates ZBX-18 PostgreSQL monitoring [Watchdog] Closed

 Description   

from my log:
20946:20091005:160035 [Z3005] Query failed: [0] PGRES_FATAL_ERROR:ERROR: duplicate key value violates unique constraint "trends_pkey"
[insert into trends (clock,itemid,num,value_min,value_avg,value_max) values (1254751200,22170,1,965.478261,965.478261,965.478261)]
20946:20091005:160035 [Z3005] Query failed: [0] PGRES_FATAL_ERROR:ERROR: current transaction is aborted, commands ignored until end of transaction block
[update items set nextcheck=1254751227,prevvalue=lastvalue,prevorgvalue='4569905065.000000',lastvalue='965.478261',lastclock=1254751222 where itemid=22170]
20946:20091005:160035 [Z3005] Query failed: [0] PGRES_FATAL_ERROR:ERROR: current transaction is aborted, commands ignored until end of transaction block
[select distinct function,parameter,itemid,lastvalue from functions where itemid=22170]
20347:20091005:160036 One child process died. Exiting ...

 Comments   
Comment by Aleksandrs Saveljevs [ 2010 Mar 09 ]

Fixed in pre-1.8.2 in r10669.

Generated at Fri May 23 07:51:27 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.