Bug 77469
Summary: | Significant Data-loss type issues on RHN updates | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <questy> |
Component: | up2date | Assignee: | Adrian Likins <alikins> |
Status: | CLOSED WORKSFORME | QA Contact: | Red Hat Satellite QA List <satqe-list> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 8.0 | CC: | gafton, mihai.ibanescu |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-01-15 06:09:35 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
2002-11-07 15:54:54 UTC
try: rm -rf /var/lib/rpm/__* and trying again. This looks to be a rpm database related locking bug (the __* files are essentially lock files). Ok... found and fixed problem. Note: If *any* program up2date is going to update is open, or even in memory, the rpm database (instead of not applying the update and giving an error as should be) will simply corrupt itself. a quick edit of inittab to runlevel 3, reboot, rpm --rebuilddb, and then an up2date on a clean boot fixes the problem. Thanks for the help. |