<?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: Splunk Indexer Error in Monitoring Splunk</title>
    <link>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-Indexer-Error/m-p/528117#M4642</link>
    <description>&lt;P&gt;Why are the queues blocked?&amp;nbsp; Use the Monitoring Console to see which queue is blocked then address it.&amp;nbsp; Usually, a slow storage system is the cause.&lt;/P&gt;</description>
    <pubDate>Thu, 05 Nov 2020 13:33:50 GMT</pubDate>
    <dc:creator>richgalloway</dc:creator>
    <dc:date>2020-11-05T13:33:50Z</dc:date>
    <item>
      <title>Splunk Indexer Error</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-Indexer-Error/m-p/528086#M4640</link>
      <description>&lt;P&gt;&lt;SPAN&gt;We received the below error in splunkd.log on our indexer server. We are using cluster env with 6 indexers. The indexers are coming up and down&lt;/SPAN&gt;&lt;/P&gt;&lt;DIV&gt;11-05-2020 07:43:17.734 +0000 WARN TcpInputProc - Stopping all listening ports. Queues blocked for more than 300 seconds&lt;BR /&gt;11-05-2020 07:43:17.734 +0000 INFO TcpInputProc - Stopping IPv4 port 9995&lt;BR /&gt;11-05-2020 07:43:17.734 +0000 INFO TcpInputProc - Stopping IPv4 port 9997&lt;/DIV&gt;</description>
      <pubDate>Thu, 05 Nov 2020 09:57:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-Indexer-Error/m-p/528086#M4640</guid>
      <dc:creator>abhijitnath89ax</dc:creator>
      <dc:date>2020-11-05T09:57:00Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Indexer Error</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-Indexer-Error/m-p/528117#M4642</link>
      <description>&lt;P&gt;Why are the queues blocked?&amp;nbsp; Use the Monitoring Console to see which queue is blocked then address it.&amp;nbsp; Usually, a slow storage system is the cause.&lt;/P&gt;</description>
      <pubDate>Thu, 05 Nov 2020 13:33:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-Indexer-Error/m-p/528117#M4642</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2020-11-05T13:33:50Z</dc:date>
    </item>
  </channel>
</rss>

