How do you ensure a deployment client's .conf files are running with new changes?

[russell120]

Hi,

If I use push an update (.conf files) to deployment clients using my deployment server, how do I ensure those clients are running properly using those new .conf file changes? Do I have to manually rebuild the forwarder asset table? Restart splunkd on those clients? Something else?

[tiagofbmm · Accepted solution]

If you want to make sure the apps in the client are the same as the ones in the Deployment Server, you can check the serverclass.xml file under /opt/splunk/var/run.

There you'll see the last time the client got a push a what is the hash of the app. If for instance you changed something in an app on the Deployment Server, just run /opt/splunk/bin/splunk reload deploy-server and the hashes of each app are recomputed and the match of client and server hashes per app is done again, pushing it when there is a mismatch.