Alerting

Web interface doesn't loads in 4.2

drubio
New Member

I've got a problem after upgrading to 4.2... I can't access splunk because de home page doesn't finish loading.

I've tried with different browsers, but it doesn't works, the source code is there, but nothing is shown.

There's nothing strange on the logs, and if I stop the server, there are a pair of remaining splunk process like this:

python -O /usr/loca/splunk/lib/python2.6/site-packages/splunk/appserver/mrsparkle/

If I kill this process, then the page finish loading and is shown...

Some idea? maybe something phyton-related?

Tags (1)
0 Karma

Stephen_Sorkin
Splunk Employee
Splunk Employee

You should probably file a support case to track this issue, as it sounds like a bug. You could try disabling JS/CSS minification by adding the following to $SPLUNK_HOME/etc/system/local/web.conf:

[settings]
minify_js = false
minify_css = false

sideview
SplunkTrust
SplunkTrust

It's also possible that two apps on your system have a custom module by the same name -- I believe in 4.2 that scenario locks up SplunkWeb much in the way you describe.

0 Karma
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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Build resilience for the agentic era: Join us at Splunk Go San Jose

AI is changing how organizations build, operate, and secure digital services. As teams adopt AI agents and ...

Manage Edge Processor pipelines end to end with APIs

This guide uses the Data Management APIs to create an Edge Processor, onboard one instance, deploy a pipeline ...