Bug 6913
Summary: | Updated installer died with a signal 11 near/at the end of installing RPMs | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Chris Siebenmann <cks-rhbugzilla> |
Component: | installer | Assignee: | Jay Turner <jturner> |
Status: | CLOSED DUPLICATE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 6.1 | CC: | srevivo |
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: | 1999-12-02 15:44:56 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
Chris Siebenmann
1999-11-11 04:14:28 UTC
Try rebuilding the RPM databse and then running the upgrade. We have a couple of reports of similiar problems when running the upgrade process on a RPM database which might be corrupt. I am making this bug a duplicate of #6938. Please reopen if rebuilding the database does not change the behavior that you are seeing. *** This bug has been marked as a duplicate of 6938 *** I am about 90% sure that the install that died did a RPM database rebuild at the start (I think it's standard practice). Since we couldn't afford to leave the server half-upgraded (and rather definetly out of service) we have long-since kludged through the upgrade, so nothing remains at this date to retry. |