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!

Announcing Scheduled Export GA for Dashboard Studio

We're excited to announce the general availability of Scheduled Export for Dashboard Studio. Starting in ...

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics GA in US-AWS!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...