Checking System After Configuration

the postcheck command helps capture critical node health states and metrics after the {{ocient}} configuration process you can run the command as shown in this example the flags included after the precheck command are optional see docid\ zkuyotmhjcmjcq3vwr0je for descriptions $ sudo /usr/local/bin/postcheck dsn ocient //ur sql0 4050/system;user=admin\@system;password=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) with the option to send a text file or a json file to specify the file option, use this flag logfile location \<directory> where \<directory> is the directory where the postcheck command creates the log file before you begin, ensure that all steps in the docid\ jcwkla4nvk4sjcxhcriy0 process are complete prerequisites the script requires {{java}} and the ocient jdbc jar to run in most cases, you should use this script on client servers rather than database nodes to get the post check script onto a client, perform the scp operation on the wheel onto the server and run python3 m pip install no index \<path to wheel>/postcheck whl , and replace \<path to wheel> with the path to the directory of the wheel file on your server flags for command execution use the postcheck command to run the script that checks the system configuration after you configure ocient you can execute the command using these flags 100,83,77,91,185,241 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 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 \ foundation nodes storage are non uniform os configuration ok \================ huge page settings ok isolcpus settings ok memory ok \====== foundation nodes 1024 gb sql nodes 1024 gb loader nodes 1536 gb total dram 123120 gb this example shows output in json format {"status" 2, "components" { "firmware" { "status" 0, "message" "success nvme drive firmware is consistent across nodes " } "symmetry" { "status" 2, "message" "warning non uniform configuration " "storage" { "status" 2, "foundation" { "status" 0, "message" "success storage consistent across foundation nodes " "foundation1" 16tb, } } } related links docid\ jcwkla4nvk4sjcxhcriy0 docid q3srqnu4dww9on6fldj