Project

General

Profile

Bug #10912

Duration of logrotate for /var/log/rudder/ is too long making /var/log too big

Added by François ARMAND about 1 year ago. Updated 6 months ago.

Status:
Released
Priority:
N/A
Category:
System integration
Target version:
Target version (plugin):
Severity:
Major - prevents use of part of Rudder | no simple workaround
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Priority:
76
Tags:

Description

For now, we can't configure the duration of the retention of logs in /var/log/rudder which managed by logrotate, itself managed by Rudder (the one managed by logback can be changed in the logback.xml file not managed by rudder itself).

The correct solution would be to add a new parameter to make the duration configurable.

See also #10899 for the architecture constraints on that ticket (can impact the version on which we will be able to change the behavior)

For the record, workaround is to have a defaut value of 30 days for log rotation, and if the Parameter log_duration is defined, then the defined value will be used to define rotation (as a number of days)


Related issues

Related to Rudder - Architecture #10899: Allow to update system variables in technique without changing webapp codeIn progress

Associated revisions

Revision 6ba1df9a (diff)
Added by Benoît PECCATTE 8 months ago

Fixes #10912: Duration of logrotate for /var/log/rudder/ is too long making /var/log too big

History

#1 Updated by François ARMAND about 1 year ago

  • Related to Architecture #10899: Allow to update system variables in technique without changing webapp code added

#2 Updated by François ARMAND about 1 year ago

  • Description updated (diff)

#3 Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 3.1.21 to 3.1.22

#4 Updated by Benoît PECCATTE about 1 year ago

  • Severity set to Major - prevents use of part of Rudder | no simple workaround
  • User visibility set to Operational - other Techniques | Technique editor | Rudder settings
  • Priority changed from 0 to 36

#5 Updated by Benoît PECCATTE about 1 year ago

  • Tags set to Sponsored
  • Priority changed from 36 to 61

#6 Updated by Benoît PECCATTE about 1 year ago

  • Assignee set to Benoît PECCATTE

We can use a global parameter to set this value.
rudder agent can then use the variable, affect a default value and generate the logrotate template.

#7 Updated by Benoît PECCATTE about 1 year ago

  • Priority changed from 61 to 77

#8 Updated by Vincent MEMBRÉ 12 months ago

  • Target version changed from 3.1.22 to 3.1.23
  • Priority changed from 77 to 76

#9 Updated by Vincent MEMBRÉ 11 months ago

  • Target version changed from 3.1.23 to 3.1.24
  • Priority changed from 76 to 75

#10 Updated by Vincent MEMBRÉ 9 months ago

  • Target version changed from 3.1.24 to 3.1.25
  • Priority changed from 75 to 73

#11 Updated by Benoît PECCATTE 9 months ago

  • Priority changed from 73 to 72

#12 Updated by Benoît PECCATTE 9 months ago

  • Status changed from New to In progress

#13 Updated by Benoît PECCATTE 9 months ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Benoît PECCATTE to Alexis MOUSSET
  • Pull Request set to https://github.com/Normation/rudder-techniques/pull/1216

#14 Updated by Alexis MOUSSET 8 months ago

  • Assignee changed from Alexis MOUSSET to Benoît PECCATTE
  • Priority changed from 72 to 78

#15 Updated by Benoît PECCATTE 8 months ago

  • Assignee changed from Benoît PECCATTE to Alexis MOUSSET

#16 Updated by Benoît PECCATTE 8 months ago

  • Status changed from Pending technical review to Pending release

#17 Updated by Vincent MEMBRÉ 7 months ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.1.25, 4.1.9 and 4.2.3 which were released today.

#18 Updated by Nicolas CHARLES 6 months ago

  • Description updated (diff)
  • Priority changed from 78 to 76

Also available in: Atom PDF