blcli Delete cleanupObsoleteFilesFromFileServer command


Important

This flash supersedes theearlier flash dated April, 2020.


BMC Software is alerting users to a serious problem that requires immediate attention in versions 23.4, 23.2, 23.1, 22.2 and 21.3 of the TrueSight Server Automation product. If you have any questions about the problem, contact Customer Support.

June 14, 2022

Issue

This issue occurs when you run the blcli command Delete cleanupObsoleteFilesFromFileServer. When certain conditions are met, files and directories in the root of the file server location are erroneously deleted. If you subsequently attempt to access the affected files from TrueSight Server Automation after running the cleanupObsoleteFilesFromFileServer command, the following error message is displayed: filesystem object not found.

This blcli command is provided as a way to perform file server cleanup in situations when other database cleanups are not completing and is not the normal command used to cleanup the file server.  The normal blcli command for file server cleanup,  Delete  cleanupFileServer , is not affected by this problem.

Important

The Delete cleanupObsoleteFilesFromFileServer command is not part of the out-of-the-box database or file server cleanup script by default. However, if the command has been added manually to any out-of-the-box script or any other custom script you are using, it would run automatically when you run the script. Therefore, locate the cleanup scripts in your environment and ensure that this command is not being run as part of the scripts by performing the following steps:

  1. Navigate to the Depot workspace and locate any database or file server cleanup scripts which are being executed in your environment. For example, the following image shows the BSA Recommended Database Cleanup Script:
    CleanUpScript.png
  2. Right-click the script and select the editor to open it. 
  3. Search for cleanupObsoleteFilesFromFileServer.
  4. If no occurrences of cleanupObsoleteFilesFromFileServer are found in the script, the command is not being run by the script. If an occurrence is found, unschedule the job, and contact BMC Support for assistance.
  5. Repeat steps 1 through 4 for any other database or file server cleanup scripts being used in your environment (for example, Daily Cleanup or Weekly Cleanup).

Resolution

BMC is currently working on a fix for this issue and will release a patch as soon as possible.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*