Project

General

Profile

Actions
Copy link

Bug #3363

closed

When we restart Jetty, the webapp logs are overflowed with non compliance reports

Added by Nicolas CHARLES almost 12 years ago. Updated almost 10 years ago.

Status:
Rejected
Priority:
1 (highest)
Assignee:
Jonathan CLARKE
Category:
System integration
Target version:
2.5.6
Pull Request:
https://github.com/Normation/rudder-p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

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 ?

Related issues 1 (0 open — 1 closed)

Related to Rudder - Bug #3655: Non compliant reports flood the Rudder logs on a new installationReleasedFrançois ARMAND2013-06-18Actions
Actions
Copy link
 #1

Updated by Nicolas PERRON over 11 years ago

  • Target version changed from 2.5.1 to 2.5.2
Actions
Copy link
 #2

Updated by Nicolas PERRON over 11 years ago

  • Target version changed from 2.5.2 to 2.5.3
Actions
Copy link
 #3

Updated by Nicolas PERRON over 11 years ago

  • Target version changed from 2.5.3 to 2.5.4
Actions
Copy link
 #4

Updated by Nicolas PERRON over 11 years ago

  • Target version changed from 2.5.4 to 2.5.5
Actions
Copy link
 #5

Updated by Vincent MEMBRÉ over 11 years ago

  • 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

https://github.com/Normation/rudder-packages/pull/68

I put another pull request here also to correct the initial logback.xml

Actions
Copy link
 #6

Updated by Nicolas PERRON over 11 years ago

  • Target version changed from 2.5.5 to 2.5.6
Actions
Copy link
 #7

Updated by Jonathan CLARKE over 11 years ago

  • 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.

Actions
Copy link
 #8

Updated by Benoît PECCATTE almost 10 years ago

  • Category changed from 39 to System integration
Actions
Copy link

Also available in: Atom PDF