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!

Introducing Splunk Enterprise 9.2

WATCH HERE! Watch this Tech Talk to learn about the latest features and enhancements shipped in the new Splunk ...

Adoption of RUM and APM at Splunk

    Unleash the power of Splunk Observability   Watch Now In this can't miss Tech Talk! The Splunk Growth ...

Routing logs with Splunk OTel Collector for Kubernetes

The Splunk Distribution of the OpenTelemetry (OTel) Collector is a product that provides a way to ingest ...