-
-
Notifications
You must be signed in to change notification settings - Fork 254
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
[BUG] no more logrotate with access.log #451
Comments
The issue has been previously reported(see here) and fixed in this PR, but it hasn't been merged by the maintainers yet. For now you can just use the test image from the branch i.e. |
Yes i find it after i posted the issue. I will wait the official release, until then i force logrotate with command line in the container. |
Fixed in #441 |
Is there an existing issue for this?
Current Behavior
Some weeks ago my swag dashboard started to have very long loading time.
After some checks, i find my access.log was huge (more than 400MB). The cause is that there was no logrotate since the beginning of december (3 december for me at 02:00). Before that i can see logrotate working once a week.
On the 15 january , i have forced a manual logrotate by connecting in the container, it works and started a new access.log, but still no logrotate for now.
Expected Behavior
No response
Steps To Reproduce
Using latest swag image
Environment
- OS: OMV 6 latest version
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: