You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the rate of logging is fast, e.g. 200 lines/second and the file rotation with [maxsize, maxFiles, tailable] settings when files rotate the logger continues to write to old files forever, these old files get deleted but continue being written to leading to exhaustion of disk space
What do you expect to happen instead?
The logger should only be writing to one file at a time.
The text was updated successfully, but these errors were encountered:
ledbit
pushed a commit
to diag/winston
that referenced
this issue
Apr 7, 2021
Here's an example. Winston writes to both the current (output-debug.log) and an old (output-debug2.log) file. Leading to maxsize of 100mb not being respected.
Hi folks, I apologize that this issue has been sitting open for quite some time, but I'd encourage you to try the latest version of winston, which includes some fixes related to log rotation from the File transport (e.g. #2301). If anyone is able to confirm whether this issue is still happening or whether it seems resolved with the latest winston, that would be extremely helpful. And if it's still happening, any kind of MWE would be very helpful in order for others to more easily investigate and resolve an issue like this.
Please tell us about your environment:
winston
version?winston@2
winston@3
node -v
outputs: v14.15.1What is the problem?
When the rate of logging is fast, e.g. 200 lines/second and the file rotation with
[maxsize, maxFiles, tailable]
settings when files rotate the logger continues to write to old files forever, these old files get deleted but continue being written to leading to exhaustion of disk spaceWhat do you expect to happen instead?
The logger should only be writing to one file at a time.
The text was updated successfully, but these errors were encountered: