topic Re: Restart required when disabling/enabling app in Deployment Architecture

Restart required when disabling/enabling app

SarahBOA — Tue, 18 Jun 2013 22:46:59 GMT

Prior to upgrading to Splunk version 4.3.6, we were able to disable a particular app and then re-enable it without it requiring a restart. After the upgrade, we are now required to restart the splunk instance after disabling or enabling the app. Nothing in the app has changed between the last restart and the disabling, so why am I being required to restart the instance? We need to be able to re-enable the app without a restart.

Thanks,
Sarah

Re: Restart required when disabling/enabling app

asimagu — Thu, 20 Jun 2013 04:19:43 GMT

Hi Sarah,

try only restarting splunkweb

$SPLUNK_HOME/bin/splunk restart splunkweb

Re: Restart required when disabling/enabling app

watsm10 — Thu, 20 Jun 2013 10:16:18 GMT

Try a debug/refresh. Stick it on the end of your URL.

e.g.

http://yoursplunkserver:8000/en-GB/debug/refresh

You may be prompted to log in.

EDIT
I meant to say that this method means that you don't need to restart splunk at all.