Getting Data In

Minimum free disk space reached

TaraPennington
Loves-to-Learn Lots

TaraPennington_0-1614015603527.png

I just got Splunk ingesting some data and now I'm getting this error message. I found several posts related to this but they are 6 years old and I think they are out of date. One of them said to go to the server.conf file and edit this stanza, but I don't see that stanza in the file. Is that stanza in another location? 

[diskUsage]
minFreeSpace = <num>

 

0 Karma

TaraPennington
Loves-to-Learn Lots

Okay do I need to stop splunk on the forwarders then?

Also, the files that need to be deleted are on the splunk server? (single instance).

0 Karma

gcusello
SplunkTrust
SplunkTrust

Hi @TaraPennington,

The problem is a search problem so only on Indexer (your single instance).

Ciao.

Giuseppe

0 Karma

gcusello
SplunkTrust
SplunkTrust

Hi @TaraPennington,

The problem is that you reached the minimum disk space in the dispatched folder.

You have to delete the oldest folders and files in the folder $SPLUNK_HOME/var/run/splunk (after Splunk stop) and then restart Splunk.

Ciao.

Giuseppe

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 ...