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!

More Ways To Control Your Costs With Archived Metrics | Register for Tech Talk

Tuesday, May 14, 2024  |  11AM PT / 2PM ET Register to Attend Join us for this Tech Talk and learn how to ...

.conf24 | Personalize your .conf experience with Learning Paths!

Personalize your .conf24 Experience Learning paths allow you to level up your skill sets and dive deeper ...

Threat Hunting Unlocked: How to Uplevel Your Threat Hunting With the PEAK Framework ...

WATCH NOWAs AI starts tackling low level alerts, it's more critical than ever to uplevel your threat hunting ...