Bug 6938

Summary:	Python interpreter throws SIGSEGV during upgrade procedure
Product:	[Retired] Red Hat Linux	Reporter:	Philip Hisley <pnh>
Component:	installer	Assignee:	Matt Wilson <msw>
Status:	CLOSED RAWHIDE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.1
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2000-02-22 16:09:12 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 Philip Hisley 1999-11-12 00:16:55 UTC

Attempting to upgrade a running 5.2 Redhat Linux system to 6.1 using
RedHat 6.1 distribution. During the initial part of the upgrade when the
RPM database is being rebuilt, the Python interpreter throws a segment
violation:

"Python SIGSEGV Received at PC 0xb in PID 23"

The upgrade process then terminates.

Comment 1 Philip Hisley 1999-11-12 03:47:59 UTC

Problem Solved.

This problem appears to be related to one of two factors:
1. The RPM database was corrupted  -or-
2. There was not enough room in the root partition to rebuild the RPM databse

To solve the problem I deleted files to make room in order to rebuild the RPM
database. I then rebuilt the RPM database from the console prompt. Upon
rebooting the system and rerunning the upgrade procedure everything went fine
-- excpet for the fact that the upgrade procedure overwrote the MBR witout
asking and clobbered my mulit-boot handler (BootMagic).

It would appear that the Python interpreter/script does not exit gracefully
upon encountering the problems indicated above.

This bug appears to be similar in nature to Bug reports 5545 and 5705.

Comment 2 Jay Turner 1999-11-29 20:11:59 UTC

This issue has been forwarded to a developer for further action.

Comment 3 Jay Turner 1999-11-29 20:37:59 UTC

*** Bug 6913 has been marked as a duplicate of this bug. ***

Comment 4 Jay Turner 2000-02-22 16:09:59 UTC

Error handling is vastly improved in the latest installer (available in beta) so
that should help out with problems like this.