https://community.splunk.com/t5/Monitoring-Splunk/How-do-I-start-Splunk-after-it-stopped-responding-with-ERROR/m-p/418978#M6294 <P>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.</P> <PRE><CODE>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)! </CODE></PRE> Fri, 01 Mar 2019 15:15:37 GMT abhijitnath89bm 2019-03-01T15:15:37Z https://community.splunk.com/t5/Monitoring-Splunk/How-do-I-start-Splunk-after-it-stopped-responding-with-ERROR/m-p/418978#M6294 <P>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.</P> <PRE><CODE>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)! </CODE></PRE> Fri, 01 Mar 2019 15:15:37 GMT https://community.splunk.com/t5/Monitoring-Splunk/How-do-I-start-Splunk-after-it-stopped-responding-with-ERROR/m-p/418978#M6294 abhijitnath89bm 2019-03-01T15:15:37Z https://community.splunk.com/t5/Monitoring-Splunk/How-do-I-start-Splunk-after-it-stopped-responding-with-ERROR/m-p/418979#M6295 <P>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:</P> <P><CODE>dmesg -T| grep 'illed process'</CODE></P> <P>If this returns results it means you don't have enough system memory for what you are trying to do. </P> <P>All the best.</P> Fri, 01 Mar 2019 20:03:07 GMT https://community.splunk.com/t5/Monitoring-Splunk/How-do-I-start-Splunk-after-it-stopped-responding-with-ERROR/m-p/418979#M6295 chrisyounger 2019-03-01T20:03:07Z