Bug #3868
closedThe files written by java in /var/log/rudder/core/*.log are still empty after a logrotate
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.
Updated by Nicolas PERRON over 11 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 ?
Updated by François ARMAND over 11 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.
Updated by Nicolas PERRON about 11 years ago
- Target version changed from 2.4.8 to 2.4.9
Updated by François ARMAND about 11 years ago
Updated by François ARMAND about 11 years ago
- Assignee changed from François ARMAND to Nicolas PERRON
Updated by Nicolas PERRON about 11 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.
Updated by Nicolas PERRON about 11 years ago
- Target version changed from 2.4.9 to 2.4.10
Updated by Nicolas PERRON about 11 years ago
- Target version changed from 2.4.10 to 2.4.11
Updated by Nicolas PERRON about 11 years ago
- Target version changed from 2.4.11 to 2.4.12
Updated by Nicolas PERRON about 11 years ago
- Target version changed from 2.4.12 to 2.4.13
Updated by François ARMAND about 11 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).
Updated by Vincent MEMBRÉ almost 11 years ago
- Target version changed from 2.4.13 to 2.6.11
Since version 2.4 is not maintained anymore, retargeting to branch 2.6
Updated by Vincent MEMBRÉ over 10 years ago
- Target version changed from 2.6.11 to 2.6.12
Updated by Vincent MEMBRÉ over 10 years ago
- Target version changed from 2.6.12 to 2.6.13
Updated by Vincent MEMBRÉ over 10 years ago
- Target version changed from 2.6.13 to 2.6.14
Updated by Jonathan CLARKE over 10 years ago
- Target version changed from 2.6.14 to 2.6.16
Updated by Jonathan CLARKE over 10 years ago
- Target version changed from 2.6.16 to 2.6.17
Updated by Nicolas PERRON over 10 years ago
- Target version changed from 2.6.17 to 2.6.18
Updated by Matthieu CERDA about 10 years ago
- Target version changed from 2.6.18 to 2.6.19
Updated by Vincent MEMBRÉ about 10 years ago
- Target version changed from 2.6.19 to 2.6.20
Updated by François ARMAND almost 10 years ago
- Assignee deleted (
Nicolas PERRON) - Target version changed from 2.6.20 to 2.10.10
Updated by Vincent MEMBRÉ almost 10 years ago
- Target version changed from 2.10.10 to 2.10.11
Updated by Vincent MEMBRÉ over 9 years ago
- Target version changed from 2.10.11 to 2.10.12
Updated by Benoît PECCATTE over 9 years ago
- Project changed from 34 to Rudder
- Category set to Packaging
Updated by Vincent MEMBRÉ over 9 years ago
- Target version changed from 2.10.12 to 2.10.13
Updated by François ARMAND over 9 years ago
- Category changed from Packaging to System integration
- Status changed from Discussion to Rejected
- Reproduced set to No
This is a duplicate of (a subpart of) #6381.
Marjing at rejected (resolved).