Splunk Search

Search process did not exit cleanly, exit_code=255, description="exited with code 255". Please look in search.log

Ashwini008
Builder

Hi,

I am getting the following error on my search head whenever i run query in a newly created app.

  • Search results might be incomplete: the search process on the peer:indexer1 ended prematurely. Check the peer log, such as $SPLUNK_HOME/var/log/splunk/splunkd.log and as well as the search.log for the particular search.
  • [Indexer 1] Search process did not exit cleanly, exit_code=255, description="exited with code 255". Please look in search.log for this peer in the Job Inspector for more info.

In the search.log this is the error"

12-15-2021 05:42:06.881 ERROR dispatchRunner - RunDispatch::runDispatchThread threw error: Application does not exist: 

"

The above error is present for on all four of our indexers.

What is the cause for this? How do we fix this error?

 

Thank You!

Labels (2)
0 Karma

richgalloway
SplunkTrust
SplunkTrust

Did you install the new app on the indexers?  If not, try it.

---
If this reply helps you, Karma would be appreciated.
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!

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...

All Work and No Play? Not at .conf26! Unwind at These Evening Events

Between hands-on technical sessions, keynote reveals, and diving into live architectures, .conf26 is packed ...

Join the Hackathon at .conf26 and build a No-Code AI agent

Join us for the AI Agent Buildathon, an in-person, three-hour hands-on Hackathon where you’ll use Splunk Agent ...