<?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 Splunk Forwarder issue in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-Forwarder-issue/m-p/514167#M87141</link>
    <description>&lt;P&gt;A forwarder which was working before has stopped for up to a month now. After checking, it is confirmed that the forwarder is correctly configured, the service is running and reporting to the indexer, however there is no data showing on the indexer side or when a search is run on splunk&amp;nbsp; for that forwarder. Can someone please help me in the right direction?&lt;/P&gt;</description>
    <pubDate>Fri, 14 Aug 2020 17:28:34 GMT</pubDate>
    <dc:creator>saotaigiri</dc:creator>
    <dc:date>2020-08-14T17:28:34Z</dc:date>
    <item>
      <title>Splunk Forwarder issue</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-Forwarder-issue/m-p/514167#M87141</link>
      <description>&lt;P&gt;A forwarder which was working before has stopped for up to a month now. After checking, it is confirmed that the forwarder is correctly configured, the service is running and reporting to the indexer, however there is no data showing on the indexer side or when a search is run on splunk&amp;nbsp; for that forwarder. Can someone please help me in the right direction?&lt;/P&gt;</description>
      <pubDate>Fri, 14 Aug 2020 17:28:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-Forwarder-issue/m-p/514167#M87141</guid>
      <dc:creator>saotaigiri</dc:creator>
      <dc:date>2020-08-14T17:28:34Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Forwarder issue</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-Forwarder-issue/m-p/514171#M87142</link>
      <description>&lt;P&gt;If you have MC installed then you could look from forwarder monitoring that it is there. If not installed then just look from index=_intenal host=&amp;lt;your forwarder&amp;gt;.&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Is your forwarder UF or HF?&lt;/LI&gt;&lt;LI&gt;And which kind of inputs there are configured?&lt;/LI&gt;&lt;LI&gt;Was there e.g. OS update or something else before sending stops?&lt;/LI&gt;&lt;LI&gt;What you found from forwarders logs ?&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;r. Ismo&lt;/P&gt;</description>
      <pubDate>Fri, 14 Aug 2020 17:49:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-Forwarder-issue/m-p/514171#M87142</guid>
      <dc:creator>isoutamo</dc:creator>
      <dc:date>2020-08-14T17:49:05Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Forwarder issue</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-Forwarder-issue/m-p/514194#M87149</link>
      <description>&lt;P&gt;Can you check the servername in system/local/server.conf and host in system/local/inputs.conf&amp;nbsp;&lt;/P&gt;&lt;P&gt;The host and servername from Splunk config should match with server hostname.&lt;/P&gt;&lt;P&gt;and also take the guid from $SPLUNK_HOME/etc/instance.cfg and check in Search head to see how many forwarders are reporting with the GUID.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;and also identify hostname associated with guid and check if its matching with server hostname.&lt;/P&gt;</description>
      <pubDate>Fri, 14 Aug 2020 19:25:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-Forwarder-issue/m-p/514194#M87149</guid>
      <dc:creator>thambisetty</dc:creator>
      <dc:date>2020-08-14T19:25:11Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Forwarder issue</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-Forwarder-issue/m-p/514205#M87150</link>
      <description>&lt;P&gt;It’s best practices that those three names are same. But those two inside splunk must not to be a server’s hostname. Time by time (e.g. AWS when hostname changes “all” time) is much better to fix it as splunk instance name instead of physical hos/node name.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 14 Aug 2020 21:25:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-Forwarder-issue/m-p/514205#M87150</guid>
      <dc:creator>isoutamo</dc:creator>
      <dc:date>2020-08-14T21:25:26Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Forwarder issue</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-Forwarder-issue/m-p/514218#M87152</link>
      <description>&lt;P&gt;I had those happen today. Restarting the forwarder fixed the problem.&lt;/P&gt;</description>
      <pubDate>Sat, 15 Aug 2020 05:33:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-Forwarder-issue/m-p/514218#M87152</guid>
      <dc:creator>burwell</dc:creator>
      <dc:date>2020-08-15T05:33:58Z</dc:date>
    </item>
  </channel>
</rss>

