Product SiteDocumentation Site

Chapter 24. Troubleshooting Installation on IBM System z

24.1. You are unable to boot Red Hat Enterprise Linux
24.1.1. Is Your System Displaying Signal 11 Errors?
24.2. Trouble During the Installation
24.2.1. No devices found to install Red Hat Enterprise Linux Error Message
24.2.2. Saving traceback messages
24.2.3. Other Partitioning Problems
24.3. Problems After Installation
24.3.1. Remote Graphical Desktops and XDMCP
24.3.2. Problems When You Try to Log In
24.3.3. Your Printer Does Not Work
24.3.4. Apache HTTP Server or Sendmail stops responding during startup
This section discusses some common installation problems and their solutions.
For debugging purposes, anaconda logs installation actions into files in the /tmp directory. These files include:
/tmp/anaconda.log
general anaconda messages
/tmp/program.log
all external programs run by anaconda
/tmp/storage.log
extensive storage module information
/tmp/yum.log
yum package installation messages
/tmp/syslog
hardware-related system messages
If the installation fails, the messages from these files are consolidated into /tmp/anaconda-tb-identifier, where identifier is a random string.
All of the files above reside in the installer's ramdisk and are thus volatile. To make a permanent copy, copy those files to another system on the network using scp on the installation image (not the other way round).

24.1. You are unable to boot Red Hat Enterprise Linux

24.1.1. Is Your System Displaying Signal 11 Errors?

A signal 11 error, commonly known as a segmentation fault, means that the program accessed a memory location that was not assigned to it. A signal 11 error may be due to a bug in one of the software programs that is installed, or faulty hardware.
Ensure that you have the latest installation updates and images from Red Hat. Review the online errata to see if newer versions are available.