Deployment Architecture

Restart required when disabling/enabling app

SarahBOA
Path Finder

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

0 Karma

watsm10
Communicator

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.

asimagu
Builder

Hi Sarah,

try only restarting splunkweb

$SPLUNK_HOME/bin/splunk restart splunkweb

Get Updates on the Splunk Community!

Stay Connected: Your Guide to May Tech Talks, Office Hours, and Webinars!

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars this month. This ...

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...