If we're rlimiting the thumbor process from creating files bigger than 1GB, it applies to log files as well. And currently production log files can be bigger than the 1GB limit. We need to see if there's a way to configure python logging so that it would roll over not just based on date but also when log files go over a certain size.
Description
Description
Details
Details
Revisions and Commits
Revisions and Commits
| rTHMBREXT Thumbor Plugins | |||
| rTHMBREXT8620ce9c2623 Version bump | |||
| rTHMBREXTb3058eec21be Fall back to unsafe rollover when lock cannot be acquired | |||
| rTHMBREXTb0a56d032b71 Add class for multiprocess-safe log rotation | |||
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | • Gilles | T121388 Service-based thumbnailing re-architecture in production with Thumbor | |||
| Resolved | • Gilles | T139606 add thumbor to production infrastructure | |||
| Resolved | • Gilles | T145878 thumbor imagemagick filling up /tmp on thumbor1002 | |||
| Resolved | • Gilles | T150208 Avoid thumbor generating log files > 1GB |
Event Timeline
Comment Actions
Change 320273 had a related patch set uploaded (by Gilles):
Rotate Thumbor 404 log by size, not date
Comment Actions
The size-based rotation appears to be working fine:
gilles@thumbor1001:/srv/log/thumbor$ ls -alh total 2.3G drwxr-xr-x 2 thumbor thumbor 4.0K Nov 14 09:36 . drwxr-xr-x 3 root root 4.0K Oct 18 14:44 .. -rw-r--r-- 1 thumbor thumbor 431M Nov 14 09:36 thumbor.404.log -rw-r--r-- 1 thumbor thumbor 901M Nov 13 07:11 thumbor.404.log.1 -rw-r--r-- 1 thumbor thumbor 901M Nov 10 13:02 thumbor.404.log.2 -rw-r--r-- 1 thumbor thumbor 0 Nov 10 13:02 thumbor.404.log.lock