Splunk Search

"StatsFileWriterLz4 file open failed" error after upgrade to 8.2.3 when searching

podegard
Engager

After upgrading our environment from 8.1.3 to 8.2.3, some searches return "StatsFileWriterLz4 file open failed". Our environment is one Search Head, one Indexer, one Cluster Master connected in an indexer cluster, with one Heavy forwarder and a few Universal Forwarders. All servers are running on Windows 2019. 

A specific error message looks like this: "StatsFileWriterLz4 file open failed file=E:\Splunk\var\run\splunk\srtemp\374915603_1292_at_1637749050.1\statstmp_merged_5.sb.lz4" after running this tstats search:

| tstats max(_time) as time max(_indextime) as indextime where index IN ("operations_script_log","telemetry*") sourcetype=* earliest=-30d@d latest=@d by sourcetype host source date_year date_month date_mday date_hour date_minute

This search completed and returned the desired results prior to the upgrade, but won't complete after. It runs for about nine seconds before the "StatsFileWriterLz4 file open failed" error message appears and stops the search.

Has anybody encountered this problem before and know a solution?

Labels (1)
Tags (2)
1 Solution

podegard
Engager

For anyone seeing this: The solution was to upgrade our environment to 8.2.4. The "StatsFileWriterLz4 file open failed" message does not show up after the upgrade.

View solution in original post

0 Karma

podegard
Engager

For anyone seeing this: The solution was to upgrade our environment to 8.2.4. The "StatsFileWriterLz4 file open failed" message does not show up after the upgrade.

0 Karma
Get Updates on the Splunk Community!

.conf24 | Day 0

Hello Splunk Community! My name is Chris, and I'm based in Canberra, Australia's capital, and I travelled for ...

Enhance Security Visibility with Splunk Enterprise Security 7.1 through Threat ...

(view in My Videos)Struggling with alert fatigue, lack of context, and prioritization around security ...

Troubleshooting the OpenTelemetry Collector

  In this tech talk, you’ll learn how to troubleshoot the OpenTelemetry collector - from checking the ...