Bug 169632

Summary:	Running anaconda - please wait... install exited abnormally -- received signal 4
Product:	Red Hat Enterprise Linux 2.1	Reporter:	Daniel Schuh <lord_schuh>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED NOTABUG	QA Contact:	Mike McLean <mikem>
Severity:	high	Docs Contact:
Priority:	medium
Version:	2.1
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:	2005-10-03 18:08:08 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 Daniel Schuh 2005-09-30 14:20:14 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6

Description of problem:
Installing this particular version of Redhat in my rx2600 I get this error message reproduced at the Summary field:

Running anaconda - please wait...
install exited abnormally -- received signal 4
sending termination signals...done

Other sistems and versions of Redhat works fine.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Download the installation disk from HP home page.
2. Burn a RW-CD with it.
3. Boot the rx2600 with the install CD of Redhat.
4. Lauch the installation with all default options.

Actual Results:  Running anaconda - please wait...
install exited abnormally -- received signal 4
sending termination signals...done
...

Expected Results:  It should had been installed.

Additional info:

Comment 1 Paul Nasrat 2005-09-30 15:26:07 UTC

For RHEL support issues the process is to contact support

https://www.redhat.com/support/service/guide/

as documented here

https://bugzilla.redhat.com/bugzilla/index.cgi

Comment 2 Jeremy Katz 2005-10-03 18:08:08 UTC

Also, SIG4 is usually caused by hardware problems

Comment 3 Daniel Schuh 2005-10-07 18:15:16 UTC

You'r right.
It was a CRC in the image.
I had to download it 3 times, probably a connection related problem.

Thanks!