Bug 170685
Summary: | up2date from u1 to u2 causes system to freak out | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | jmccann |
Component: | audit | Assignee: | Steve Grubb <sgrubb> |
Status: | CLOSED WORKSFORME | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.0 | CC: | cschalle, dwalsh |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-02-22 00:06:10 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
jmccann
2005-10-13 19:04:37 UTC
This looks like SE Linux messages. Adding Dan to bug report. Wrong file context on utmp. restorecon /var/run/utmp OK. So, something must have caused it to become incorrect, right? Seems like a real bug to me. Did you boot with SELinux=0? Did you boot with a non SELinux kernel? Otherwise you will have to tell me how it got created with the wrong context. If an initscript created it, it should have the correct context. If another application deleted and recreated it, this is the context it would have. Stock boot options for a stock kernel. I assume it must have had the correct context before the up2date because there were no error messages before that time. Well I have no idea then. Watch it and report if it changes back. Dan I'm not sure what you mean. The context issue seems to be fixed after a reboot. However, before then the system in some cases is DoS'd by the flood of log messages and if so configured a loghost may be nearly DoS'd too. However, up2date indicates none of this. My guess is that there is a bug in some %post or trigger script. If a post install script removed and regenerated utmp this could happen. But without knowing which rpm package, it would be difficult to find. I also have not seen this bug reported by many others so I think it might be a strange occurrance. Of course I should be knocking on wood. Can not reproduce. Hey Daniel, sorry I never got back to this. I was able to reproduce it a few more times but could never pin it down to a particular package during the up2date. This hasn't happened recently. I'm tempted to blame up2date sucking ass. Thanks. |