Splunk Search

What is this error in dispatch process?

kkovanis
New Member
0400 ERROR DispatchProcess - String not found in literals.conf: DISPATCHCOMM:FAILED_TO_START_PROCESS

I need help finding out what this is and how to fix it.
Why is the dispatch process not working? What is dispatchcomm?
What do you use instead of literals.conf?

0 Karma

VatsalJagani
SplunkTrust
SplunkTrust

@kkovanis - Just make sure you have not made any changes to Splunk's internal configuration file or added any local literals.conf file.

0 Karma

codebuilder
Influencer

Did you recently upgrade? literals.conf is deprecated. You should use messages.conf instead.

If you did not upgrade, make sure that literals.conf is owned by splunk:splunk and has appropriate read/write access ,and also that literals.conf contains valid stanzas and string definitions.

The dispatch process is what returns search results from your indexers to your search head(s).

----
An upvote would be appreciated and Accept Solution if it helps!
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 ...

Catalog Is Now Generally Available on Splunk Cloud Platform

A Unified View of Your Data  Security logs, application events, business data, and historical telemetry often ...

Your Path to AgenticOps: AI Experiences for Every Splunk Practitioner

Your Path to AgenticOps: AI Experiences for Every Splunk Practitioner   Watch on demand us for a demo-driven ...