Project

General

Profile

Actions
Copy link

Bug #10478

closed

Error on inserting into nodecompliance table

Added by Nicolas CHARLES almost 8 years ago. Updated about 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
 #1

Updated by François ARMAND almost 8 years ago

  • Tracker changed from Bug to Architecture
Actions
Copy link
 #2

Updated by François ARMAND almost 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
 #3

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 4.1.0 to 4.1.1
Actions
Copy link
 #4

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 4.1.1 to 4.1.2
Actions
Copy link
 #5

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 4.1.2 to 4.1.3
Actions
Copy link
 #6

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 4.1.3 to 4.1.4
Actions
Copy link
 #7

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 4.1.4 to 4.1.5
Actions
Copy link
 #8

Updated by Alexis Mousset over 7 years ago

  • Target version changed from 4.1.5 to 4.1.6
Actions
Copy link
 #9

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 4.1.6 to 4.1.7
Actions
Copy link
 #10

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 4.1.7 to 4.1.8
Actions
Copy link
 #11

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 4.1.8 to 4.1.9
Actions
Copy link
 #12

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 4.1.9 to 4.1.10
Actions
Copy link
 #13

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 4.1.10 to 4.1.11
Actions
Copy link
 #14

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.1.11 to 4.1.12
Actions
Copy link
 #15

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.1.12 to 4.1.13
Actions
Copy link
 #16

Updated by Nicolas CHARLES over 6 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
 #17

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.1.13 to 4.1.14
Actions
Copy link
 #18

Updated by Benoît PECCATTE over 6 years ago

  • Target version changed from 4.1.14 to 4.1.15
Actions
Copy link
 #19

Updated by Vincent MEMBRÉ about 6 years ago

  • Target version changed from 4.1.15 to 4.1.16
Actions
Copy link
 #20

Updated by Vincent MEMBRÉ about 6 years ago

  • Target version changed from 4.1.16 to 4.1.17
Actions
Copy link
 #21

Updated by Vincent MEMBRÉ about 6 years ago

  • Target version changed from 4.1.17 to 4.1.18
Actions
Copy link
 #22

Updated by Vincent MEMBRÉ almost 6 years ago

  • Target version changed from 4.1.18 to 4.1.19
Actions
Copy link
 #23

Updated by Alexis Mousset almost 6 years ago

  • Target version changed from 4.1.19 to 4.1.20
Actions
Copy link
 #24

Updated by François ARMAND almost 6 years ago

  • Target version changed from 4.1.20 to 4.1.21
Actions
Copy link
 #25

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 4.1.21 to 4.1.22
Actions
Copy link
 #26

Updated by Benoît PECCATTE over 5 years ago

  • Target version changed from 4.1.22 to 5.0.10
Actions
Copy link
 #27

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 5.0.10 to 5.0.11
Actions
Copy link
 #28

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 5.0.11 to 5.0.12
Actions
Copy link
 #29

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 5.0.12 to 5.0.13
Actions
Copy link
 #30

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 5.0.13 to 5.0.14
Actions
Copy link
 #31

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 5.0.14 to 5.0.15
Actions
Copy link
 #32

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 5.0.15 to 5.0.16
Actions
Copy link
 #33

Updated by Alexis Mousset almost 5 years ago

  • Target version changed from 5.0.16 to 5.0.17
Actions
Copy link
 #34

Updated by François ARMAND over 4 years ago

  • Related to Bug #13427: On error on nodecompliance SQL, logs are huge added
Actions
Copy link
 #35

Updated by François ARMAND over 4 years ago

  • Related to Bug #15021: When receiving lots of reports, while load is high, an error occurs on node compliance historisation added
Actions
Copy link
 #36

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.17 to 5.0.18
Actions
Copy link
 #37

Updated by Benoît PECCATTE over 4 years ago

  • Target version changed from 5.0.18 to 6.2.0~beta1
Actions
Copy link
 #38

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 6.2.0~beta1 to 6.2.0~rc1
Actions
Copy link
 #39

Updated by François ARMAND about 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 about 4 years ago

  • Status changed from New to Resolved

Duplicate of #18188

Actions
Copy link
 #41

Updated by François ARMAND about 4 years ago

  • Is duplicate of Bug #18188: Error log about duplicates entries when saving node compliance levels added
Actions
Copy link
 #42

Updated by François ARMAND about 4 years ago

  • Fix check set to Checked
Actions
Copy link

Also available in: Atom PDF