ViPR SRM: After the upgrade of SRM to 4.1.1 SNMP Device Discovery and compliance frontend not working

           

   Article Number:     504610                                   Article Version: 3     Article Type:    Break Fix 
   

 


Product:

 

ViPR Family,ViPR SRM 4.1

 

Issue:

 

 

SNMP Device Discovery and Compliance Frontend URL's doesn't work, they just return blank page after the upgrade to 4.1.1   
   
    Errors seen on Catalina logs;   
   
    Sep 21, 2017 10:35:37 AM org.apache.catalina.core.StandardContext startInternal   
    SEVERE: One or more listeners failed to start. Full details will be found in the appropriate container log file   
    Sep 21, 2017 10:35:37 AM org.apache.catalina.core.StandardContext startInternal   
    SEVERE: Context [/device-discovery] startup failed due to previous errors   
        
    Sep 21, 2017 10:36:19 AM org.apache.catalina.core.StandardContext startInternal   
    SEVERE: One or more listeners failed to start. Full details will be found in the appropriate container log file   
    Sep 21, 2017 10:36:19 AM org.apache.catalina.core.StandardContext startInternal   
    SEVERE: Context [/compliance-frontend] startup failed due to previous errors   
   
   
    Errors seen on Localhost logs;   
   
    21-Sep-2017 10:35:37.739 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.listenerStart Exception sending context initialized event to listener instance of class com.watch4net.apg.gui.servlet.ApplicationListener   
    java.lang.IllegalStateException: Can't create master accessor.   
    Caused by: javax.naming.NameNotFoundException: Name [jdbc/master] is not bound in this Context. Unable to find [jdbc].   
        
    21-Sep-2017 10:36:19.211 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.listenerStart Exception sending context initialized event to listener instance of class com.watch4net.apg.gui.servlet.ApplicationContextListener   
    java.lang.IllegalStateException: An error occurred notifying listeners !   
    Caused by: java.lang.IllegalStateException: An error occurred creating the datasource.   
    Caused by: javax.naming.NameNotFoundException: Name [jdbc/master] is not bound in this Context. Unable to find [jdbc].   
     
                                                           

 

 

Resolution:

 

 

Login to Frontend server via putty.   
   
    Navigate to the location:   
   
    /opt/APG/Web-Servers/Tomcat/Default/conf/Catalina/localhost   
   
    Edit the device-discovery.xml and compliance-frontend.xml files as below:   
   
   
    The device-discovery.xml file had the incorrect entry to the database entries;   
   
    <ResourceLink name="jdbc/master" global="jdbc/master" type="javax.sql.DataSource"/>   
   
    Changed it to    
   
    <ResourceLink name="dba/master" global="dba/master" type="com.watch4net.apg.gui.datasource.DatasourceConfiguration"/>   
   
   
   
    Compliance-frontend.xml file had incorrect master db configuration   
   
    <ResourceLink name="jdbc/master" global="jdbc/master" type="javax.sql.DataSource"/>   
   
    Changed it to    
   
    <ResourceLink name="dba/master" global="dba/master" type="com.watch4net.apg.gui.datasource.DatasourceConfiguration"/>   
   
   
   
    Restarted the tomcat and resolved the issue   
   
   
    Also, verify if the resource link entries are same as above in context.xml for both the modules under location:   
   
    context.xml for device-discovery:   
   
    /opt/APG/Web-Servers/Tomcat/Default/webapps/device-discovery/META-INF   
   
    context.xml for compliance-frontend:   
   
    /opt/APG/Web-Servers/Tomcat/Default/webapps/compliance-frontend/META-INF