<?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 resync commands in Splunk Enterprise</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise/resync-commands/m-p/685587#M19246</link>
    <description>&lt;P&gt;&lt;SPAN class=""&gt;messages shows the below:&lt;BR /&gt;Search head cluster member &lt;STRONG&gt;A&lt;/STRONG&gt; is having problems pulling configurations from the search head cluster captain &lt;STRONG&gt;B&lt;/STRONG&gt;. Changes from the other members are not replicating to this member, and changes on this member are not replicating to other members. Consider performing a destructive configuration resync on this search head cluster member.&lt;BR /&gt;&lt;BR /&gt;any idea regarding the resync commands ??&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 26 Apr 2024 07:31:25 GMT</pubDate>
    <dc:creator>Bisho-Fouad</dc:creator>
    <dc:date>2024-04-26T07:31:25Z</dc:date>
    <item>
      <title>resync commands</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/resync-commands/m-p/685587#M19246</link>
      <description>&lt;P&gt;&lt;SPAN class=""&gt;messages shows the below:&lt;BR /&gt;Search head cluster member &lt;STRONG&gt;A&lt;/STRONG&gt; is having problems pulling configurations from the search head cluster captain &lt;STRONG&gt;B&lt;/STRONG&gt;. Changes from the other members are not replicating to this member, and changes on this member are not replicating to other members. Consider performing a destructive configuration resync on this search head cluster member.&lt;BR /&gt;&lt;BR /&gt;any idea regarding the resync commands ??&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 26 Apr 2024 07:31:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/resync-commands/m-p/685587#M19246</guid>
      <dc:creator>Bisho-Fouad</dc:creator>
      <dc:date>2024-04-26T07:31:25Z</dc:date>
    </item>
    <item>
      <title>Re: resync commands</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/resync-commands/m-p/685604#M19248</link>
      <description>&lt;P&gt;This is the command if using Linux - /opt/splunk/bin/splunk resync shcluster-replicated-config&amp;nbsp;(Run this on other SHC members – not captain) &amp;nbsp;&lt;/P&gt;&lt;P&gt;Check the status first, runs on one of the SHC members&lt;/P&gt;&lt;P&gt;/opt/splunk/bin/splunk show shcluster-status&lt;/P&gt;&lt;P&gt;But might be worth trying a rolling restart and see if that helps, looks like the /var/run folder on the captain is having some kind of issue. Check Disk Space as well. du -sh /opt/splunk/var/run to get the size of the folder.&lt;/P&gt;&lt;P&gt;Rolling restart command = /opt/splunk/bin/splunk rolling-restart shcluster-members&amp;nbsp;from one of the members&lt;/P&gt;&lt;P&gt;Monitor the rolling restart /opt/splunk/bin/splunk rolling-restart shcluster-members&amp;nbsp; -status 1&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;The captain may change – so observe – you can change the captain back to original&lt;/P&gt;&lt;P&gt;/opt/splunk/bin/splunk transfer shcluster-captain -mgmt_uri &lt;A href="https://s1sh1.ops.com:8089" target="_blank"&gt;&amp;lt;your SHC Captain&amp;gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;If this is production, then factor in maintenance window or do it when least busy for users, as it will be somewhat disruptive for searches, until it's resolved.&lt;BR /&gt;&lt;BR /&gt;But it It's worth going through the previous answers for this issue, the commands and various steps. Ensure you have backups and plan the steps for the procedure.&amp;nbsp;At minimum /opt/splunk/etc which contains the configuration.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;A href="https://community.splunk.com/t5/Deployment-Architecture/How-to-resolve-error-quot-Error-pulling-configurations-from-the/m-p/354231" target="_blank"&gt;https://community.splunk.com/t5/Deployment-Architecture/How-to-resolve-error-quot-Error-pulling-configurations-from-the/m-p/354231&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;A href="https://community.splunk.com/t5/Deployment-Architecture/How-do-I-fix-quot-splunk-resync-shcluster-replicated-config-quot/m-p/212358" target="_blank"&gt;https://community.splunk.com/t5/Deployment-Architecture/How-do-I-fix-quot-splunk-resync-shcluster-replicated-config-quot/m-p/212358&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 26 Apr 2024 10:05:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/resync-commands/m-p/685604#M19248</guid>
      <dc:creator>deepakc</dc:creator>
      <dc:date>2024-04-26T10:05:05Z</dc:date>
    </item>
    <item>
      <title>Re: resync commands</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/resync-commands/m-p/685614#M19253</link>
      <description>&lt;P&gt;A Google search for "destructive configuration resync" finds this in Docs: &lt;A href="https://docs.splunk.com/Documentation/Splunk/9.2.1/DistSearch/HowconfrepoworksinSHC#Why_a_recovering_member_might_need_to_resync_manually" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/9.2.1/DistSearch/HowconfrepoworksinSHC#Why_a_recovering_member_might_need_to_resync_manually&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 26 Apr 2024 12:06:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/resync-commands/m-p/685614#M19253</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2024-04-26T12:06:24Z</dc:date>
    </item>
  </channel>
</rss>

