-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ParseServer maxLogFiles not yet effective ? #8827
Comments
Thanks for opening this issue!
|
Hello, |
@vivekjoshi556 Sure, please go ahead |
Hello @mtrezza & @zurmokeeper, I was unable to reproduce the error. The rotation worked fine on my system. On the next day, the files rotated as expected. And you are right about Winston's documentation that maxSize is a required parameter but we are using winston-daily-rotate-file and there is nothing specified in the documentation about maxSize being required for maxFiles (from what I could understand, let me know if you find something else). While checking it threw an error when I tried to use a value ending with a 'd' (e.g. '5d') for maxLogFiles (which is an acceptable value according to documentation in parse). According to documentation for maxLogFiles:
I don't think 'd' matters here anyway because both imply the same thing. |
Duplidate #6426 I looked into this years ago. The objectParser needs to be changed to numberStringParser. |
Closing as duplicate; added bounty to other issue since it's already open for 4 years. |
New Issue Checklist
Issue Description
maxLogFiles not yet effective ????
I specified the maximum number of log files as 5, but the number of generated files still exceeds 5, I read the configuration of winston, it is necessary to use with maxsize, in the exceeding of maxsize will automatically delete the log files before 5. But I read the source code of winston and parse-server configurations, and this maxLogFiles configuration is not correct to be used in winston in the end.
Steps to reproduce
Actual Outcome
Expected Outcome
Environment
Server
v6.3.1
windows
Database
MongoDB
5.0
Logs
The text was updated successfully, but these errors were encountered: