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!

Detecting Remote Code Executions With the Splunk Threat Research Team

WATCH NOWRemote code execution (RCE) vulnerabilities pose a significant risk to organizations. If exploited, ...

Enter the Splunk Community Dashboard Challenge for Your Chance to Win!

The Splunk Community Dashboard Challenge is underway! This is your chance to showcase your skills in creating ...

.conf24 | Session Scheduler is Live!!

.conf24 is happening June 11 - 14 in Las Vegas, and we are thrilled to announce that the conference catalog ...