Bug 28825
Summary: | Network install crashes when installing chkconfig | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | n.blackaby |
Component: | anaconda | Assignee: | Michael Fulbright <msf> |
Status: | CLOSED RAWHIDE | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.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: | 2001-02-28 16:40:04 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
n.blackaby
2001-02-22 12:17:32 UTC
If any messages appear on the screen when it crashes that would be very helpful to know about. Messages on screen after installation program crashes out during chkconfig package install are: install exited abnormally -- received signal 11 sending termination signals...done sending kill signals ...done disabling swap unmounting filesystems (etc...) The machine concerned is a relatively new Dell PowerEdge 2450 server with one internal 18GB SCSI disk and two ethernet cards. How much RAM is detected (you can cat /proc/meminfo from VC2 once you see the welcome screen in the installer)? Also, what are you running as the web server you are using to drive the HTTP install? Finally, can you try a NFS or FTP install from this host? (i) RAM detected = 896MB -- why can't Redhat Linux be compiled to see a bit more than this (say at least 1GB)? (ii) HTTP install via Apache 1.3.14 on Solaris 7 on Sun Ultra 2 (iii) HTTP fails every time (always at same place [chkconfig]) FTP install tried and completed twice (100% success) NFS install worked twice and failed twice (50% success) In more detail, it appears the HTTP install will always fail; the FTP install will always work whereas the NFS install will work every-other time (eg. the second time, the fourth time)! Also, the two times the NFS install failed, it failed in the _same_ place (during the "bind" package install). Please try with the more recent wolverine beta release. HTTP install runs to completion OK with latest beta (Wolverine; RH 7.0.91). It appears to take a lot longer to install than earlier versions of RH7 (almost double the time?). On SCSI systems the newer 2.4 kernels seem to have some tuning problems we're looking at. Noting that wolverine works for you. |