Monitoring Splunk

How do I start Splunk after it stopped responding with ERROR ProcessRunner?

abhijitnath89bm
New Member

I received the below error. Now, none of the Splunk start or stop commands are responding. Please let us know how we will bring Splunk back to life.

03-01-2019 09:05:15.702 -0500 FATAL ProcessRunner - Unexpected EOF from process runner child!
03-01-2019 09:05:15.702 -0500 ERROR ProcessRunner - helper process seems to have died (child killed by signal 15: Terminated)!  
Tags (2)
0 Karma

chrisyounger
SplunkTrust
SplunkTrust

The linux OOM (out-of-memory) killer probably killed the Splunk search process. You should run this command to see if the OOM killer is occuring:

dmesg -T| grep 'illed process'

If this returns results it means you don't have enough system memory for what you are trying to do.

All the best.

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!

SOC4Kafka - New Kafka Connector Powered by OpenTelemetry

The new SOC4Kafka connector, built on OpenTelemetry, enables the collection of Kafka messages and forwards ...

Rounding off the Splunk Dashboard Contest

What does a contest-winning Splunk dashboard look like? In this case, it isn't in a browser tab at all. It ...

A Four Part Event Series: AI + Observability: AI Agents, LLMs, Apps, & Infrastructure

AI + Observability: AI Agents, LLMs, Apps, & Infrastructure The rapid evolution of artificial intelligence ...