000035307 - How to reset the Licensing Server (LLS / FNE) in RSA NetWitness Logs & Network versions 10.5.x and 10.6.x

Document created by RSA Customer Support Employee on Jul 14, 2017Last modified by RSA Customer Support on Jul 16, 2019
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000035307
Applies ToRSA Product Set: RSA Netwitness Logs & Network
RSA Product/Service Type: SA Server
RSA Version/Condition: 10.5.x, 10.6.x
Platform: CentOS
O/S Version: EL6
IssueThe following steps will allow you to reset the licensing server in RSA NetWitness Logs & Network when running into various licensing issues.
ResolutionSSH into the SA Server appliance and execute the following commands:
  1. Log into the mongo sa database:

    # mongo sa

  2. Display the list of collections:

    > show collections

  3. Remove all of the entries within the entitlement collection in mongo and then exit mongo:

    > db.entitlement.remove()
    > exit

  4. Check the status of the fneserver service, and stop the service if it is currently running:

    # service fneserver status

    You may run into the following error - "lock file found but no process running for pid <pid>" when checking the fneserver service status. If so, please follow KB #000033227  to resolve this issue, and then continue below with Steps 5-11 below.
  5. Stop the fneserver service if it is currently running:

    # service fneserver stop

  6. Export the LD_LIBRARY_PATH environment variable to append the path /opt/fneserver/lib:

    # export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/fneserver/lib

  7. Reset the trust store for the license server:

    # /opt/fneserver/bin/fneserver reset

  8. Navigate to the fneserver library directory:

    # cd /var/lib/fneserver

  9. If you list the files in the directory, there will be license stub files within the directory that begin with "ra". Clear the license stub files beginning with "ra" from the directory - be sure you are in the /var/lib/fneserver directory before clearing these files: 

    # rm -rf ra*

  10. Start the fneserver service:

    # service fneserver start

  11. Upload a new response file into the RSA Security Analytics UI using the following steps: https://community.rsa.com/docs/DOC-45428