<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Why do forwarders go down with Unexpected EOF messages such as &amp;quot;FATAL ProcessRunner - Unexpected EOF from process runner child&amp;quot;? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Why-do-forwarders-go-down-with-Unexpected-EOF-messages-such-as/m-p/234498#M45690</link>
    <description>&lt;P&gt;Hi ddrillic ,&lt;/P&gt;

&lt;P&gt;What OS are your Splunk running on top of? Is there any server management software running on the same server? I've had a similar experience like this when my Splunk was running on top of Red Hat with heavy load. If you are running Linux too, you may check from dmesg or /var/log/messages to see whether the similar type of error is recorded there (about terminating a process). If it exists, you may want to recheck the policies of your OS regarding process management.&lt;/P&gt;

&lt;P&gt;I hope this could become your reference for troubleshooting.&lt;/P&gt;</description>
    <pubDate>Mon, 21 Nov 2016 18:43:39 GMT</pubDate>
    <dc:creator>vincenteous</dc:creator>
    <dc:date>2016-11-21T18:43:39Z</dc:date>
    <item>
      <title>Why do forwarders go down with Unexpected EOF messages such as "FATAL ProcessRunner - Unexpected EOF from process runner child"?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-do-forwarders-go-down-with-Unexpected-EOF-messages-such-as/m-p/234497#M45689</link>
      <description>&lt;P&gt;Three of our forwarders went down today saying - &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;11-17-2016 15:39:33.525 -0600 INFO  HttpPubSubConnection - Running phone uri=/services/broker/phonehome/connection_10.123.200.143_8089_dbslt0080.uhc.com_dbslt0080_DC816E54-5F68-4259-BBE3-A97F24AD2EA8
11-17-2016 15:39:35.015 -0600 FATAL ProcessRunner - Unexpected EOF from process runner child!
11-17-2016 15:39:35.015 -0600 ERROR ProcessRunner - helper process seems to have died (child killed by signal 15: Terminated)!
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;What can the cause be?&lt;/P&gt;</description>
      <pubDate>Mon, 21 Nov 2016 17:03:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-do-forwarders-go-down-with-Unexpected-EOF-messages-such-as/m-p/234497#M45689</guid>
      <dc:creator>ddrillic</dc:creator>
      <dc:date>2016-11-21T17:03:47Z</dc:date>
    </item>
    <item>
      <title>Re: Why do forwarders go down with Unexpected EOF messages such as "FATAL ProcessRunner - Unexpected EOF from process runner child"?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-do-forwarders-go-down-with-Unexpected-EOF-messages-such-as/m-p/234498#M45690</link>
      <description>&lt;P&gt;Hi ddrillic ,&lt;/P&gt;

&lt;P&gt;What OS are your Splunk running on top of? Is there any server management software running on the same server? I've had a similar experience like this when my Splunk was running on top of Red Hat with heavy load. If you are running Linux too, you may check from dmesg or /var/log/messages to see whether the similar type of error is recorded there (about terminating a process). If it exists, you may want to recheck the policies of your OS regarding process management.&lt;/P&gt;

&lt;P&gt;I hope this could become your reference for troubleshooting.&lt;/P&gt;</description>
      <pubDate>Mon, 21 Nov 2016 18:43:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-do-forwarders-go-down-with-Unexpected-EOF-messages-such-as/m-p/234498#M45690</guid>
      <dc:creator>vincenteous</dc:creator>
      <dc:date>2016-11-21T18:43:39Z</dc:date>
    </item>
    <item>
      <title>Re: Why do forwarders go down with Unexpected EOF messages such as "FATAL ProcessRunner - Unexpected EOF from process runner child"?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-do-forwarders-go-down-with-Unexpected-EOF-messages-such-as/m-p/234499#M45691</link>
      <description>&lt;P&gt;works for me ,&lt;BR /&gt;
In my case some other person have killed the process (splunk) through ansible script .&lt;/P&gt;</description>
      <pubDate>Thu, 07 Sep 2017 10:11:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-do-forwarders-go-down-with-Unexpected-EOF-messages-such-as/m-p/234499#M45691</guid>
      <dc:creator>kannu</dc:creator>
      <dc:date>2017-09-07T10:11:10Z</dc:date>
    </item>
  </channel>
</rss>

