Project

General

Custom queries

Profile

Actions
Copy link

Bug #10478

closed

Error on inserting into nodecompliance table

Added by Nicolas CHARLES about 8 years ago. Updated over 4 years ago.

Status:
Resolved
Priority:
N/A
Assignee:
François ARMAND
Category:
Web - Compliance & node report
Target version:
6.2.0~rc1
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
29
Name check:
Fix check:
Checked
Regression:

Description

In my postgresql logs, I get sometimes errors like

ERROR:  duplicate key value violates unique constraint "nodecompliance_pkey" 
DETAIL:  Key (nodeid, runtimestamp)=(747ebdce-2769-4d04-a7ae-0ff6ace8086a, 2017-03-21 00:27:19+00) already exists.
STATEMENT:  insert into nodecompliance (nodeid, runtimestamp, endoflife, runanalysis, summary, details)
                               values ($1, $2, $3, $4, $5, $6)

ERROR:  duplicate key value violates unique constraint "nodecompliance_pkey" 
DETAIL:  Key (nodeid, runtimestamp)=(root, 2017-03-21 15:30:53+00) already exists.
STATEMENT:  insert into nodecompliance (nodeid, runtimestamp, endoflife, runanalysis, summary, details)
                               values ($1, $2, $3, $4, $5, $6)

There is 0 logs in the webapp about that

Related issues 3 (0 open — 3 closed)

Related to Rudder - Bug #13427: On error on nodecompliance SQL, logs are hugeReleasedFrançois ARMANDActions
Related to Rudder - Bug #15021: When receiving lots of reports, while load is high, an error occurs on node compliance historisation RejectedActions
Is duplicate of Rudder - Bug #18188: Error log about duplicates entries when saving node compliance levelsReleasedNicolas CHARLESActions
Actions
Copy link
 #2

Updated by François ARMAND about 8 years ago

We are switching that ticket to architecture because this is not a feature for now, so an user should not even know about that.

Actions
Copy link
 #16

Updated by Nicolas CHARLES almost 7 years ago

If all reports are duplicated (even end run), we get an error

[2018-07-10 12:50:32] ERROR report - Error when saving node compliances: Batch entry 0 insert into nodecompliance (nodeid, runtimestamp, endoflife, runanalysis, summary, details)
 values ('817e987d-db8a-4368-8dc4-6bf061775f96', '2018-07-10 12:50:19+00'::timestamp with time zone, '2018-07-10 13:00:19+00'::timestamp with time zone, '{
  "run":{
    "type":"ComputeCompliance",
    "expectedConfigId":"20180710-124310-f0870b1e",
    "runConfigId":"20180710-124310-f0870b1e" 
  },
  "status":{
    "status":"success" 

 was aborted: ERROR: duplicate key value violates unique constraint "nodecompliance_pkey" 
  Detail: Key (nodeid, runtimestamp)=(817e987d-db8a-4368-8dc4-6bf061775f96, 2018-07-10 12:50:19+00) already exists.  Call getNextException to see other errors in the batch.

entries are correctly unique in reportsexecution

Actions
Copy link
 #39

Updated by François ARMAND over 4 years ago

  • Tracker changed from Architecture to Bug
  • Severity set to Minor - inconvenience | misleading | easy workaround
  • User visibility set to Operational - other Techniques | Rudder settings | Plugins
  • Priority set to 29

This still happens and cause unending problems with users understanding.

Actions
Copy link
 #40

Updated by François ARMAND over 4 years ago

  • Status changed from New to Resolved

Duplicate of #18188

Actions
Copy link

Also available in: Atom PDF