Splunk® User Behavior Analytics

Administer Splunk User Behavior Analytics

Clean up the standby system if you accidentally started Splunk UBA services

If you started Splunk UBA services on the standby system, the PostgreSQL logs can become very large and negatively affect performance.

Perform the follow tasks to work around this issue:

  1. Login to the management node on the standby system as the caspida user.
  2. Run the following command to stop Splunk UBA:
    /opt/caspida/bin/Caspida stop
  3. Run the following command to stop PostgreSQL:
    /opt/caspida/bin/Caspida stop-postgres
  4. As a user with root privileges, manually delete all the PostgreSQL logs on the PostgreSQL node. In 20-node deployments, PostgreSQL runs on node 2. In all other deployment sizes, PostgreSQL runs on node 1.

    PostgreSQL logs are located in /var/log/postgresql/*.

  5. Run the following command to start PostgreSQL:
    /opt/caspida/bin/Caspida start-postgres
  6. Follow the instructions in Set up the standby Splunk UBA system to set up replication in the standby system again. Make sure you do not start any Splunk UBA services in the standby system.
Last modified on 25 March, 2024
Perform maintenance on your Splunk UBA clusters using warm standby   Recover Splunk UBA after an outage

This documentation applies to the following versions of Splunk® User Behavior Analytics: 5.3.0, 5.4.0

Was this topic useful?

You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters