Troubleshooting on UNIX systems

Writing messages to log files is disabled by default on UNIX systems. You can enable debugging functions by using the debug input parameter. The tool writes the debug data to a log file and uses time stamps to flag the start and end times of steps or functions. You can use the log file to correlate and troubleshoot a specific issue, function, or prerequisite check.

Attention: Before Prerequisite Scanner Version 1.2.0.1, Prerequisite Scanner supported an optional trace parameter that logged the trace information in the ips_output_dir/temp/prs.trc file. The input parameter and trace file are deprecated. If you specify the trace parameter in the command line, a warning message is displayed.

Debugging log file

When you run the Prerequisite Scanner script and set the optional debug parameter, Prerequisite Scanner writes detailed processing and debugging information and the scan results to the ips_output_dir/precheck.log file. It also writes informational, warning, and error messages to the file.

If you do not set the optional parameter, Prerequisite Scanner outputs the scan results, informational, warning, and errors messages in the ips_output_dir/precheck.log file by default.

Attention: Before Prerequisite Scanner Version 1.2.0.1, the tool logged the debugging information to the ips_output_dir/temp/prs.debug file. This file is now deprecated, with the contents logged to the precheck.log file.

The ips_output_dir/temp subdirectory also contains the interim result1.txt and result2.txt files that provide the input to the final ips_output_dir/result.txt file. You can use these interim files to determine issues with results for specific prerequisite checks.

Figure 1. precheck.log file on UNIX systems