Bug #3868: The files written by java in /var/log/rudder/core/*.log are still empty after a logrotate - Rudder - Issue Tracker

Custom queries

8.1 beta
Bugs triage
My TR
Need technical review
Open bugs (all)
Open bugs (UI - UX)
Open UX defects (all)
Opened by users

Actions

Copy link

Bug #3868

closed

The files written by java in /var/log/rudder/core/*.log are still empty after a logrotate

Added by Nicolas PERRON over 10 years ago. Updated about 9 years ago.

Status:

Rejected

Priority:

Assignee:

Category:

System integration

Target version:

2.10.13

Pull Request:

Severity:

UX impact:

User visibility:

Effort required:

Priority:

Name check:

Fix check:

Regression:

Description

After a logrotate of the files present in /var/log/rudder/core/, they are naver filled again. Normally, the application should be reload or restarted in order to release the rotated file but restart the whole application for that seems a bit...heavy.

Related issues 2 (0 open — 2 closed)

	Related to Rudder - Bug #3603: The files written by syslog in /var/log/rudder/reports/*.log and slapd in /var/log/rudder/ldap/slapd.log are still empty after a logrotate	Released	Jonathan CLARKE	2013-05-22			Actions
	Related to Rudder - Bug #4433: Log rotation problems due to bad post-rotate script	Rejected	Benoît PECCATTE	2014-01-31			Actions

Issue # Delay: days Cancel

History
Notes
Property changes

Actions

Copy link

Updated by Nicolas PERRON over 10 years ago

Status changed from New to Discussion
Assignee set to François ARMAND

I wonder if this file should be rotated with log4j. What do you think François ?

Actions

Copy link

Updated by François ARMAND over 10 years ago

I think so, else log4j doesn't know where to write (the file it was written to is no more here). But it should be checked on internet.

Actions

Copy link

Updated by Nicolas PERRON over 10 years ago

Target version changed from 2.4.8 to 2.4.9

Actions

Copy link

Updated by François ARMAND over 10 years ago

This is related to #3916

It is known that Log4j does not handle correctly rotation if logrotate is not configure with copytruncate.

I thing that one should be closed as "duplicate" of #3916, no?

Actions

Copy link

Updated by François ARMAND over 10 years ago

Assignee changed from François ARMAND to Nicolas PERRON

Actions

Copy link

Updated by Nicolas PERRON over 10 years ago

Assignee changed from Nicolas PERRON to François ARMAND

Not sure. This is related because I was asking if log4j or logrotate should manage the rotation but in my opinion, this is not really a duplicate.

Actions

Copy link

Updated by Nicolas PERRON over 10 years ago

Target version changed from 2.4.9 to 2.4.10

Actions

Copy link

Updated by Nicolas PERRON over 10 years ago

Target version changed from 2.4.10 to 2.4.11

Actions

Copy link

Updated by Nicolas PERRON over 10 years ago

Target version changed from 2.4.11 to 2.4.12

Actions

Copy link

#10

Updated by Nicolas PERRON over 10 years ago

Target version changed from 2.4.12 to 2.4.13

Actions

Copy link

#11

Updated by François ARMAND over 10 years ago

Assignee changed from François ARMAND to Nicolas PERRON

I don't know what to say more than what is already say here and in #3916.

Log4j (as it's what Jetty uses) does not reload file when they are closed. We don't have any way to make it so. So the only solutions I see are:
1/ to reload the webapp (not good)
2/ make Log4j handle the rotation (and so duplicate of #3916).
3/ to use copytruncate (and so duplicate of #3916).

Actions

Copy link

#12