On a Linux detection server, the DLP FileReader process will not start, but stays in a "starting" state indefinitely.
DLP Detection Server in Linux (RHEL) OS - usually after fresh install or upgrade
The FileReader process requires several Linux library prerequisites. If some of these are not met, the process will be unable to invoke all of the necessary components for it to start completely.
Review the list of required Linux RPMs in related article TECH219031: What Linux RPMs are needed to install Symantec DLP?
To quickly check for this problem, try to invoke the content extractor (filter) manually from the command line. Log into the system using the user whose credentials are used for the DLP services (default is 'protect'), and run the following command:
If the command displays a list of options, then the libraries are installed correctly. If there is an error referring to a library file (commonly libstdc++.so.5), then some prerequisite library packages are not installed. The most common missing packages are the compat-libstdc++-296 and compat-libstdc++-33 libraries.
NOTE: In some cases, filter is not executable by protect - in this case, another error will appear when trying to run the file. To correct this, login with root credentials and issue the following commands:
chown protect:protect /opt/SymantecDLP/Protect/plugins/contentextraction/Verity/x86_64/filter chmod 750 /opt/SymantecDLP/Protect/plugins/contentextraction/Verity/x86_64/filter
Additionally, note that in versions of DLP 14.0 and earlier, that path to filter is different: /opt/SymantecDLP/Protect/lib/native/filter - please adjust as needed.