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!

Index This | I am a number, but when you add ‘G’ to me, I go away. What number am I?

March 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...

What’s New in Splunk App for PCI Compliance 5.3.1?

The Splunk App for PCI Compliance allows customers to extend the power of their existing Splunk solution with ...

Extending Observability Content to Splunk Cloud

Register to join us !   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to ...