Hi;
We are currently setting up multiple new forwarders, which are getting their configs from the deployment server.
Everytime, we setup a new app or modify an existing app we are having to restart splunk.
Is there an easier way to re-initialise the Deployment Server to refresh the /opt/splunk/var/run/tmp/ sub-folders without having to do a "service restart splunk"
Trevor..
Yes , You can create a server class for restart . Add the restart app and clients for it.
It will work like smooth
You might want to look at https://splunkbase.splunk.com/app/2775/
it has a relod deploy server as well as restart forwarder feature.
If you are getting this error
An error occurred: Could not create Splunk settings directory at '/root/.splunk'
Then make sure you run the process as the user you typically run splunk from. splunk in my case.
sudo su splunk
[splunk@servername5001 /opt/splunk/etc](603)
$ /opt/splunk/bin/splunk reload deploy-server
Your session is invalid. Please login.
Splunk username: admin
Password:
Login successful, running command...
Reloading serverclass(es).
[splunk@servername /opt/splunk/etc](604)
I have a dummy app that I push when I want to make changes. Just add that app and next check in all updated apps get pushed.
Great, help out and accept the right answer or post a better one.
Bingo. We have success.
Thanks Peoples.. 🙂
Should be able to reload the configs by accessing http://yoursplunkinstance/en-US/debug/refresh
that takes longer time, and it reloads a bunch of other stuff. I think it's generally better suited for reloading props/transforms stuff that would normally require a restart.
According to http://wiki.splunk.com/Deploy:DeploymentServer it is $SPLUNK_HOME/bin/splunk reload deploy-server
There is other information there but I think that answers you question.
For larger deployments, I think it's better to use the -class switch
${SPLUNK_HOME}/bin/splunk reload deploy-server -class
This helped me a lot. Thank You!
Big fan of reload deploy-server
myself.
Can anyone second that this is the endpoint for the command?
/services/deployment/client/config/reload -X POST