Error code 1302 after installing or upgrading a Linux detection server to DLP v11

Article Id: 160122
Status: Published
Updated On: 29-07-2014 04:54
Legacy Id: TECH220422
Products:
Data Loss Prevention Endpoint Prevent , Data Loss Prevention Network Monitor , Data Loss Prevention Network Prevent for Email , Data Loss Prevention Network Discover , Data Loss Prevention Network Prevent for Web , Data Loss Prevention Network Protect , Data Loss Prevention Endpoint Discover
Issue/Introduction:

After installing or upgrading a Linux detection server to DLP v11, one of the following Severe events is displayed in the Enforce console:

Code: 1302

Summary: File Reader failed to start

Detail: Error starting File Reader. /opt/Vontu/Protect/lib/native/libcontentextractionjni.so.11.0.0: liblog4cxx.so.10: cannot open shared object file: No such file or directory No incidents will be detected.

Detail: Error starting File Reader. /opt/Vontu/Protect/lib/native/libcontentextractionjni.so.11.0.0: libaprutil-1.so.0: cannot open shared object file: No such file or directory No incidents will be detected.

Entries similar to the following may also be found in FileReader0.log:

SEVERE: File Reader failed to start. Error starting File Reader. /opt/Vontu/Protect/lib/native/libcontentextractionjni.so.11.0.0: libaprutil-1.so.0: cannot open shared object file: No such file or directory No incidents will be detected.
Apr 5, 2011 3:29:52 PM com.vontu.messaging.FileReader stop

Another symptom is that no network interface options will be listed in the Network Interfaces section of the Packet Capture tab on the System > Servers > Overview > Configure Server screen.

Resolution:

If this is a new installation, install the Red Hat package "apr-util" and restart the Vontu Monitor service.

If this is an upgrade, ensure the Red Hat package "apr-util" is installed and run the post-upgrade script as described in step 10 on page 51 of the DLP v11 Linux Upgrade Guide.

Also, confirm that any upgrades or patches were applied using the "protect" user, rather than root. Similar errors also appear when file permissions on some directories are incorrect (some items are owned by root).