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.
Category:
System integration
Description
Following #3363, logback.xml should be updated to not write non compliant reports in /var/log/rudder/webapp/*.log
- 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
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
- 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
- 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
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.5.5, which was released today.
Check out:
- Category changed from 39 to System integration
Also available in: Atom
PDF
Updated by 
Updated by Nicolas PERRON 
Updated by