Bug #3363
closed
When we restart Jetty, the webapp logs are overflowed with non compliance reports
Added by Nicolas CHARLES over 11 years ago.
Updated over 9 years ago.
Category:
System integration
Description
Upon starting Jetty on a prod system, the /var/rudder/log/webapp/2013_03_19.stderrout.log is filled with literally thousands of lines of non compliance reports, tracing back to start of march
It makes it really difficult to look for something in the logs, especially if we are not sure of what we should look for or see..
Could these message live in another log file please ?
- Target version changed from 2.5.1 to 2.5.2
- Target version changed from 2.5.2 to 2.5.3
- Target version changed from 2.5.3 to 2.5.4
- Target version changed from 2.5.4 to 2.5.5
- Status changed from New to Pending technical review
- Assignee set to Jonathan CLARKE
- Pull Request set to https://github.com/Normation/rudder-packages/pull/68
- Target version changed from 2.5.5 to 2.5.6
- Status changed from Pending technical review to Rejected
I'm afraid that I am not comfortable with this change.
The code involved to change some XML is very complex, and introducing this in a stable version does not seem worth the result: all this will gain is excluding some logs from the webapp logs. This is not a major problem, because a) they have been in that file for a while now, and b) if you need to read the logs without those lines, then use "grep -v", and c) the webapp logs aren't really easily read by anyone except the developers anyway.
The original problem has been fixed for new installs (see #3655), so this only affects users upgrading from older versions (and "grep -v" still works fine ;) ).
I am therefore not going to merge it. Sorry Vincent, I know you invested effort to make this possible.
- Category changed from 39 to System integration
Also available in: Atom
PDF
Updated by Nicolas PERRON 
Updated by 
Updated by Jonathan CLARKE 
Updated by