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
We're using DailyRotateFile transport and also have separate log archiving box. So after a few days, we move all the log files from app boxes to archive server to free up some space on app boxes, and here comes the problem.
So we have log files with very low traffic (like severe errors) that would have only couple of log entries per week, and the node.js app is running for months without restarting.
The app logged something to the file "20141125.log" which is a week ago, and the app is still running, that file "20141125.log" is already moved to the archive days ago, but the app is still pointing to that file. And today, the app is trying to log something more, and it'll write that log message to the old file "20141125.log" rather than "20141202.log". So it actually creates a file named "20141125.log" again and writes log entry in there.
The text was updated successfully, but these errors were encountered:
The DailyRotateFile transport was moved to a separate module (winston-daily-rotate-file) as of winston@2.0.0. As such we are closing issues here and tracking their status in a single tracking issue in the new repository.
We're using DailyRotateFile transport and also have separate log archiving box. So after a few days, we move all the log files from app boxes to archive server to free up some space on app boxes, and here comes the problem.
So we have log files with very low traffic (like severe errors) that would have only couple of log entries per week, and the node.js app is running for months without restarting.
The app logged something to the file "20141125.log" which is a week ago, and the app is still running, that file "20141125.log" is already moved to the archive days ago, but the app is still pointing to that file. And today, the app is trying to log something more, and it'll write that log message to the old file "20141125.log" rather than "20141202.log". So it actually creates a file named "20141125.log" again and writes log entry in there.
The text was updated successfully, but these errors were encountered: