Actions
Bug #18188
closedError log about duplicates entries when saving node compliance levels
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Reviewed
Fix check:
Checked
Regression:
Description
[2020-09-09 14:14:02+0000] INFO policy.generation.timing - Policy generation succeeded in: 10 s [2020-09-09 14:14:02+0000] INFO policy.generation.manager - Flag file '/opt/rudder/etc/policy-update-running' successfully removed [2020-09-09 14:14:02+0000] INFO policy.generation.manager - Flag file '/opt/rudder/etc/trigger-policy-generation' successfully removed [2020-09-09 14:14:02+0000] INFO policy.generation.manager - Successful policy update '16' [started 2020-09-09 14:13:51 - ended 2020-09-09 14:14:02] [2020-09-09 14:14:12+0000] INFO compliance - [metrics] global compliance (number of components): 12 [p:0 s:1 r:1 e:0 u:0 m:4 nr:4 na:2 rd:0 c:0 ana:0 nc:0 ae:0 bpm:0] [2020-09-09 14:16:13+0000] ERROR report - SystemError: Error when saving node compliances:; cause was: java.sql.BatchUpdateException: Batch entry 0 insert into nodecompliancelevels (nodeid,runtimestamp,ruleid,directiveid,pending,success,r... [2020-09-09 14:16:13+0000] ERROR application - Error when executing [Store Agent Run Times] scheduler task started at 2020-09-09T14:16:13Z, ended at 2020-09-09T14:16:13Z. <- SystemError: Error when saving node compliances:; cause was: java.sql.BatchUpdateException: Batch entry 0 insert into nodecompliancelevels (nodeid,runtimestamp,ruleid,directiveid,pending,success,repaired,error,unexpected,missing,noanswer,notapplicable,reportsdisabled,compliant,auditnotapplicable,noncompliant,auditerror,badpolicymode) values ( 'root','2020-09-09 14:05:30+00'::timestamp with time zone,'server-roles','server-roles-directive',0,24,0,0,0,0,0,1,0,0,0,0,0,0 ) was aborted: ERROR: duplicate key value violates unique constraint "nodecompliancelevels_pkey" Detail: Key (nodeid, runtimestamp, ruleid, directiveid)=(root, 2020-09-09 14:05:30+00, server-roles, server-roles-directive) already exists. Call getNextException to see other errors in the batch. -> [2020-09-09 14:16:13+0000] INFO inventory-processing - Watch new inventory file 'server-root.ocs' with signature available: process.
Updated by Nicolas CHARLES almost 4 years ago
- Related to Bug #17410: Error log about duplicates entries when saving node compliance levels added
Updated by Nicolas CHARLES almost 4 years ago
- Translation missing: en.field_tag_list set to Sponsored
Updated by François ARMAND almost 4 years ago
- Status changed from New to In progress
- Assignee set to François ARMAND
Updated by François ARMAND almost 4 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder/pull/3221
Updated by Vincent MEMBRÉ almost 4 years ago
- Target version changed from 6.1.5 to 6.1.6
Updated by François ARMAND almost 4 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|b8aadbad2134ad53b69cfc623f6dbbbd8a9712c5.
Updated by Alexis Mousset almost 4 years ago
- Name check changed from To do to Reviewed
Updated by Alexis Mousset almost 4 years ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ almost 4 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.1.6 and 6.2.0~beta1 which were released today.
Updated by François ARMAND almost 4 years ago
- Has duplicate Bug #10478: Error on inserting into nodecompliance table added
Updated by Nicolas Ecarnot over 3 years ago
In 6.2.0, I'm seeing this :
Dec 30 11:58:08 sit-conf-prd01 rudder[report]: [ERROR] SystemError: Error when saving node compliances:; cause was: java.sql.BatchUpdateException: Batch entry 0 insert into nodecompliancelevels (nodeid,runtimestamp,ruleid,directiveid,pending,sDec 30 11:58:08 sit-conf-prd01 rudder[scheduled.job]: [ERROR] Error when executing [Store Agent Run Times] scheduler task started at 2020-12-30T11:58:08+01:00, ended at 2020-12-30T11:58:08+01:00. <- SystemError: Error when saving node complianc values ( 'a2743fbe-8f74-42fd-a2b5-c09366e27452','2020-12-30 11:52:30+01','65485923-9e4b-4b42-88c1-3b2b1039822b','7a136103-9313-4d9e-9b43-aa57e3ebbfa2',0,1,0,0,0,0,0,1,0,0,0,0,0,0 ) was aborted: ERREUR: la valeur d'une clé dupliquée rompt la co Detail: La clé « (nodeid, runtimestamp, ruleid, directiveid)=(a2743fbe-8f74-42fd-a2b5-c09366e27452, 2020-12-30 11:52:30+01, 65485923-9e4b-4b42-88c1-3b2b1039822b, 7a136103-9313-4d9e-9b43-aa57e3ebbfa2) » existe déjà. Call getNextException to s ->
I suppose there's still something to fix?
Updated by François ARMAND over 3 years ago
- Related to Bug #18814: Error log about duplicates entries when saving node compliance levels added
Updated by François ARMAND over 3 years ago
@Nicolas: it seems that the localisation breaks something. I've open that ticket: https://issues.rudder.io/issues/18814
Actions