Buildup of Temp Files on Secondary DLP OCR Servers
- Article Number: 000018821
- Products: Forcepoint DLP
- Version: 8.7, 8.6, 8.5
- Last Published Date: July 31, 2020
Notes & Warnings
Note For version 8.6 of DLP, there is a known issue with the OCR Server described in the following article:
8.6 OCR Performance Issues
On a secondary DLP Server with the OCR Server installed, temporary files are being written to one or more of the following directories and not being cleaned up:
The boost_interprocess folder is used by the process pool (Boost), which in turn is used by the OCR Server service. Every process poll creates these temporary files per several requests, and eventually these files should be deleted. In general, the number of files in the boost_interprocess folder should roughly match the number of threads being used by the OCR Server process, and if the OCR service restarts, then the files are deleted and new ones are created.
The build up of files in the boost_interprocess folder may be related to crashes happening on the OCR server. For 8.5.x versions of DLP, this may be related to the HealthCheck script with a potential fix. In general, upgrading to the latest DLP version will include improvements made to the HealthCheck over time.
For immediate relief, the temporary files can be manually deleted from these directories after stopping the Websense Data OCR Engine (OCRServer) service. If your environment does not use the OCR Server at all, the service can be disabled if desired. Please confirm beforehand on the System Modules page under each Policy Engine in your network that the OCR Server is not actively in use and System Health shows that OCR analysis isn't being performed. If this is the case, then you can disable the service.
In general, please confirm that the following configuration changes are in place:
Configuring and Troubleshooting OCR DLP
Keywords: DLP Data Security; OCR Server; Optical Character Recognition; Secondary Server Issue; High CPU RAM Resource Utilization; Temp File Buildup; Boost Interprocess; TempFiles;