000032777 - Malware Service is not up when deployed using fresh install ISO for RSA Security Analytics 10.6

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000032777
Applies ToRSA Product Set: Security Analytics
RSA Product/Service Type: Security Analytics Server
RSA Version/Condition: 10.6
Platform: CentOS 6
 
IssueWhen deploying a new ISO, Malware CoLo is not up in the Security Analytics UI (not coloured in green) while the service is up from the SSH connection.
 

Steps to Reproduce


  1. Deploy the Security Analytics using the ISO December- 14th - 2015 Image.
  2. Make sure Provision is successful.


Actual Behaviour


  1. When Logged into SA, malware colo is not up (Not Coloured in Green) and the service is up when SSH connection.
  2. So navigated to SA-Malware and Edit, Checked for Test Connection – Test Connection was Failing.
  3. In Spectrum log Autowired exception is logged.
 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)

  1. When user stops and starts the rsaMalwareDevice service the Malware service will be up in the Security Analytics UI as well now.

 


Expected Behaviour


  1. As soon as user deploys the ISO and selects the Security Analytics Server, the Malware service must be up with out user interruption.
ResolutionAs a workaround, After the deployment, wait 30 minutes (for Puppet to run and set the Carlos keystone properly) and then restart the Malware service.
restart rsaMalwareDevice

Attachments

    Outcomes