<?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 some of our universal forwarder intermittently stops forwarding logs? in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Why-some-of-our-universal-forwarder-intermittently-stops/m-p/303964#M11517</link>
    <description>&lt;BLOCKQUOTE&gt;
&lt;P&gt;&lt;STRONG&gt;@dantimola will give you +30 Karma points for answering this question.&lt;/STRONG&gt;&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;</description>
    <pubDate>Fri, 14 Jul 2017 02:30:18 GMT</pubDate>
    <dc:creator>dantimola</dc:creator>
    <dc:date>2017-07-14T02:30:18Z</dc:date>
    <item>
      <title>Why some of our universal forwarder intermittently stops forwarding logs?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Why-some-of-our-universal-forwarder-intermittently-stops/m-p/303962#M11515</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;

&lt;P&gt;Good day, would like to seek for help regarding on our universal forwarders. Some of our sources (universal forwarder) intermittently stops forwarding logs. I don't know why, firewall definition is intact, if you telnet splunk ports from the sources, the results are good. However, when checking &lt;CODE&gt;splunkd.log&lt;/CODE&gt;, &lt;STRONG&gt;Cooked Connection, Raw Connection, Ping connection&lt;/STRONG&gt; and &lt;STRONG&gt;Connection TIme out&lt;/STRONG&gt; can be seen. Please help. Thanks.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;Universal Forwarder Versions are:
6.2.6, 6.4.0

Splunk Enterprise Infra and versions:
6 Indexers: 6.6.1
3 Heavy Forwarders: 6.6.1
2 SH: 6.6.1
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Regards,&lt;BR /&gt;
Dan&lt;/P&gt;</description>
      <pubDate>Wed, 12 Jul 2017 03:25:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Why-some-of-our-universal-forwarder-intermittently-stops/m-p/303962#M11515</guid>
      <dc:creator>dantimola</dc:creator>
      <dc:date>2017-07-12T03:25:48Z</dc:date>
    </item>
    <item>
      <title>Re: Why some of our universal forwarder intermittently stops forwarding logs?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Why-some-of-our-universal-forwarder-intermittently-stops/m-p/303963#M11516</link>
      <description>&lt;P&gt;I've conducted health check on our infra. Maybe this can help. Looks like the event-processing queues is having an issue. How can I optimize/resolve this? Thanks.&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/3190iBA0BCFA5EE46B93F/image-size/large?v=v2&amp;amp;px=999" role="button" title="alt text" alt="alt text" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 12 Jul 2017 03:34:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Why-some-of-our-universal-forwarder-intermittently-stops/m-p/303963#M11516</guid>
      <dc:creator>dantimola</dc:creator>
      <dc:date>2017-07-12T03:34:37Z</dc:date>
    </item>
    <item>
      <title>Re: Why some of our universal forwarder intermittently stops forwarding logs?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Why-some-of-our-universal-forwarder-intermittently-stops/m-p/303964#M11517</link>
      <description>&lt;BLOCKQUOTE&gt;
&lt;P&gt;&lt;STRONG&gt;@dantimola will give you +30 Karma points for answering this question.&lt;/STRONG&gt;&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;</description>
      <pubDate>Fri, 14 Jul 2017 02:30:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Why-some-of-our-universal-forwarder-intermittently-stops/m-p/303964#M11517</guid>
      <dc:creator>dantimola</dc:creator>
      <dc:date>2017-07-14T02:30:18Z</dc:date>
    </item>
  </channel>
</rss>

