<?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: Cluster manager troubleshooting in Monitoring Splunk</title>
    <link>https://community.splunk.com/t5/Monitoring-Splunk/Cluster-manager-troubleshooting/m-p/759861#M11130</link>
    <description>&lt;P&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/313776"&gt;@Darkvader&lt;/a&gt;&amp;nbsp;These two issues are most common in many Splunk deployments and will address them separately.&lt;/P&gt;&lt;P&gt;For the first one, bundle replication may fail warning - usually caused by large lookup files (often CSVs) included in the search head bundle. This issue is documented in the Splunk knowledge base and refer it for solution.&lt;/P&gt;&lt;P&gt;Solution:&amp;nbsp;&lt;A href="https://splunk.my.site.com/customer/s/article/Distributed-Bundle-Replication-Manager-The-current-bundle-directory-contains-a-large-lookup-file-that-might-cause-bundle-replication-fail" target="_blank" rel="noopener"&gt;Distributed Bundle Replication Manager: The current bundle directory contains a large lookup file that might cause bundle replication fail | Splunk&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Secondly, for Orphaned Searches messages indicates there are active scheduled searches which are owned by disabled or deleted user accounts, may be a user who left the organization.&amp;nbsp;The recommended resolution is to reassign ownership to an active account or disable the search if it is no longer needed.&lt;/P&gt;&lt;P&gt;Refer:&amp;nbsp;&lt;A href="https://help.splunk.com/en/splunk-enterprise/manage-knowledge-objects/knowledge-management-manual/9.3/get-started-with-knowledge-objects/manage-orphaned-knowledge-objects" target="_blank" rel="noopener"&gt;Manage orphaned knowledge objects | Splunk Enterprise (last updated 2025-07-04T01:22:43.095Z)&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Solution:&amp;nbsp;&lt;A href="https://splunk.my.site.com/customer/s/article/Orphaned-Scheduled-Searches" target="_blank" rel="noopener"&gt;Orphaned Scheduled Searches, Reports, and Alerts are missing. | Splunk&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;gt;&amp;gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;If this post addressed your question, you can:&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;Give it&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;karma&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;to show appreciation&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":thumbs_up:"&gt;👍&lt;/span&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Mark it as the&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;solution&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;if it solved your issue&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":heavy_check_mark:"&gt;✔️&lt;/span&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Add a&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;comment&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;if you’d like more details&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":pencil:"&gt;✏️&lt;/span&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN&gt;Acknowledging helpful answers keeps the community strong and motivates contributors to continue sharing their expertise.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;gt;&amp;gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 01 Apr 2026 14:36:56 GMT</pubDate>
    <dc:creator>kknairr</dc:creator>
    <dc:date>2026-04-01T14:36:56Z</dc:date>
    <item>
      <title>Cluster manager troubleshooting</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Cluster-manager-troubleshooting/m-p/759860#M11129</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Search peer appprd09 has the following message: The current bundle directory contains a large lookup file that might cause bundle replication fail. The path to the directory is&amp;nbsp;/opt/splunk/var/run/xyz.bundle&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Search peer appprd09 has the following message: Splunk has found 1 orphaned searches owned by 1 unique disabled users.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Greetings all,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I received the above messages in the cluster manager. How do I identify what that bundle consists of, the orphaned search best troubleshooting steps and is there a troubleshooting doc/video I can use to learn more?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 01 Apr 2026 12:59:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Cluster-manager-troubleshooting/m-p/759860#M11129</guid>
      <dc:creator>Darkvader</dc:creator>
      <dc:date>2026-04-01T12:59:50Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster manager troubleshooting</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Cluster-manager-troubleshooting/m-p/759861#M11130</link>
      <description>&lt;P&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/313776"&gt;@Darkvader&lt;/a&gt;&amp;nbsp;These two issues are most common in many Splunk deployments and will address them separately.&lt;/P&gt;&lt;P&gt;For the first one, bundle replication may fail warning - usually caused by large lookup files (often CSVs) included in the search head bundle. This issue is documented in the Splunk knowledge base and refer it for solution.&lt;/P&gt;&lt;P&gt;Solution:&amp;nbsp;&lt;A href="https://splunk.my.site.com/customer/s/article/Distributed-Bundle-Replication-Manager-The-current-bundle-directory-contains-a-large-lookup-file-that-might-cause-bundle-replication-fail" target="_blank" rel="noopener"&gt;Distributed Bundle Replication Manager: The current bundle directory contains a large lookup file that might cause bundle replication fail | Splunk&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Secondly, for Orphaned Searches messages indicates there are active scheduled searches which are owned by disabled or deleted user accounts, may be a user who left the organization.&amp;nbsp;The recommended resolution is to reassign ownership to an active account or disable the search if it is no longer needed.&lt;/P&gt;&lt;P&gt;Refer:&amp;nbsp;&lt;A href="https://help.splunk.com/en/splunk-enterprise/manage-knowledge-objects/knowledge-management-manual/9.3/get-started-with-knowledge-objects/manage-orphaned-knowledge-objects" target="_blank" rel="noopener"&gt;Manage orphaned knowledge objects | Splunk Enterprise (last updated 2025-07-04T01:22:43.095Z)&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Solution:&amp;nbsp;&lt;A href="https://splunk.my.site.com/customer/s/article/Orphaned-Scheduled-Searches" target="_blank" rel="noopener"&gt;Orphaned Scheduled Searches, Reports, and Alerts are missing. | Splunk&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;gt;&amp;gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;If this post addressed your question, you can:&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;Give it&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;karma&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;to show appreciation&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":thumbs_up:"&gt;👍&lt;/span&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Mark it as the&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;solution&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;if it solved your issue&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":heavy_check_mark:"&gt;✔️&lt;/span&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Add a&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;comment&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;if you’d like more details&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":pencil:"&gt;✏️&lt;/span&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN&gt;Acknowledging helpful answers keeps the community strong and motivates contributors to continue sharing their expertise.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;gt;&amp;gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 01 Apr 2026 14:36:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Cluster-manager-troubleshooting/m-p/759861#M11130</guid>
      <dc:creator>kknairr</dc:creator>
      <dc:date>2026-04-01T14:36:56Z</dc:date>
    </item>
  </channel>
</rss>

