Backport #12350
closedProvided logrotate setup does not handle ceph-fuse correctly
Updated by Greg Farnum almost 9 years ago
- Priority changed from Normal to High
- Tags set to new_dev
Updated by Zhi Zhang over 8 years ago
Hi Greg,
Since our production cluster is also encountered same issue recently, we provide following fix. I describe more details in PR. Could you pls take a look? Thanks.
Updated by Greg Farnum over 8 years ago
- Status changed from New to Fix Under Review
Updated by Zhi Zhang over 8 years ago
- Tracker changed from Backport to Bug
- Category set to 45
- Status changed from Fix Under Review to Pending Backport
- % Done set to 0
- Backport set to hammer
Updated by Loïc Dachary over 8 years ago
- Tracker changed from Bug to Backport
- Description updated (diff)
- Status changed from Pending Backport to In Progress
- Assignee set to Zhi Zhang
original description¶
(move here because Backport issues only have a link to the PR in the description)
OS: Ubuntu 14.04
Ceph: Hammer 0.94.2
Increasing the debug output of ceph-fuse results in large log files in /var/log/ceph.
The logrotate setup handles the usual ceph daemon correctly (mon, osd, mds), but in case of ceph-fuse the postrotate entry does not handle a ceph-fuse mountpoint at all. Since logrotate moves and compresses the log file, you end up with a stale open fd and the (now invisible) log file starts to consume disk space...
Proposed solution:
- make ceph-fuse reopen its logfile on SIGHUP (or similar notification mechanism)
- in case of a processed ceph-fuse logfile (ceph-client.XYZ.log) notify ceph-fuse after log rotation
Updated by Loïc Dachary about 8 years ago
- Status changed from In Progress to Resolved
- Target version set to v0.94.7