To get a more detailed error message on why the content extraction engine cannot start we will launch it manually as the “protect” linux user.
Sudo into the protect linux user with command su - protect
Navigate to the content extraction engine default path: /opt/SymantecDLP/Protect/lib/native folder.
Run the content extraction engine manually with the ./ceh command as protect user.
The content extraction engine will throw a more detailed error on why it cannot start, 90% of the time it is missing a library or .so file, it will tell you which one. You can run lld ceh command to see what libraries are missing as well.
You will have to then install the RPM that contains the missing library, once this is done run the ./ceh command again, and if it returns a blank screen without any errors, it has loaded correctly and is ready to run.
You may start the VontuMonitor service now on the detection server and monitor the Filereader log when starting with the > tail-f /var/log/SymantecDLP/debug/FileReader0.log file command.
Subscribing will provide email updates when this Article is updated. Login is required.