Project

General

Profile

Actions

Bug #3655

closed

Non compliant reports flood the Rudder logs on a new installation

Added by Vincent MEMBRÉ almost 11 years ago. Updated about 9 years ago.

Status:
Released
Priority:
2
Category:
System integration
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

Following #3363, logback.xml should be updated to not write non compliant reports in /var/log/rudder/webapp/*.log


Related issues 1 (0 open1 closed)

Related to Rudder - Bug #3363: When we restart Jetty, the webapp logs are overflowed with non compliance reportsRejectedJonathan CLARKE2013-03-19Actions
Actions #1

Updated by Vincent MEMBRÉ almost 11 years ago

  • Status changed from New to Pending technical review
  • Assignee changed from Vincent MEMBRÉ to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder/pull/232
Actions #2

Updated by Vincent MEMBRÉ almost 11 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions #3

Updated by Nicolas PERRON over 10 years ago

  • Subject changed from change logback.xml in to prevent log flooded with non compliant reports on new installation to Non compliant reports flood the Rudde logs on a new installation
Actions #4

Updated by Nicolas PERRON over 10 years ago

  • Subject changed from Non compliant reports flood the Rudde logs on a new installation to Non compliant reports flood the Rudder logs on a new installation
Actions #5

Updated by Nicolas PERRON over 10 years ago

  • Status changed from Pending release to Released
Actions #6

Updated by Nicolas PERRON over 10 years ago

This bug has been fixed in Rudder 2.5.5, which was released today.
Check out:

Actions #7

Updated by Benoît PECCATTE about 9 years ago

  • Category changed from 39 to System integration
Actions

Also available in: Atom PDF