<?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: Skipped Indexing in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Skipped-Indexing/m-p/82267#M17009</link>
    <description>&lt;P&gt;I had this problem while running 5.0 but I believe the root cause was due to forwarding syslog data from a forwarder on the same box as the search head to the indexer (this was due to a work around due to a syslog bug in 5.0).&lt;/P&gt;

&lt;P&gt;Once I upgraded to 5.0.1 I had to fsch the database to keep this error for showing up. Stop splunk and run this command.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;splunk fsck --all --repair
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Wed, 28 Nov 2012 20:57:16 GMT</pubDate>
    <dc:creator>kphillipson</dc:creator>
    <dc:date>2012-11-28T20:57:16Z</dc:date>
    <item>
      <title>Skipped Indexing</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Skipped-Indexing/m-p/82264#M17006</link>
      <description>&lt;P&gt;What does this message mean and how does one resolve it. Has appeared now for several days. Using at best 1% of disk space.&lt;/P&gt;

&lt;P&gt;skipped indexing of internal audit event will keep dropping events until indexer congestion is remedied. Check disk space and other issues that may cause indexer to block&lt;/P&gt;</description>
      <pubDate>Wed, 03 Nov 2010 01:33:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Skipped-Indexing/m-p/82264#M17006</guid>
      <dc:creator>sleathley</dc:creator>
      <dc:date>2010-11-03T01:33:07Z</dc:date>
    </item>
    <item>
      <title>Re: Skipped Indexing</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Skipped-Indexing/m-p/82265#M17007</link>
      <description>&lt;P&gt;Recommendation: Run the "splunk diag" utility, open a case and upload the diag file to your case, Splunk Support will provide you assistance.&lt;/P&gt;

&lt;P&gt;Here are a few things to check, according to the url listed below:&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;Check disk space on all of your partitions. If your space is too low, then that will cause indexing and searching problems.&lt;/LI&gt;
&lt;LI&gt;Verify that "splunk-optimize" has been running. If you see a large number of *.tsidx files in your buckets, you can simply run splunk-optimize /path/to/your/bucket to force this process to run.&lt;/LI&gt;
&lt;LI&gt;Try disabling some non-essential scheduled saved searches and see if that helps relieve the problem. (You probably don't want to do this for summary-indexing saved searches, if it can be avoided.)&lt;/LI&gt;
&lt;/OL&gt;

&lt;P&gt;&lt;A href="http://splunk-base.splunk.com/answers/7996/down-error-skipped-indexing-of-internal-audit-event-will-keep-dropping-events-until-indexer-congestion-is-remedied-check-disk-space-and-other-issues-that-may-cause-indexer-to-block"&gt;http://splunk-base.splunk.com/answers/7996/down-error-skipped-indexing-of-internal-audit-event-will-keep-dropping-events-until-indexer-congestion-is-remedied-check-disk-space-and-other-issues-that-may-cause-indexer-to-block&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 03 Nov 2010 01:48:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Skipped-Indexing/m-p/82265#M17007</guid>
      <dc:creator>rsimmons</dc:creator>
      <dc:date>2010-11-03T01:48:11Z</dc:date>
    </item>
    <item>
      <title>Re: Skipped Indexing</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Skipped-Indexing/m-p/82266#M17008</link>
      <description>&lt;P&gt;What did this end up being?&lt;/P&gt;</description>
      <pubDate>Thu, 20 Oct 2011 16:13:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Skipped-Indexing/m-p/82266#M17008</guid>
      <dc:creator>chicodeme</dc:creator>
      <dc:date>2011-10-20T16:13:42Z</dc:date>
    </item>
    <item>
      <title>Re: Skipped Indexing</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Skipped-Indexing/m-p/82267#M17009</link>
      <description>&lt;P&gt;I had this problem while running 5.0 but I believe the root cause was due to forwarding syslog data from a forwarder on the same box as the search head to the indexer (this was due to a work around due to a syslog bug in 5.0).&lt;/P&gt;

&lt;P&gt;Once I upgraded to 5.0.1 I had to fsch the database to keep this error for showing up. Stop splunk and run this command.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;splunk fsck --all --repair
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Wed, 28 Nov 2012 20:57:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Skipped-Indexing/m-p/82267#M17009</guid>
      <dc:creator>kphillipson</dc:creator>
      <dc:date>2012-11-28T20:57:16Z</dc:date>
    </item>
    <item>
      <title>Re: Skipped Indexing</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Skipped-Indexing/m-p/82268#M17010</link>
      <description>&lt;P&gt;In what folder set would I run this command on a Window indexer?&lt;/P&gt;</description>
      <pubDate>Thu, 05 Mar 2015 15:21:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Skipped-Indexing/m-p/82268#M17010</guid>
      <dc:creator>ITUser1</dc:creator>
      <dc:date>2015-03-05T15:21:38Z</dc:date>
    </item>
  </channel>
</rss>

