Getting Data In

ERROR: failed to load index config: 'maxTotalDataSizeMB' tag required in config for

Flynt
Splunk Employee
Splunk Employee

My Splunk won't start due to this error! What do I do?

ERROR: failed to load index config: 'maxTotalDataSizeMB' tag required in config for (...)

1 Solution

Flynt
Splunk Employee
Splunk Employee

A few things to check here.

  1. Check your indexes.conf for any typos or non-numeric characters for this field.
  2. Check and make sure your indexes.conf does not contain a comment or any other information AFTER the number - see below

OK :

maxTotalDataSizeMB = 50000  

NOT OK :

maxTotalDataSizeMB = 50000   #Some comment here

View solution in original post

Flynt
Splunk Employee
Splunk Employee

A few things to check here.

  1. Check your indexes.conf for any typos or non-numeric characters for this field.
  2. Check and make sure your indexes.conf does not contain a comment or any other information AFTER the number - see below

OK :

maxTotalDataSizeMB = 50000  

NOT OK :

maxTotalDataSizeMB = 50000   #Some comment here

jrodman
Splunk Employee
Splunk Employee

FWIW, we can't cut configuration values generally with the # mark; for example they are needed in paths, and in regular expressions.

We could theoretically cut values that don't require # marks, but it could get rather tedious in documenting all the execeptions. In short I think it would make using and supporting splunk harder.

yannK
Splunk Employee
Splunk Employee
Get Updates on the Splunk Community!

Splunk Observability Cloud's AI Assistant in Action Series: Auditing Compliance and ...

This is the third post in the Splunk Observability Cloud’s AI Assistant in Action series that digs into how to ...

Splunk Community Badges!

  Hey everyone! Ready to earn some serious bragging rights in the community? Along with our existing badges ...

What You Read The Most: Splunk Lantern’s Most Popular Articles!

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...