Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
Unable to manually install, anaconda dies after installing last package

Version-Release number of selected component (if applicable):
RHEL6.1-20110222.n.1_nfs-Server-x86_64 	

How reproducible:
always on hp-ml370g4-01.rhts.eng.bos.redhat.com with RHEL6.1-20110222.n.1_nfs-Server-x86_64 	

Steps to Reproduce:
1. schedule a beaker reserve job and add manual and vnc options form manual vnc install
2. 20.000MB / /dev/sda1, rest of /dev/sda free space
3. run the instalation
  
Actual results:
04:42:22 Starting graphical installation.
Anaconda died after receiving signal 9.
install exited abnormally [1/1] 
The system will be rebooted when you press Ctrl-C or Ctrl-Alt-Delete.

Expected results:
successfull instalation

Additional info:
doesn't have to be anaconda issue, no idea where the signal 9 came from

How much memory does the machine have?

Can you grab /tmp/anaconda.log and /tmp/syslog from the machine once you hit this error?  You may need to add the "nokill" parameter.

(In reply to comment #2)
> How much memory does the machine have?
> 
> Can you grab /tmp/anaconda.log and /tmp/syslog from the machine once you hit
> this error?  You may need to add the "nokill" parameter.

According beaker information, the machine has 867 MB of memory.

Anaconda log:
http://beaker-archive.app.eng.bos.redhat.com/beaker-logs/2011/02/560/56053/114232///anaconda.log
sys.log beaker provides, not sure if is identical with /tmp/syslog
http://beaker-archive.app.eng.bos.redhat.com/beaker-logs/2011/02/560/56053/114232///sys.log

Just as I thought - first depmod, then anaconda are getting killed by the oom killer.  I don't know that there's anything we can do about this situation.