Skip to content
  • There are no suggestions because the search field is empty.

RSA-SMS service not starting in RSA NetWitness Platform due to corrupted discovery_cache.map file

Issue

rsa-sms service does not start even if systemctl start rsa-sms.service command used in Node-0(NwServer) and sms.log shows below error.
 
/opt/rsa/sms/logs/sms.log 
Caused by: org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [com.rsa.smc.esm.core.services.stats.discovery. DiscoveryCache]: Constructor threw exception; nested exception is java.lang.IllegalArgumentException: Last unit does not have enough valid bits
 
 

Cause

This issue is due to corrupted discovery_cache.map file.


Resolution

Follow the below steps to start rsa-sms service.
  1. Login to Node-0 (NwServer) putty with root credentials.
  2. Rename the old discover discovery_cache.map file as different name.
    sample commands:
    cd /opt/rsa/sms/
    mv discovery_cache.map old_discovery_cache.map_old
     
  3. Start rsa-sms service using systemctl start rsa-sms.service command.
  4. Verify rsa-sms service status using systemctl status rsa-sms.service command.
  5. Also, this creates new /opt/rsa/sms/discovery_cache.map automatically.

Product Details

RSA Product Set: RSA NetWitness Platform
RSA Product/Service Type: Security Analytics Server
RSA Version/Condition: 11.X
Platform: CentOS
O/S Version: 7

Summary

This document outlines the procedure to start rsa-sms service.


Approval Reviewer Queue

RSA NetWitness Suite Approval Queue