Project

General

Profile

Actions
Copy link

Bug #13427

closed

On error on nodecompliance SQL, logs are huge

Added by François ARMAND about 6 years ago. Updated over 2 years ago.

Status:
Released
Priority:
N/A
Assignee:
François ARMAND
Category:
Performance and scalability
Target version:
4.1.15
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Very Small
Priority:
0
Name check:
Fix check:
Regression:

Description

One user reported an error on insertion for "nodecompliance" table. That resulted in the full row content being logged, and that content is huge (it is the JSON serialisation of detailled compliance).

We must only log the error without details, and only add details for debug level (or trace).

The problematic insert was:

[2018-09-07 02:22:56] ERROR report - Error when saving node compliances: Batch entry 0 insert into nodecompliance (nodeid, runtimestamp, endoflife, runanalysis, summary, details)
values (‘9c8bab57-d6e2-475b-99f9-df2e8e0521cf’, ‘2018-09-07 02:22:32+02’, ‘2018-09-07 02:32:32+02’, ’{

...
huge json
...

}’) was aborted: ERROR: permission denied for relation nodecompliance  Call getNextException to see other errors in the batch.

Related issues 2 (0 open — 2 closed)

Related to Rudder - Bug #13429: Make nodecompliance ttl data RejectedActions
Related to Rudder - Bug #10478: Error on inserting into nodecompliance tableResolvedFrançois ARMANDActions
Actions
Copy link
 #1

Updated by François ARMAND about 6 years ago

  • Description updated (diff)
Actions
Copy link
 #2

Updated by François ARMAND about 6 years ago

  • Target version set to 4.1.15
Actions
Copy link
 #3

Updated by François ARMAND about 6 years ago

  • Status changed from New to In progress
Actions
Copy link
 #4

Updated by François ARMAND about 6 years ago

  • Related to Bug #13429: Make nodecompliance ttl data added
Actions
Copy link
 #5

Updated by François ARMAND about 6 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/2028
Actions
Copy link
 #6

Updated by Rudder Quality Assistant about 6 years ago

  • Assignee changed from Nicolas CHARLES to François ARMAND
Actions
Copy link
 #7

Updated by François ARMAND about 6 years ago

  • Status changed from Pending technical review to Pending release
Actions
Copy link
 #8

Updated by Vincent MEMBRÉ about 6 years ago

  • Status changed from Pending release to Released
  • Priority changed from 113 to 112
This bug has been fixed in Rudder 4.1.15, 4.3.5 and 5.0.1 which were released today. 
Changelog
 Changelog
 Changelog
Actions
Copy link
 #9

Updated by François ARMAND over 4 years ago

  • Related to Bug #10478: Error on inserting into nodecompliance table added
Actions
Copy link
 #10

Updated by Alexis Mousset over 2 years ago

  • Priority changed from 112 to 0
Actions
Copy link

Also available in: Atom PDF