The pre-check script (see Using the Pre-Check
Script) generates the following files:
- Precheck Log: This log is more detailed than the basic output described in
Sample Pre-Check Output, but
contains high-level information based on the options supplied when you ran the
script and the findings generated by the script. This file will be stored in
/tmp/bd_prechecks.<pid>.log, where <pid> is the process ID number of the script run, such as 11893. HPE may request this file if you contact us for technical
support.
- Xtrace: This file is a verbose, line-by-line description of the exact
commands used by the script to both get data and determine the outcome of each test.
This file will be stored in
/tmp/bd_prechecks.<pid>.log.xtrace, where <pid> is the process ID number of the script run, such as 11893. It is intended for use by HPE for support purposes, and
HPE may request this file if you contact us for technical support.
Note:
Neither the .log nor .xtrace files will pass any data or other
sensitive information to HPE.
- Configuration file: The pre-check script will also generate a configuration
file that you can use to speed up installing the Controller host. This file passes
relevant configuration to the installer and bypasses the checking performed by that
script. This file will be named
/tmp/bd_prechecks.conf. See Using the Pre-Check Config File.
CAUTION:
DO NOT MODIFY THE CONTENTS OF THE CONFIG FILE BEFORE PASSING
IT TO THE INSTALLER AS THIS COULD CAUSE THE CONTROLLER HOST
INSTALLATION PROCESS TO FAIL.
CAUTION:
THE PRE-CHECK SCRIPT WILL GENERATE A CONFIGURATION FILE
REGARDLESS OF ANY WARNINGS OR ERRORS ENCOUNTERED. DO NOT USE THE
CONFIGURATION FILE TO INSTALL HPE EZMERAL CONTAINER
PLATFORM IF ANY TESTS HAVE FAILED.