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
{{ message }}
This repository was archived by the owner on Jun 12, 2018. It is now read-only.
I'm not entirely sure where to file this bug, so feel free to redirect it to the appropriate project.
I have a cozy instance which I don't use very often and don't monitor. It ended up filling the disk of the machine on which it was running. The culprit was the emails.log which ended up being 30G.
There's currently no log rotation, that's probably something that should be added system wide.
For the record, email's logs grow fast because the application was very verbose, to help us debug imap issues. We made it way less verbose some months ago. Also, logs are rotated each time the application restart. So, restarting the application from time to time is a workaround to prevent the logs from becoming to big.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm not entirely sure where to file this bug, so feel free to redirect it to the appropriate project.
I have a cozy instance which I don't use very often and don't monitor. It ended up filling the disk of the machine on which it was running. The culprit was the emails.log which ended up being 30G.
Should cozy do some kind of log rotation ? Is it the task of cozy-emails ? Should this be a system side logrotate configuration ?
As you can see it's running inside Docker (but built a long time ago, so maybe this is now handled in https://github.com/cozy-labs/cozy-docker ?)
Thanks for your help and advice.
The text was updated successfully, but these errors were encountered: