Actions
Bug #3655
closed
Non compliant reports flood the Rudder logs on a new installation
Pull Request:
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
Updated by Vincent MEMBRÉ over 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
Pull request here : https://github.com/Normation/rudder/pull/232
Updated by Vincent MEMBRÉ over 11 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset 4c9139d496ba5cf6b2a66e6d23198f46e2814042.
Updated by Nicolas PERRON over 11 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
Updated by Nicolas PERRON over 11 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
Updated by Nicolas PERRON over 11 years ago
- Status changed from Pending release to Released
Updated by Nicolas PERRON over 11 years ago
This bug has been fixed in Rudder 2.5.5, which was released today.
Check out:
- The release announcement: http://www.rudder-project.org/pipermail/rudder-announce/2013-July/000040.html
- The full ChangeLog: http://www.rudder-project.org/foswiki/bin/view/System/Documentation:ChangeLog25
- Download information: http://www.rudder-project.org/foswiki/Download/
Updated by Benoît PECCATTE almost 10 years ago
- Category changed from 39 to System integration
Actions