<?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 How to fix BTree unexpected offset 0 while on order 1? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-fix-BTree-unexpected-offset-0-while-on-order-1/m-p/691990#M115063</link>
    <description>&lt;P&gt;I'm getting these failures after a prior disk corruption.&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;ERROR TailReader [1876879 tailreader0] - Ignoring path="/somepath/somefile" due to: BTree::Exception: unexpected resulting offset 0 while on order 1, starting from offset 2056 node offset: 53209432 order: 255 keys: {  } children: { 0 }&lt;/LI-CODE&gt;&lt;P&gt;I thought I had ejected buckets affected by the corruption; in addition, recent ingestions all go into buckets created after the corruption.&lt;/P&gt;&lt;P&gt;What can I do to fix this?&lt;/P&gt;</description>
    <pubDate>Sat, 29 Jun 2024 00:36:53 GMT</pubDate>
    <dc:creator>yuanliu</dc:creator>
    <dc:date>2024-06-29T00:36:53Z</dc:date>
    <item>
      <title>How to fix BTree unexpected offset 0 while on order 1?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-fix-BTree-unexpected-offset-0-while-on-order-1/m-p/691990#M115063</link>
      <description>&lt;P&gt;I'm getting these failures after a prior disk corruption.&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;ERROR TailReader [1876879 tailreader0] - Ignoring path="/somepath/somefile" due to: BTree::Exception: unexpected resulting offset 0 while on order 1, starting from offset 2056 node offset: 53209432 order: 255 keys: {  } children: { 0 }&lt;/LI-CODE&gt;&lt;P&gt;I thought I had ejected buckets affected by the corruption; in addition, recent ingestions all go into buckets created after the corruption.&lt;/P&gt;&lt;P&gt;What can I do to fix this?&lt;/P&gt;</description>
      <pubDate>Sat, 29 Jun 2024 00:36:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-fix-BTree-unexpected-offset-0-while-on-order-1/m-p/691990#M115063</guid>
      <dc:creator>yuanliu</dc:creator>
      <dc:date>2024-06-29T00:36:53Z</dc:date>
    </item>
    <item>
      <title>Re: How to fix BTree unexpected offset 0 while on order 1?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-fix-BTree-unexpected-offset-0-while-on-order-1/m-p/692003#M115064</link>
      <description>&lt;P&gt;This is a tailreader message so it should be about ingestion, not indexed data.&lt;/P&gt;&lt;P&gt;You might need to clean fishbucket (of course it will reingest all monitor inputs).&lt;/P&gt;</description>
      <pubDate>Sat, 29 Jun 2024 19:50:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-fix-BTree-unexpected-offset-0-while-on-order-1/m-p/692003#M115064</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2024-06-29T19:50:39Z</dc:date>
    </item>
    <item>
      <title>Re: How to fix BTree unexpected offset 0 while on order 1?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-fix-BTree-unexpected-offset-0-while-on-order-1/m-p/692005#M115065</link>
      <description>&lt;P&gt;Indeed this error is related to ingestion failure. &amp;nbsp;I just thought the BTree problem is inside the buckets. &amp;nbsp;To clean up, do I just delete everything in fishbucket? &amp;nbsp;Reingestion is not a problem, but I do not want to cause other behavior changes.&lt;/P&gt;</description>
      <pubDate>Sun, 30 Jun 2024 05:15:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-fix-BTree-unexpected-offset-0-while-on-order-1/m-p/692005#M115065</guid>
      <dc:creator>yuanliu</dc:creator>
      <dc:date>2024-06-30T05:15:40Z</dc:date>
    </item>
    <item>
      <title>Re: How to fix BTree unexpected offset 0 while on order 1?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-fix-BTree-unexpected-offset-0-while-on-order-1/m-p/692006#M115066</link>
      <description>&lt;P&gt;If you had bucket problems, the error would come from another component &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Normally with stale fishbucket entries and similar problems you'd simply remove a particular entry from the fishbucket but in this case it looks that the fishbucket database itself is damaged so you probably need to remove whole fishbucket - stop splunkd, remove var/lib/splunk/fishbucket, start splunkd&lt;/P&gt;&lt;P&gt;You might want to fiddle with the db first. If I remember correctly (but I wouldn't bet any money on it), it's a berkeleydb so it might be possible to repair it.&lt;/P&gt;</description>
      <pubDate>Sun, 30 Jun 2024 07:15:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-fix-BTree-unexpected-offset-0-while-on-order-1/m-p/692006#M115066</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2024-06-30T07:15:28Z</dc:date>
    </item>
    <item>
      <title>Re: How to fix BTree unexpected offset 0 while on order 1?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-fix-BTree-unexpected-offset-0-while-on-order-1/m-p/692252#M115096</link>
      <description>&lt;P&gt;Removing databases in fishbucket restored order in my ingestions. &amp;nbsp;Thank you!&lt;/P&gt;&lt;P&gt;For the record, I preserved fishbucket/db/ which does not contain any BTree. (Had I known this, I could have done this while cleaning up disk corruption. &amp;nbsp;There should be no assumption that fishbucket escaped corruption.)&lt;/P&gt;</description>
      <pubDate>Tue, 02 Jul 2024 23:26:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-fix-BTree-unexpected-offset-0-while-on-order-1/m-p/692252#M115096</guid>
      <dc:creator>yuanliu</dc:creator>
      <dc:date>2024-07-02T23:26:34Z</dc:date>
    </item>
  </channel>
</rss>

