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

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Mastering Threat Intelligence in ES 8.5, Splunk AI Assistant v2, and More from Splunk ...

Splunk Lantern is Splunk’s customer success center that provides practical guidance from Splunk experts on key ...

Break the Build: Inside the KubeDoom Lounge at .conf26

    You step up to the machine. The pixelated corridors of a certain 1993 FPS load in front of you, EMP Pulse ...

Splunk Auto Ingestion Parallel Pipeline Scaling

Why this feature matters Many Splunk environments experience ingestion pressure long before the host is fully ...