Bug 23273
Summary: | logrotate goes berzerk and fills /var, uses all inodes | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <rick> |
Component: | logrotate | Assignee: | Preston Brown <pbrown> |
Status: | CLOSED WORKSFORME | QA Contact: | David Lawrence <dkl> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 7.0 | CC: | dr, jarno.huuskonen |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-06-21 20:34:52 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Need Real Name
2001-01-04 08:14:53 UTC
Can you give us a little bit more information on this bug? In the environment where you are having this problem, run "logrotate -v" and attach the output to the bug report. I don't have logrotate running in those environments any more due to this problem. I'd find /var full (and these were 512MB /var partitions) due to /var/log/{mail,news} being filled with thousands and thousands of files named like: mail.1.gz.2.gz.1.gz.2.gz mail.1.gz.2.gz.1.gz.2.gz.1.gz [and on out with something like 15 gz's in a single name] It looked to me like logrotate was versioning and gzipping files it had already versioned and gzipped. I thought perhaps the directory permissions (0600) had something to do with it, but ultimately even changing them to 700 or even 755 didn't seem to alleviate the problem. Ultimately I moved to a pair of centralized loghosts running FreeBSD and using a custom rotation and summarization script instead of logrotate. Sorry I can't be more helpful. Rick Bradley (rick) Thanks for trying. We haven't been able to duplicate this and there have been no other reports of such behaviour, so I have to assume it is a very esoteric bug related somehow to the environment that had been set up. |