Data Loss Prevention

 View Only
Expand all | Collapse all

While accessing DLP's web console an error "HTTP Status 404" is displayed

  • 1.  While accessing DLP's web console an error "HTTP Status 404" is displayed

    Posted Dec 17, 2012 07:01 AM
      |   view attached

    I have done fresh installation of Symantec DLP 11.1 on Red Hat. It is three tier installation with Enforce, Database and Detection Servers on different machines. I have installed Oracle client on Enforce Server and it can successfully connect to Oracle Database(Windows Server 2008 R2) through sqlplus.

    All the Vontu services are running. Furthermore "apr-util" package is also installed on Red Hat. When accessing the DLP Web console in browser i am getting the following error "HTTP Status 404. The requested resource () is not available". I have attached the tomcat log file. Please help.

    Attachment(s)

    txt
    localhost.2012-12-18.txt   41 KB 1 version


  • 2.  RE: While accessing DLP's web console an error "HTTP Status 404" is displayed

    Posted Dec 17, 2012 07:03 AM

    Hi,

    Check this same thread

    https://www-secure.symantec.com/connect/forums/dlp-web-access-shows-error-http-status-404



  • 3.  RE: While accessing DLP's web console an error "HTTP Status 404" is displayed

    Posted Dec 17, 2012 07:34 AM

    Ashish i have already checked that post before posting this query. Unfortunately it doesn't list any solution.



  • 4.  RE: While accessing DLP's web console an error "HTTP Status 404" is displayed



  • 5.  RE: While accessing DLP's web console an error "HTTP Status 404" is displayed

    Posted Dec 18, 2012 01:21 AM

    Thanks Asish. But let me mention that i have searched the forums for all the related posts including this. None of the recommendations work. Furthermore my problem is not related to Vontu Incident Persister. All the services are running correctly. If we observe the logs the problem starts here

     

    "18 Dec 2012 16:23:32,086- 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-11.1.0.so: libldap-2.3.so.0: cannot open shared object file: No such file or directory

    at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:254)

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:925)

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:835)

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:440)

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)

    at java.security.AccessController.doPrivileged(Native Method)

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380)

    at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:264)

    at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)

    at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:261)

    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:185)

    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164)

    at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:429)

    at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:728)

    at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:380)

    at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:255)

    at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:199)

    at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45)

    at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3795)

    at org.apache.catalina.core.StandardContext.start(StandardContext.java:4252)

    at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:760)

    at org.apache.catalina.core.ContainerBase.access$000(ContainerBase.java:122)

    at org.apache.catalina.core.ContainerBase$PrivilegedAddChild.run(ContainerBase.java:144)

    at java.security.AccessController.doPrivileged(Native Method)

    at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:738)

    at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:544)

    at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:980)

    at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:943)

    at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:500)

    at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1203)

    at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:319)

    at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:120)

    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1022)

    at org.apache.catalina.core.StandardHost.start(StandardHost.java:736)

    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014)

    at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)

    at org.apache.catalina.core.StandardService.start(StandardService.java:448)

    at org.apache.catalina.core.StandardServer.start(StandardServer.java:700)

    at org.apache.catalina.startup.Catalina.start(Catalina.java:552)

    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

    at java.lang.reflect.Method.invoke(Method.java:597)

    at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:295)

    at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:433)

    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

    at java.lang.reflect.Method.invoke(Method.java:597)

    at org.tanukisoftware.wrapper.WrapperStartStopApp.run(WrapperStartStopApp.java:243)

    at java.lang.Thread.run(Thread.java:619)

    Caused by: 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-11.1.0.so: libldap-2.3.so.0: cannot open shared object file: No such file or directory

    at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:115)

    at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:87)

    at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:248)

    ... 50 more

    Caused by: java.lang.UnsatisfiedLinkError: /opt/Vontu/Protect/lib/native/libcontentextractionjni-11.1.0.so: libldap-2.3.so.0: cannot open shared object file: No such file or directory

    at java.lang.ClassLoader$NativeLibrary.load(Native Method)

    at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1803)

    at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1699)

    at java.lang.Runtime.load0(Runtime.java:770)

    at java.lang.System.load(System.java:1003)

    at com.vontu.cracker.jni.JniLoader.loadLibrary(JniLoader.java:32)

    at com.vontu.cracker.jni.NativeObject.<clinit>(NativeObject.java:10)

    at com.vontu.cracker.jni.EngineContext.<init>(EngineContext.java:13)

    at com.vontu.cracker.NativeExtractionEngine.<init>(NativeExtractionEngine.java:39)

    at com.vontu.cracker.NativeExtractionEngine.<init>(NativeExtractionEngine.java:23)

    at com.vontu.cracker.NativeExtractionEngine.<init>(NativeExtractionEngine.java:17)

    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)

    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)

    at java.lang.reflect.Constructor.newInstance(Constructor.java:513)

    at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:100)

    ... 52 more"



  • 6.  RE: While accessing DLP's web console an error "HTTP Status 404" is displayed

    Broadcom Employee
    Posted Dec 18, 2012 01:22 AM

    try to stop and start the services in the sequence and let know if it helps

     

    • How to stop the Manager Vontu Services:

                1. Vontu Monitor Controller (if applicable)
                2. Vontu Incident Persister
                3. Vontu Manager
                4. Vontu Notifier
                5. Vontu Update (if necessary)

    How to start the Manager Vontu Services:

                1. Vontu Notifier
                2. Vontu Manager
                3. Vontu Incident Persister
                4. Vontu Monitor Controller (if applicable)
                5. Vontu Update (if necessary)

     



  • 7.  RE: While accessing DLP's web console an error "HTTP Status 404" is displayed

    Posted Dec 18, 2012 04:55 AM

    @pete_4u2002

    I have already done these steps but they didn't help either. Kindly suggest what should further be done to resolve this problem.



  • 8.  RE: While accessing DLP's web console an error "HTTP Status 404" is displayed

    Posted Dec 18, 2012 05:03 AM

    Hi,

    If you have try all of you can rasied support ticket.



  • 9.  RE: While accessing DLP's web console an error "HTTP Status 404" is displayed

    Posted Feb 03, 2013 09:38 AM

    have you disabled selinux?  what version of redhat are you using?  



  • 10.  RE: While accessing DLP's web console an error "HTTP Status 404" is displayed

    Broadcom Employee
    Posted Feb 04, 2013 05:55 AM

    Hi jawad1987

    I realise you’ve run through the documentation and I suspect this issue has been resolved, but if no, it’s best to verify that the following RPMs are installed (DLP System Requirements 11.1 p33)

    • apr
    • apr-util
    • binutils
    • compat-libstdc++-296
    • compat-libstdc++-33
    • expat
    • Xorg-x11

    Looking at similar (sorry can’t find the exact) error message

    "Caused by: java.lang.UnsatisfiedLinkError: /opt/Vontu/Protect/lib/native/libcontentextractionjni-11.1.0.so: libldap-2.3.so.0: cannot open shared object file: No such file or directory"

    libldap-2.3.so.0 is the issue

    This could result from it not being present, symlinks being wrong or a permissions issue.

    Away from this, I’d suggest logging with support as I'm at my knowledge's end! (please let them know the RH version you’re running with).

    Kind regards
    David



  • 11.  RE: While accessing DLP's web console an error "HTTP Status 404" is displayed

    Posted Feb 05, 2013 07:36 AM

    Hi,

    I have faced this issue after upgrade and i ran script /opt/SymantecDLP/Protect/install/11.6.1_Upgrade_Resources/11.6_upgrade_root_script.sh and restart the Detection server services.  I am also using linux 5.9 version and now it is working fine for me... So try and check whether is working for you or not.

     

    Regards,

    Amol



  • 12.  RE: While accessing DLP's web console an error "HTTP Status 404" is displayed

    Posted Feb 05, 2013 10:20 AM

    @fivelakes SELinux was already disabled

     

    @davjoh I logged a case with Symantec Support a while ago. And they said that issue was related to Red Hat 6 not being offically supported. And my installation was on Red Hat 6. So i reverted back to Red Hat 5.7 and issue was resolved. Its a bit strange i still have one testing envoirnment which is on Red Hat 6 and every thing is running smoothly.



  • 13.  RE: While accessing DLP's web console an error "HTTP Status 404" is displayed

    Posted Feb 05, 2013 10:23 AM
    Amol from where can one get the updated packages for 11.6 etc? Because when i log onto File Connect it only shows me the DLP 11.1 Installation packages.


  • 14.  RE: While accessing DLP's web console an error "HTTP Status 404" is displayed

    Broadcom Employee
    Posted Feb 05, 2013 10:45 AM
    are you still under DLP support entitlement? if yes, contact Symantec customer care.