Start and stop Splunk UBA services from the command line
You can use some common command line interface (CLI) commands to perform the following administrative tasks in Splunk UBA:
Note: You must be logged in to the Splunk UBA management node as the caspida user to run these commands.
| Task | CLI Commands |
|---|---|
| Stop and start the Splunk UBA web interface. | Run the following commands on the management node:
|
| Stop and start the resource monitor services. | Run the following commands on the management node:
You can also |
| Synchronize configuration changes to all nodes in a distributed deployment. | In any distributed deployment, changes to the /etc/caspida/local/conf/uba-site.properties file must be synchronized to all nodes in the cluster. To do this, run the following command on the management node:
For information on setting Splunk UBA configuration properties, see Manage Splunk UBA configuration properties in the uba-site.properties file . |
Stop and start Splunk UBA services only on all nodes. The following services are stopped:
|
Run the following command on the management node:
|
Stop and start Splunk UBA services (listed with the /opt/caspida/bin/Caspida stop/start command) and all dependent platform services on all nodes:
|
Run the following command on the management node:
|
| Stop and start the Splunk UBA containers. | Run the following command on the management node:
|
| Stop and start the Splunk UBA data sources. | Run the following command on the management node:
|
| Check the version number of your Splunk UBA packages. | Run the following command on Ubuntu systems:
Run the following command on other supported Linux systems: |
| Get a list of the nodes in your Splunk UBA cluster. |
|