Troubleshoot Host CLI Action Failures

If a Host CLI Action fails, you can use the following checklist for areas to check:

• While testing, use .? for your success (success_match:.?) criteria:
  • This regular expression matches to any character, either 0 times or one time.
  • This configuration allows the command to run and continue to the next command regardless of the returned value.
  • This configuration lets you separate testing of the commands and success criteria.
• Check to ensure that dependent files are correct:
  • Verify that the file hash matches the intended file.
  • Verify that you loaded the correct file into the Director.
  • If there are multiple dependencies, verify that the correct file is being called.
  • Verify that the file name in the Action configuration matches what's referenced in the CLI.
  • Verify that the path for the initial load to disk location is correct and matches where it’s referenced in the CLI.
  • As a best practice, use full paths and not relative paths.
• If you see %errorlevel% or any unexpected 0 value in the CLI log:
  • Give the Action more time to execute.
  • Examine the prompt regular expression.
• If you don't see any CLI log information, check for special characters in the description.
• Verify whether the file has any anti-forensic or anti-sandbox detection that could prevent it running in the Security Validation platform.