<?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 Issue in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-Issue/m-p/95019#M19802</link>
    <description>&lt;P&gt;Well, I guess I would check for a crash log and see if there was any unusual activity (CPU, disk, memory) according to any data you gathered, as well as the splunk internal logs files. Those are in $SPLUNK_HOME/var/log/splunk, but also indexed into the _internal index.&lt;/P&gt;</description>
    <pubDate>Fri, 16 Mar 2012 18:39:10 GMT</pubDate>
    <dc:creator>gkanapathy</dc:creator>
    <dc:date>2012-03-16T18:39:10Z</dc:date>
    <item>
      <title>Splunk Issue</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-Issue/m-p/95018#M19801</link>
      <description>&lt;P&gt;Good morning, &lt;/P&gt;

&lt;P&gt;Still VERY new to Splunk here. But I had a issue I was looking for input on where to start with troubleshooting. &lt;/P&gt;

&lt;P&gt;Our company has an index splunk service die somepoint yesterday. I started it again with ./splunk start and it went into a fsck mode and was doing that for roughly an hour then worked. This mornming A different indexer has the same issue. &lt;/P&gt;

&lt;P&gt;Any idea what could be happening? Where I would start troubleshooting something like that?&lt;/P&gt;</description>
      <pubDate>Fri, 16 Mar 2012 17:43:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-Issue/m-p/95018#M19801</guid>
      <dc:creator>daniel333</dc:creator>
      <dc:date>2012-03-16T17:43:42Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Issue</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-Issue/m-p/95019#M19802</link>
      <description>&lt;P&gt;Well, I guess I would check for a crash log and see if there was any unusual activity (CPU, disk, memory) according to any data you gathered, as well as the splunk internal logs files. Those are in $SPLUNK_HOME/var/log/splunk, but also indexed into the _internal index.&lt;/P&gt;</description>
      <pubDate>Fri, 16 Mar 2012 18:39:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-Issue/m-p/95019#M19802</guid>
      <dc:creator>gkanapathy</dc:creator>
      <dc:date>2012-03-16T18:39:10Z</dc:date>
    </item>
  </channel>
</rss>

