Restart LWF's to use new app deployed from deployment server

[chicodeme]

The deployment server deploys the apps just fine using the splunk reload deploy-server command. But once the app is on the LWF's, are you required to restart the LWF in order to get the app to start working?

Maybe it depends on the app, so lets pick the unix app(Splunk for Unix and Linux) from splunkbase.

Are you required to restart the LWF's as of version 4.1.6 in order for the deployed app to become active? Active.. meaning collecting data and sending it to the indexer.

I'm not on the recently released 4.1.7 yet.

[David · Accepted solution]

I believe the LWF is going to need a restart in order for it to pick up any new inputs. You should be able to do that with:

[global]
restartSplunkd=true 

in your serverclass.conf. (Or you can put it under any particular server stanza, if desired.)

Does that work for you?

[gkanapathy · Accepted solution]

Most app configurations that you would deploy to a LWF will require a restart of the LWF. (This is not so for, say, most search head configurations) If you add restartSplunkd to the app stanza, e.g.:

[serverClass:myclass:app:myspecialapp]
whitelist.0=server1
restartSplunkd=true

[chicodeme]

I didn't know of that option. Thanks I will try it out.

[David · Accepted solution]

I believe the LWF is going to need a restart in order for it to pick up any new inputs. You should be able to do that with:

[global]
restartSplunkd=true 

in your serverclass.conf. (Or you can put it under any particular server stanza, if desired.)

Does that work for you?

[chicodeme]

I didn't know of that option. Thanks I will try it out.