Article Content
Article Number | 000032777 |
Applies To | RSA Product Set: Security Analytics RSA Product/Service Type: Security Analytics Server RSA Version/Condition: 10.6 Platform: CentOS 6 |
Issue | When deploying a new ISO, Malware CoLo is not up in the Security Analytics UI (not colored in green) while the service is up from the SSH connection. Steps to Reproduce
2015-12-15 06:17:45,545 [main] ERROR org.springframework.web.context.ContextLoader - Context initialization failed org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'transientValueInjectorBean': Injection of autowired dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could not autowire field: private com.netwitness.malware.server.repository.Repository com.netwitness.malware.server.domain.TransientValueInjectorBean.repository; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'repository': Injection of autowired dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could not autowire field: private com.rsa.netwitness.ma.client.service.CommunityService com.netwitness.malware.server.repository.DefaultRepository.communityService; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'httpCommunityService' defined in class path resource [META-INF/applicationContextCommunityClient-context.xml]: Cannot resolve reference to bean 'communityHttpsClient' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'communityHttpsClient' defined in class path resource [META-INF/applicationContextCommunityClient-context.xml]: Invocation of init method failed; nested exception is java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: SunJSSE, class: sun.security.ssl.SSLContextImpl$DefaultSSLContext)
Expected Behaviour
|
Resolution | As a workaround, After the deployment, wait 30 minutes (for Puppet to run and set the Carlos keystone properly) and then restart the Malware service.
|