A scenario that narrows down the root cause, centered on understanding the difference between log rotation and file handles, in the situation of an open log-file problem where space is not freed even after logrotate runs.
An open log-file problem where space is not freed even after logrotate runs
Covers a common operational trap where swapping the log file without restarting the service still does not free space.
시나리오
단서
구독하면 이어서 볼 수 있어요
이 문제의 전체 시나리오와 점검 체크리스트, 복구 순서, 모범 풀이는 Pro 구독에서 열립니다.
먼저 볼 것
- Identify the primary failure signal in the Log Management scenario.
- Separate visible symptoms from the underlying technical dependency.
- Describe the safest recovery path and the follow-up prevention work.
점검 체크리스트
- Summarize the current impact and the last known change.
- Collect direct evidence from logs, runtime state, and configuration before changing anything.
- Separate immediate recovery from permanent prevention work.
복구와 재발 방지
Choose the smallest safe recovery action first, then record the prevention work that reduces repeat incidents.
같이 보면 좋은 질문
A process may keep writing to a deleted or rotated file descriptor until it reopens the log handle.
Verify the open file handle, then reopen or restart the relevant process in the least disruptive way.
현장에서 본 비슷한 케이스