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
Get Updates on the Splunk Community!

Splunk Mobile: Your Brand-New Home Screen

Meet Your New Mobile Hub  Hello Splunk Community!  Staying connected to your data—no matter where you are—is ...

Introducing Value Insights (Beta): Understand the Business Impact your organization ...

Real progress on your strategic priorities starts with knowing the business outcomes your teams are delivering ...

Enterprise Security (ES) Essentials 8.3 is Now GA — Smarter Detections, Faster ...

As of today, Enterprise Security (ES) Essentials 8.3 is now generally available, helping SOC teams simplify ...