Sync the server and client
This documentation does not apply to the most recent version of Splunk. Click here for the latest version.
Contents
Sync the server and client
To sync the server with the clients, start the deployment server from the Splunk CLI:
./splunk start
Start the deployment clients from their Splunk CLIs. Use this command to start Splunk without a license prompt:
./splunk start --accept-license
After syncing, each client either picks up the multicast packet as sent out by the deployment server or polls the deployment server for configurations. Once the client receives configurations, it restarts splunkd.
To confirm that all clients received the configuration correctly, check from the deployment server by using ./splunk list deploy-clients . This lists all the deployment clients and the last time they were successfully synced.
Note: If you're running Splunk 3.4 or later and looking for instructions on enabling the Splunk light forwarder via the deployment server, go here.
Configuration changes
To make a configuration change after initial deployment, edit or add the appropriate file to the applicable server class subdirectory. By default, the server class directory is located on the deployment server in $SPLUNK_HOME/etc/modules/distributedDeployment/classes/. For a list of configuration files, see the configuration file reference.
After you finish editing configuration files, alert the deployment server of the change via the Splunk CLI. To use Splunk's CLI, navigate to the $SPLUNK_HOME/bin/ directory and use the ./splunk command. You can also add Splunk to your path and use the splunk command.
./splunk reload deploy-server
This command checks all server classes for a change, and notifies clients.
-or-
./splunk reload deploy-server -class $SERVER_CLASS
This command notifies and updates only the specified server class. For example:
./splunk reload deploy-server -class www
This command notifies and updates only www server class clients.
Once a client receives configurations, it restarts splunkd.
Confirm the sync
To confirm that all clients received the configuration correctly, check from the deployment server by using ./splunk list deploy-clients . This lists all the deployment clients and the last time they were successfully synced.
This documentation applies to the following versions of Splunk: 3.3 , 3.3.1 , 3.3.2 , 3.3.3 , 3.3.4 , 3.4.1 , 3.4.2 , 3.4.3 , 3.4.5 , 3.4.6 , 3.4.8 , 3.4.9 , 3.4.10 , 3.4.11 , 3.4.12 , 3.4.13 , 3.4.14 View the Article History for its revisions.