Bug 8003
Summary: | kernel log entries lost after /etc/logrotate.d/syslog runs | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | peterw |
Component: | sysklogd | Assignee: | Bill Nottingham <notting> |
Status: | CLOSED WORKSFORME | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.1 | CC: | rhw, rvokal |
Target Milestone: | --- | Keywords: | Security |
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 1999-12-27 05:28:25 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
peterw
1999-12-27 00:34:57 UTC
Oops. Updated to latest sysklogd package for RH 6.1. Seems OK now. There appears to be a slight race problem here. If my analysis is right, then either syslogd or klogd blocks if the kernel generated an OOPS whilst the logs are being rotated, and about five minutes of logs vanish as a result. The problem, of course, is that the ONLY evidence of this happenning is a gap in the logs where entries relating to syslogd restarting should occur. As a result, it's virtually impossible to produce any examples. |