HTTP Status 404 error after installing or upgrading to DLP v11 on Linux

book

Article ID: 159653

calendar_today

Updated On:

Products

Data Loss Prevention Enforce

Issue/Introduction

After installing or upgrading to DLP v11 on Linux, you receive the error "HTTP Status 404 -" when trying to access the Enforce console.  One or both of the following errors are also present in the tomcat log:

Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'extractionProvider' defined in ServletContext resource [/WEB-INF/policy-objects-spring.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [com.vontu.cracker.NativeExtractionEngine]: Constructor threw exception; nested exception is java.lang.UnsatisfiedLinkError: /opt/Vontu/Protect/lib/native/libcontentextractionjni.so.11.0.0: libaprutil-1.so.0: cannot open shared object file: No such file or directory

Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'extractionProvider' defined in ServletContext resource [/WEB-INF/policy-objects-spring.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [com.vontu.cracker.NativeExtractionEngine]: Constructor threw exception; nested exception is java.lang.UnsatisfiedLinkError: /opt/Vontu/Protect/lib/native/libcontentextractionjni.so.11.0.0: liblog4cxx.so.10: cannot open shared object file: No such file or directory

Caused by: java.lang.UnsatisfiedLinkError:
/opt/Vontu/Protect/lib/native/libcontentextractionjni-11.1.0.so: libboost_thread-gcc41-mt-1_39.so.1.39.0: cannot open shared object file: No such file or directory

Resolution

If this is a new installation, install the Red Hat package "apr-util" and restart the Enforce services.

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.

Note that similar errors can appear after an upgrade to v11.1 from 11.0. In this case, the error can indicate missing symlinks for existing DLP libraries. The upgrade script creates those symlinks.