Notification of a critical issue with the cleanup_Agent.nsh script
BMC Software is alerting users of TrueSight Server Automation to a critical issue with the cleanup_Agent.nsh NSH script.
The standard method to clean up files from a TrueSight Server Automation RSCD Agent is to use the . This command is called by the out of the box BSA Recommended Database Cleanup Script.
Some customers have reported issues with the cleanupAgent BLCLI command not removing the expected files from a target server. In these cases, Customer 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.
The cleanup_Agent.nsh NSH script is compatible with all the of BMC Server Automation and TrueSight Server Automation.
If certain error conditions occur while the cleanup_Agent.nsh script is executing, the script may attempt to remove files from outside the intended STAGING_DIR, RSCD_TMP or Transactions directories on the target server.
If you are currently using the cleanup_Agent.nsh script for RSCD Agent cleanup, BMC recommends that you contact Customer Support in order to obtain the updated version (v3) 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:
Example where 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
Example where cleanup_Agent.nsh script is not present:
# grep -iR cleanup_Agent.nsh * #