(SM) Support Tip SRC - ’Browse catalog’ option not visible in server and support catalog
SRC - Not getting Browse catalog option in service and support catalog
It is a typical issue in SRC. Please follow the guide below for troubleshooting.
Clean SRC cache, and then check if the issue persists.
- Stop Tomcat
- Delete all log files from the web application server e.g. If using Apache Tomcat the directory would be C:\Program Files\Apache Software Foundation\Tomcat 7.0\logs
- Delete the web application server cache e.g. If using Apache Tomcat the directory would be C:\Program Files\Apache Software Foundation\Tomcat 7.0\work
- Delete the src4csadb folder e.g. If using Apache Tomcat the directory would be C:\Program Files\Apache Software Foundation\Tomcat 7.0\src4csadb
- Delete all files\folders in the <SRC INSTALL DIRECTORY>\secure\attachments folder
- Delete the SRC lucene index i.e. delete the folder in <SRC INSTALL DIRECTORY>\secure\luceneIndexedData
- Start Tomcat and wait for 4-5 min.
Enable the debug parameters in SRC and SM server, and collect the trace.
- Stop SM server and SRC.
- For SM log, Edit Server\RUN\sm.ini:
For SRC log, Edit \WEB-INF\classes\log4j.properties:
Change log4j.rootLogger=INFO, stdout, rolling to log4j.rootLogger=DEBUG, stdout, rolling
Change log4j.logger.httpclient.wire=INFO to log4j.logger.httpclient.wire=DEBUG
Backup and clean all log files in SRC (SRC tomcat/logs/server.log) and SM (SM server/logs).
Start SM server and SRC.
Reproduce the issue and write down the time as reproducing.
Send back all log files in SRC (SRC tomcat/logs/server.log) and SM (SM server/logs) and the reproduce time.
HPE SM support would further the investigation by analyzing the log. Share one of the potential root causes, it is a credential issue because the SRC trace looks like this,
25 Nov 2016 10:40:53,228 FATAL [localhost-startStop-1] (CatalogLifecycleManagerImpl.java:594) - [Load Catalog: sm ] Error authenticating catalog org.springframework.security.authentication.UsernamePasswordAuthenticationToken@df35a654: Principal: falcon; Credentials: [PROTECTED]; Authenticated: false; Details: org.springframework.security.authentication.AuthenticationDetails@6ca2769a: Context: sm; Not granted any authorities. *Root cause*: com.hp.siberia.exception.ServiceException: Incorrect credentials
com.hp.siberia.exception.ServiceException: Incorrect credentials
To correct it, try to set the password of falcon to “”.
- Go to falcon operator in SM, set the password to empty, save it, logout and login for validation.
- Go to SRC\WEB-INF\classes\applicationContext.properties, set as sm.adminCredentials=LIST(falcon,)
- Clean the cache in SRC as above and restart SRC tomcat.
If non-empty password is to be set, please follow how to use the password encryptor in SRC section in SM release notes.