Installation

Upgrade from 6.5.2 to 6.6.2 introduced delayed Web Start

wayn23
Explorer

The config in version 6.5.2 enable the web UI to use standard port 8000. Upgraded to Splunk 6.6.2 following the recommended process and all proceeded as expected. However, now whenever a Splunk instance is restarted (Indexer or search head), there is about a 5 minute delay before it starts listening on port 8000. There is nothing indicating in the splunkd.log as to what is causing the delay. Once it starts listening on port 8000, then a login can occur and everything works as expected.
While not an actual error, does add extra elapsed when doing some configuration changes in Splunk that needs a reboot.
Any ideas on what is happening?

Thanks in advance
Wayne

0 Karma
1 Solution

teunlaan
Contributor

see https://answers.splunk.com/answers/545000/slow-splunkweb-startup-caused-by-splunk-instrument.html

"On a server which doesn't have access to the proxy, I just put the following in my splunk-launch.conf: "
QUICKDRAW_URL=0

View solution in original post

0 Karma

teunlaan
Contributor

see https://answers.splunk.com/answers/545000/slow-splunkweb-startup-caused-by-splunk-instrument.html

"On a server which doesn't have access to the proxy, I just put the following in my splunk-launch.conf: "
QUICKDRAW_URL=0

0 Karma

wayn23
Explorer

That resolved the issue. Thanks for the response!

0 Karma
Get Updates on the Splunk Community!

Detecting Cross-Channel Fraud with Splunk

This article is the final installment in our three-part series exploring fraud detection techniques using ...

Splunk at Cisco Live 2025: Learning, Innovation, and a Little Bit of Mr. Brightside

Pack your bags (and maybe your dancing shoes)—Cisco Live is heading to San Diego, June 8–12, 2025, and Splunk ...

Splunk App Dev Community Updates – What’s New and What’s Next

Welcome to your go-to roundup of everything happening in the Splunk App Dev Community! Whether you're building ...