Project

General

Profile

Actions

Bug #13427

closed

On error on nodecompliance SQL, logs are huge

Added by François ARMAND over 4 years ago. Updated 8 months ago.

Status:
Released
Priority:
N/A
Category:
Performance and scalability
Target version:
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
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 open2 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 #1

Updated by François ARMAND over 4 years ago

  • Description updated (diff)
Actions #2

Updated by François ARMAND over 4 years ago

  • Target version set to 4.1.15
Actions #3

Updated by François ARMAND over 4 years ago

  • Status changed from New to In progress
Actions #4

Updated by François ARMAND over 4 years ago

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

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

Updated by Rudder Quality Assistant over 4 years ago

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

Updated by François ARMAND over 4 years ago

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

Updated by Vincent MEMBRÉ over 4 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 #9

Updated by François ARMAND almost 3 years ago

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

Updated by Alexis Mousset 8 months ago

  • Priority changed from 112 to 0
Actions

Also available in: Atom PDF