Security

Splunkweb consumes large amounts of memory and appears to hang

ahattrell_splun
Splunk Employee
Splunk Employee

On restart splunkweb starts up, but does not respond to attempts to connect via web. Nestat showed that we were listening on the port.

Over the course of half an hour splunkweb gradually consumed all memory on the box (24 Gb).

If you attempted to restart - splunkweb wouldn't respond before the timeout and would therefore be killed.

Splunk was version 4.3.1.

Tags (1)
1 Solution

ahattrell_splun
Splunk Employee
Splunk Employee

Turned out this was caused by a known bug SPL-48237.

The problem is that Splunk doesn't always clear up the session lock files found within {splunk install}/var/run/splunk. We had many thousands of these session lock files that SplunkWeb was trying to process.

Deleting the files manually allowed splunkweb to restart. Fixed in 4.3.4 and later.

View solution in original post

ahattrell_splun
Splunk Employee
Splunk Employee

Turned out this was caused by a known bug SPL-48237.

The problem is that Splunk doesn't always clear up the session lock files found within {splunk install}/var/run/splunk. We had many thousands of these session lock files that SplunkWeb was trying to process.

Deleting the files manually allowed splunkweb to restart. Fixed in 4.3.4 and later.

Get Updates on the Splunk Community!

Fastest way to demo Observability

I’ve been having a lot of fun learning about Kubernetes and Observability. I set myself an interesting ...

September Community Champions: A Shoutout to Our Contributors!

As we close the books on another fantastic month, we want to take a moment to celebrate the people who are the ...

Splunk Decoded: Service Maps vs Service Analyzer Tree View vs Flow Maps

It’s Monday morning, and your phone is buzzing with alert escalations – your customer-facing portal is running ...