Checking System Configuration Before Bootstrapping

the precheck command helps capture critical node health states and metrics before bootstrapping your {{ocient}} installation you can run the command as shown in this example the flags included after the precheck command are optional see /#optional flags for command execution for descriptions $ sudo precheck print level verbose node type metadata logfile location /home/admin the command invokes a script from the command line on operating systems supported by ocient the script sends output to standard output (stdout) and standard error (stderr) to specify the file option, use this flag logfile location \<directory> where \<directory> is the directory where the precheck command creates the log file critically, this script captures information about huge page configuration optional flags for command execution use the precheck command to run the script that checks the system configuration you can execute the command using the optional flags shown in this table flag name values default description example logfile location non empty string /var/opt/ocient/log name of the directory that contains the log file created from the execution of the script logfile location /user/query/logs generates a log file in the /user/query/logs directory if this directory does not exist, the command issues a warning print level verbose or silent verbose denotes the level of detail in the output see the “outputs” section print level verbose provides a detailed report with information about the checks that ocient performs print level silent provides the overall status from the check of the system node type metadata, lts, streamloader, sql, or unknown unknown denotes the current node type if you do not specify this setting, the script tries to infer node type based on metrics it collects node type lts runs checks with values and constraints that pertain to an lts node timeout any integer 3 denotes the default timeout (in seconds) to run any command line command in the script in most cases, the default is enough, so you do not need to specify this setting timeout 4 runs checks with a timeout of 4 seconds for each command nvme driver util path non empty string /opt/ocient/scripts/nvme driver util sh path to nvme driver util script that the precheck script uses the default value is the location of the script on most installations, so in most cases, you do not need to specify this setting nvme driver util path /opt/ocient/test dir/nvme driver util sh uses /opt/ocient/test dir/nvme driver util sh as the path to the utility script json not applicable false if you specify the json flag, the command prints output in json format to stdout if you do not specify this flag, the command prints human readable output to stdout json prints output in json format to stdout command output the command has two types of output, silent or verbose, which you can specify by using the print level flag at the command line silent the silent value for the print level flag only produces a status code the code is 0 for success, 1 for error, and 2 for warning verbose the verbose value for the print level flag prints either human readable output by default or output in json format (if you specify the json flag) the output contains all status details this example shows human readable output warnings \ isolcpus not configured recommended for performance \ no eligible nvme payload drives found for node \ bootstrap conf file does not exist create a file at /var/opt/ocient/bootstrap conf with the correct bootstrapping settings if this is the initial node in the system set "initialsystem true" in the bootstrap conf file if this is not the initial node, use the "adminhost" setting to specify the address of the initial node to add custom settings, follow the instructions in bootstrapping and ocient system in the user documentation \ selinux is enabled this might prevent ocient from functioning properly please disable or set to permissive mode memory ok \====== ramconfig success ram configuration is adequate firmware and hardware error \==================== nonbootdrives warning no eligible nvme payload drives found for node this example shows output in json format {"status" 1, "components" { "enforce status" { "status" 2, "message" "warning selinux is enabled this might prevent ocient from functioning properly please disable or set to permissive mode" } "bootstrap" { "status" 2, "message" "warning bootstrap conf file does not exist create a file at /var/opt/ocient/bootstrap conf with the correct bootstrapping settings if this is the initial node in the system set "initialsystem true" in the bootstrap conf file if this is not the initial node, use the "adminhost" setting to specify the address of the initial node to add custom settings, follow the instructions in bootstrapping and ocient system in the user documentation " } } } related links docid 4005nflvguw4fqfqa1spu docid\ nneedy7yn8g1pennmamng