Project

General

Profile

Actions

Bug #6381

closed

File /var/log/rudder/{compliance/non-compliant-reports.log, core/rudder-webapp.log} are not correctly rotated

Added by Nicolas CHARLES about 9 years ago. Updated over 8 years ago.

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

Description

This file is not correctly rotated, as on the systems, it is empty, and the file /var/log/rudder/compliance/non-compliant-reports.log.1 contains the most up to date reports (but is 250Mo big, with 2 months of logs)

Oddly, on my test system, it was correctly rotated 26, 27, 28 January,and rotation broke on 29 January.

Happens on Debian and SLES and Centos.

It is the same thing for /var/log/rudder/core/rudder-webapp.log.


Subtasks 1 (0 open1 closed)

Bug #6385: Remove /var/log/rudder/compliance/non-compliant-reports.log rotation from logrotateReleasedNicolas CHARLES2015-03-11Actions

Related issues 5 (2 open3 closed)

Related to Rudder - Bug #5453: Incomplete logrotate configurationRejectedMatthieu CERDA2014-09-01Actions
Related to Rudder - User story #6384: Clean log rotation & compression letting Java aloneNew2015-03-11Actions
Related to Rudder - Bug #4433: Log rotation problems due to bad post-rotate scriptRejectedBenoît PECCATTE2014-01-31Actions
Related to Rudder - User story #6719: Suppress webapp logs after some timeRejectedFrançois ARMANDActions
Related to Rudder - Bug #8418: Configuration files do not get updated when user has modified the stock onesNewActions
Actions

Also available in: Atom PDF