Chapter 5. Troubleshooting Prerequisite Scanner
You can troubleshoot issues in IBM Prerequisite Scanner by using log files and
logging functions when you create custom prerequisite checks.
Prerequisite Scanner generates returns codes dependent on the results of the scan
and whether it must exit because of errors. These return codes are written to the
log files. For example, if the Prerequisite Scanner fails to run the scan because
cannot read the configuration file, it generates return code of 2.
Troubleshooting on Windows systems
When you run IBM Prerequisite Scanner, it creates a log file by default. It contains
detailed information with each step and function that the Scanner performs in
sequence. The file also contains timestamps, including start and end times of each
function and step. You can debug and review the log file to determine where and
when the error occurred.
Prerequisite Scanner outputs processing information, warning and error messages,
and the scan results in the ips_output_dir/precheck.log file. When you run the
Prerequisite Scanner script and set the optional debug parameter, Prerequisite
Scanner outputs additional debugging messages in this file.
Figure 11 on page 68 shows an example of the log file when the optional debug
parameter is set and Figure 12 on page 69 shows the log file when the parameter is
not set.
© Copyright IBM Corp. 2009, 2012
67
Need help?
Do you have a question about the Prerequisite Scanner and is the answer not in the manual?
Questions and answers