<?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: Trying to fix the corrupted bucket. Error - JournalSliceDirectory: Cannot seek to rawdata offset 0 in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Trying-to-fix-the-corrupted-bucket-Error-JournalSliceDirectory/m-p/448130#M77930</link>
    <description>&lt;P&gt;Hi David&lt;BR /&gt;
Tried these but nope. Additionally I tried the exporttool to csv and then import back to reconstruct the bucket. But its failing to read the journal at all&lt;/P&gt;</description>
    <pubDate>Tue, 25 Jun 2019 19:47:04 GMT</pubDate>
    <dc:creator>amitm05</dc:creator>
    <dc:date>2019-06-25T19:47:04Z</dc:date>
    <item>
      <title>Trying to fix the corrupted bucket. Error - JournalSliceDirectory: Cannot seek to rawdata offset 0</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Trying-to-fix-the-corrupted-bucket-Error-JournalSliceDirectory/m-p/448126#M77926</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;
I am getting the error:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;JournalSliceDirectory: Cannot seek to rawdata offset 0, path="/opt/splunk/var/li b/splunk/indextest/db/&amp;lt;bucket_id&amp;gt;/rawdata"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I understand this means that the bucket is corrupted. I confirmed this by running the Splunk fsck scan and got the same bucket flagged as corrupted. Now I am trying to rebuild this bucket by Splunk rebuild and Splunk fsck repair commands but still not able to.&lt;/P&gt;

&lt;P&gt;I further tried to decompress/open my journal.gz of the corrupted directory and I am getting the error that its corrupted and cannot be opened. Now I've got this problem on a single indexer env and there are no other copies of the bucket available.&lt;/P&gt;

&lt;P&gt;Can someone point out how this can be fixed?&lt;/P&gt;</description>
      <pubDate>Tue, 25 Jun 2019 06:06:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Trying-to-fix-the-corrupted-bucket-Error-JournalSliceDirectory/m-p/448126#M77926</guid>
      <dc:creator>amitm05</dc:creator>
      <dc:date>2019-06-25T06:06:16Z</dc:date>
    </item>
    <item>
      <title>Re: Trying to fix the corrupted bucket. Error - JournalSliceDirectory: Cannot seek to rawdata offset 0</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Trying-to-fix-the-corrupted-bucket-Error-JournalSliceDirectory/m-p/448127#M77927</link>
      <description>&lt;P&gt;May be that this helps.&lt;BR /&gt;
Although it sounds like you tried these steps already?&lt;BR /&gt;
&lt;A href="https://answers.splunk.com/answers/389363/getting-error-streamed-search-execute-failed-becau.html"&gt;https://answers.splunk.com/answers/389363/getting-error-streamed-search-execute-failed-becau.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 25 Jun 2019 07:17:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Trying-to-fix-the-corrupted-bucket-Error-JournalSliceDirectory/m-p/448127#M77927</guid>
      <dc:creator>effem</dc:creator>
      <dc:date>2019-06-25T07:17:25Z</dc:date>
    </item>
    <item>
      <title>Re: Trying to fix the corrupted bucket. Error - JournalSliceDirectory: Cannot seek to rawdata offset 0</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Trying-to-fix-the-corrupted-bucket-Error-JournalSliceDirectory/m-p/448128#M77928</link>
      <description>&lt;P&gt;Hi @amitm05,&lt;/P&gt;

&lt;P&gt;Have you tried running &lt;CODE&gt;fsck&lt;/CODE&gt; for repair ? You can follow this guide for repairing buckets in standalone indexers :&lt;BR /&gt;
&lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Indexer/Bucketissues"&gt;https://docs.splunk.com/Documentation/Splunk/latest/Indexer/Bucketissues&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;And here you can find more options and parameters for the fsck command:&lt;BR /&gt;
&lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Troubleshooting/CommandlinetoolsforusewithSupport#fsck"&gt;https://docs.splunk.com/Documentation/Splunk/latest/Troubleshooting/CommandlinetoolsforusewithSupport#fsck&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Let me know if that helps.&lt;/P&gt;

&lt;P&gt;Cheers,&lt;BR /&gt;
David&lt;/P&gt;</description>
      <pubDate>Tue, 25 Jun 2019 08:47:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Trying-to-fix-the-corrupted-bucket-Error-JournalSliceDirectory/m-p/448128#M77928</guid>
      <dc:creator>DavidHourani</dc:creator>
      <dc:date>2019-06-25T08:47:02Z</dc:date>
    </item>
    <item>
      <title>Re: Trying to fix the corrupted bucket. Error - JournalSliceDirectory: Cannot seek to rawdata offset 0</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Trying-to-fix-the-corrupted-bucket-Error-JournalSliceDirectory/m-p/448129#M77929</link>
      <description>&lt;P&gt;yes, I've tried these steps already but its still not able to fix the jornal.gz&lt;/P&gt;</description>
      <pubDate>Tue, 25 Jun 2019 19:45:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Trying-to-fix-the-corrupted-bucket-Error-JournalSliceDirectory/m-p/448129#M77929</guid>
      <dc:creator>amitm05</dc:creator>
      <dc:date>2019-06-25T19:45:18Z</dc:date>
    </item>
    <item>
      <title>Re: Trying to fix the corrupted bucket. Error - JournalSliceDirectory: Cannot seek to rawdata offset 0</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Trying-to-fix-the-corrupted-bucket-Error-JournalSliceDirectory/m-p/448130#M77930</link>
      <description>&lt;P&gt;Hi David&lt;BR /&gt;
Tried these but nope. Additionally I tried the exporttool to csv and then import back to reconstruct the bucket. But its failing to read the journal at all&lt;/P&gt;</description>
      <pubDate>Tue, 25 Jun 2019 19:47:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Trying-to-fix-the-corrupted-bucket-Error-JournalSliceDirectory/m-p/448130#M77930</guid>
      <dc:creator>amitm05</dc:creator>
      <dc:date>2019-06-25T19:47:04Z</dc:date>
    </item>
    <item>
      <title>Re: Trying to fix the corrupted bucket. Error - JournalSliceDirectory: Cannot seek to rawdata offset 0</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Trying-to-fix-the-corrupted-bucket-Error-JournalSliceDirectory/m-p/448131#M77931</link>
      <description>&lt;P&gt;Sorted.&lt;BR /&gt;
Downloaded the journal file from the server. Decompressed it using 7z. Then recompressed to gz. Put it back in the bucket. And restarted splunk. &lt;/P&gt;</description>
      <pubDate>Tue, 25 Jun 2019 19:50:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Trying-to-fix-the-corrupted-bucket-Error-JournalSliceDirectory/m-p/448131#M77931</guid>
      <dc:creator>amitm05</dc:creator>
      <dc:date>2019-06-25T19:50:13Z</dc:date>
    </item>
    <item>
      <title>Re: Trying to fix the corrupted bucket. Error - JournalSliceDirectory: Cannot seek to rawdata offset 0</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Trying-to-fix-the-corrupted-bucket-Error-JournalSliceDirectory/m-p/448132#M77932</link>
      <description>&lt;P&gt;Isn't that exactly what is suggested in the link I posted?&lt;/P&gt;</description>
      <pubDate>Tue, 25 Jun 2019 19:56:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Trying-to-fix-the-corrupted-bucket-Error-JournalSliceDirectory/m-p/448132#M77932</guid>
      <dc:creator>effem</dc:creator>
      <dc:date>2019-06-25T19:56:07Z</dc:date>
    </item>
    <item>
      <title>Re: Trying to fix the corrupted bucket. Error - JournalSliceDirectory: Cannot seek to rawdata offset 0</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Trying-to-fix-the-corrupted-bucket-Error-JournalSliceDirectory/m-p/448133#M77933</link>
      <description>&lt;P&gt;No. with gunzip it wasnt working. I wasnt even able to get ahead of the first step. The second command was throwing error only.&lt;BR /&gt;
May be the point is that 7z can also help, but ofcourse you'll have to choose gz while recompressing it back because that is what splunk expects.&lt;/P&gt;</description>
      <pubDate>Wed, 26 Jun 2019 07:09:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Trying-to-fix-the-corrupted-bucket-Error-JournalSliceDirectory/m-p/448133#M77933</guid>
      <dc:creator>amitm05</dc:creator>
      <dc:date>2019-06-26T07:09:22Z</dc:date>
    </item>
  </channel>
</rss>

