000017207 - RSA Security Analytics UI will not come up after an upgrade to 10.4.x from 10.3.x

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 Number000017207
Applies ToRSA Security Analytics
RSA Security Analytics 10.3.x
RSA Security Analytics 10.4.x
RSA Security Analytics Server
Puppet
MongoDB
IssueRSA Security Analytics UI will not come up after an upgrade to 10.4.x from 10.3.x.
Error message "Certificate is not matching" is displayed in the /var/log/messages file.
CauseThis issue occurs because Puppet did not identify the correct ID of the puppet master, being the Security Analytics Server.  This results in no puppet connections coming up.
Resolution

Puppet may occasionally get the wrong certificate and no services will work.  To resolve the issue, follow the steps below.


  1. Connect to the Security Analytics server appliance via SSH as the root user.
  2. Navigate to the /etc/puppet/scripts directory.
  3. Issue the following command to identify the node:  ./node_id.py
  4. Issue the following command to list the certificates in use:  puppet cert list --all
  5. Stop the Puppet services with the following commands:

    1. service puppetmaster stop
    2. service puppet stop
  6. Clean out the bad certificate with the following command:  cert clean <node_id>
  7. Start the Puppet services with the following commands:

    1. service puppetmaster start
    2. service puppet start
  8. After performing the steps above, Puppet should now pick up the correct node ID.  Verify this with the following command:  ./node_id.py
  9. Check to see if therea are any new errors by monitoring the messages file for a time with the following command:  tail -f /var/log/messages
  10. Add the correct node to MongoDB with the following command:  ./mongo_enc.py `./node_id.py`

After completing this procedure, all services should now be operational.


 


If you are unsure of any of the steps above or experience any issues, contact RSA Support and quote this article ID for further assistance.

Legacy Article IDa68042

Attachments

    Outcomes