Bug 131746 - installer crashes when NFS server is not running
installer crashes when NFS server is not running
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: anaconda (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2004-09-03 16:51 EDT by Max Spevack
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-12-21 09:49:15 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Max Spevack 2004-09-03 16:51:00 EDT
Description of problem:

I was trying to do an NFS install of RHEL3U2, and every time I entered
the information of the server/directory (using linux askmethod) when I
installed, it would say something like "installer exited with signal
11" and I would have to reboot.

After a while I realized that I had rebooted the machine that had the
install images available over NFS, and I hadn't restarted nfs on that

The bug here is that if nfsd isn't running on the machine name
entered, the installer should re-prompt or give an error message to
that effect rather than crash with only signal 11 as the output, since
that offers no real debugging information to the user.

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

How reproducible:
always -- try installing via NFS when the machine that you enter as
the nfs host isn't running nfsd

Steps to Reproduce:
1. see description
Actual results:

anaconda crashes

Expected results:

non-crash, more informative error message

Additional info:
Comment 1 Jeremy Katz 2004-09-07 00:20:18 EDT
Merged the fix from HEAD to the RHEL3 branch for a future update.
Comment 2 John Flanagan 2004-12-21 09:49:15 EST
An advisory has been issued which should help the problem 
described in this bug report. This report is therefore being 
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, 
please follow the link below. You may reopen this bug report 
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.