<?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: Forwarder refusing to start in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Forwarder-refusing-to-start/m-p/393788#M70299</link>
    <description>&lt;P&gt;Okay. I checked my log files again and I can see a bunch of errors and warnings from before I started encountering the issue:&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;Processing server from outpus.conf: can't resolve a valid IP address for host=XXXX&lt;/LI&gt;
&lt;LI&gt;Cooked connection to ip=XXXX timed out&lt;/LI&gt;
&lt;LI&gt;Connection to XXXX closed. Read error. An existing connection was forcibly closed by remote host.&lt;/LI&gt;
&lt;LI&gt;The TCP processor has paused the data flow. Forwarding to output group default-autolb-group has been blocked for 2300 seconds. This will probably stall the data flow towards indexing and other network outputs. Review the receiving system's health in the Splunk Monitoring Console. It is probably not accepting data.&lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;I have checked my splunk server and deleted/created port 9997 which I am using for the forwarding but still no difference. &lt;/P&gt;</description>
    <pubDate>Tue, 19 Jun 2018 09:00:14 GMT</pubDate>
    <dc:creator>mawomommoh</dc:creator>
    <dc:date>2018-06-19T09:00:14Z</dc:date>
    <item>
      <title>Forwarder refusing to start</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Forwarder-refusing-to-start/m-p/393786#M70297</link>
      <description>&lt;P&gt;My forwarder was working fine but stopped and I can't get it running again. Running the &lt;CODE&gt;splunk start&lt;/CODE&gt; command appears to be working fine but then it fails at the last step. &lt;/P&gt;

&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="alt text"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/5225i532C3833356567E9/image-size/large?v=v2&amp;amp;px=999" role="button" title="alt text" alt="alt text" /&gt;&lt;/span&gt;&lt;/P&gt;

&lt;P&gt;No logs are being generated in &lt;CODE&gt;splunkd.log&lt;/CODE&gt; but some logs are generated in &lt;CODE&gt;splunkd-utility.log&lt;/CODE&gt;:&lt;/P&gt;

&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="alt text"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/5226i133F1957D6F92AF9/image-size/large?v=v2&amp;amp;px=999" role="button" title="alt text" alt="alt text" /&gt;&lt;/span&gt;&lt;/P&gt;

&lt;P&gt;I am not certain what is causing it from starting. Any help would be appreciated. Thanks&lt;/P&gt;</description>
      <pubDate>Sat, 16 Jun 2018 03:47:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Forwarder-refusing-to-start/m-p/393786#M70297</guid>
      <dc:creator>mawomommoh</dc:creator>
      <dc:date>2018-06-16T03:47:19Z</dc:date>
    </item>
    <item>
      <title>Re: Forwarder refusing to start</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Forwarder-refusing-to-start/m-p/393787#M70298</link>
      <description>&lt;P&gt;Hi @mawomommoh,&lt;/P&gt;

&lt;P&gt;Check the following,&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;Do you have any crash log in splunk log directory?&lt;/LI&gt;
&lt;LI&gt;Directory permissions are intact.&lt;/LI&gt;
&lt;LI&gt;System has enough memory.&lt;/LI&gt;
&lt;LI&gt;Check in windows events to see if there any issues related to splunk crash&lt;/LI&gt;
&lt;/UL&gt;</description>
      <pubDate>Sat, 16 Jun 2018 04:22:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Forwarder-refusing-to-start/m-p/393787#M70298</guid>
      <dc:creator>renjith_nair</dc:creator>
      <dc:date>2018-06-16T04:22:03Z</dc:date>
    </item>
    <item>
      <title>Re: Forwarder refusing to start</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Forwarder-refusing-to-start/m-p/393788#M70299</link>
      <description>&lt;P&gt;Okay. I checked my log files again and I can see a bunch of errors and warnings from before I started encountering the issue:&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;Processing server from outpus.conf: can't resolve a valid IP address for host=XXXX&lt;/LI&gt;
&lt;LI&gt;Cooked connection to ip=XXXX timed out&lt;/LI&gt;
&lt;LI&gt;Connection to XXXX closed. Read error. An existing connection was forcibly closed by remote host.&lt;/LI&gt;
&lt;LI&gt;The TCP processor has paused the data flow. Forwarding to output group default-autolb-group has been blocked for 2300 seconds. This will probably stall the data flow towards indexing and other network outputs. Review the receiving system's health in the Splunk Monitoring Console. It is probably not accepting data.&lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;I have checked my splunk server and deleted/created port 9997 which I am using for the forwarding but still no difference. &lt;/P&gt;</description>
      <pubDate>Tue, 19 Jun 2018 09:00:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Forwarder-refusing-to-start/m-p/393788#M70299</guid>
      <dc:creator>mawomommoh</dc:creator>
      <dc:date>2018-06-19T09:00:14Z</dc:date>
    </item>
    <item>
      <title>Re: Forwarder refusing to start</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Forwarder-refusing-to-start/m-p/393789#M70300</link>
      <description>&lt;P&gt;Hi @mawomommoh,&lt;/P&gt;

&lt;P&gt;Check your index configuration (host and ip) in output conf of forwarder and make sure that they are reachable and not blocked by firewall or acl&lt;/P&gt;</description>
      <pubDate>Wed, 20 Jun 2018 08:43:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Forwarder-refusing-to-start/m-p/393789#M70300</guid>
      <dc:creator>renjith_nair</dc:creator>
      <dc:date>2018-06-20T08:43:42Z</dc:date>
    </item>
  </channel>
</rss>

