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 checking system configuration before bootstrapping /#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 82,96,81,152,285 trueleft unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type 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 ocient system bootstrapping docid 4005nflvguw4fqfqa1spu ocient application configuration docid\ nneedy7yn8g1pennmamng