Notification of a critical issue with the cleanup_Agent.nsh script

Background

The standard method to clean up files from a TrueSight Server Automation RSCD Agent is to use the cleanupAgent BLCLI command.  This command is invoked by the out-of-the-box BSA Recommended Database Cleanup Script.

Sometimes, the cleanupAgent BLCLI command does not remove the expected files from a target server. In these cases, BMC Support provided the cleanup_Agent.nsh NSH script as a workaround to resolve these issues.

The cleanup_Agent.nsh NSH script does not use the cleanupAgent BLCLI command nor any other BLCLI command. This script can be used if both Application Server and RSCD Agent minimal versions are less than or equal to 20.02.

Problem

If certain errors occur during the execution of the cleanup_Agent.nsh script, the script might attempt to remove files from outside the intended STAGING_DIR, RSCD_TMP, or Transactions directories on the target server.

Solution

If you are currently using the cleanup_Agent.nsh script for RSCD Agent cleanup, BMC recommends that you contact BMC Support to obtain the updated version of the cleanup_Agent.nsh script.

This issue does not affect the cleanupAgent BLCLI command. If an environment is using the cleanupAgent BLCLI command to perform RSCD Agent cleanup, and is not running the cleanup_Agent.nsh NSH script, this flash may be safely ignored.

To determine whether the cleanup_Agent.nsh script is present in your TrueSight Server Automation environment, run the following grep command from an NSH prompt in your FileServer storage directory:

• The following output is displayed when the cleanup_Agent.nsh script is present:

  grep -iR cleanup_Agent.nsh *
  
  scripts/4140710.1_cleanup_Agent.nsh:# File Name: cleanup_Agent.nsh
  scripts/4140710.1_cleanup_Agent.nsh:# End of cleanup_Agent.nsh

• No output is displayed when the cleanup_Agent.nsh script is not present:
  

  # grep -iR cleanup_Agent.nsh *
  #