<?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 Error during Splunk forwarder upgrade from 7.2.0 to 8.1.0 in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Error-during-Splunk-forwarder-upgrade-from-7-2-0-to-8-1-0/m-p/568832#M100930</link>
    <description>&lt;P&gt;Did anyone ever offer any answer to this issue.&amp;nbsp; I am running into the same problem.&lt;/P&gt;</description>
    <pubDate>Tue, 28 Sep 2021 19:34:59 GMT</pubDate>
    <dc:creator>dsanders80</dc:creator>
    <dc:date>2021-09-28T19:34:59Z</dc:date>
    <item>
      <title>Error during Splunk forwarder upgrade from 7.2.0 to 8.1.0</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Error-during-Splunk-forwarder-upgrade-from-7-2-0-to-8-1-0/m-p/534047#M89664</link>
      <description>&lt;P&gt;Getting below error after executing below command&amp;nbsp;&lt;/P&gt;&lt;P&gt;./splunk start --accept-license --answer-yes&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;It seems that the Splunk default certificates are being used. If certificate validation is turned on using the default certificates (not-recommended), this may result in loss of communication in mixed-version Splunk environments after upgrade.&lt;/P&gt;&lt;P&gt;"/base_app/splunk/splunkforwarder/etc/auth/ca.pem": already a renewed Splunk certificate: skipping renewal&lt;BR /&gt;"/base_app/splunk/splunkforwarder/etc/auth/cacert.pem": already a renewed Splunk certificate: skipping renewal&lt;BR /&gt;ERROR: Valid migration mode not specified.&lt;BR /&gt;ERROR while running migrate-distsearch-conf migration.&lt;/P&gt;</description>
      <pubDate>Thu, 24 Dec 2020 13:09:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Error-during-Splunk-forwarder-upgrade-from-7-2-0-to-8-1-0/m-p/534047#M89664</guid>
      <dc:creator>ramshan</dc:creator>
      <dc:date>2020-12-24T13:09:58Z</dc:date>
    </item>
    <item>
      <title>Error during Splunk forwarder upgrade from 7.2.0 to 8.1.0</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Error-during-Splunk-forwarder-upgrade-from-7-2-0-to-8-1-0/m-p/568832#M100930</link>
      <description>&lt;P&gt;Did anyone ever offer any answer to this issue.&amp;nbsp; I am running into the same problem.&lt;/P&gt;</description>
      <pubDate>Tue, 28 Sep 2021 19:34:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Error-during-Splunk-forwarder-upgrade-from-7-2-0-to-8-1-0/m-p/568832#M100930</guid>
      <dc:creator>dsanders80</dc:creator>
      <dc:date>2021-09-28T19:34:59Z</dc:date>
    </item>
    <item>
      <title>Re: Error during Splunk forwarder upgrade from 7.2.0 to 8.1.0</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Error-during-Splunk-forwarder-upgrade-from-7-2-0-to-8-1-0/m-p/711882#M117566</link>
      <description>&lt;P&gt;It's been a long time. But did any one got any answers. I am stuck with same issue on aix machine. Trying to upgrade my forwarder from 8.2.3 to 9.2.3 version&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 17 Feb 2025 18:38:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Error-during-Splunk-forwarder-upgrade-from-7-2-0-to-8-1-0/m-p/711882#M117566</guid>
      <dc:creator>amanve</dc:creator>
      <dc:date>2025-02-17T18:38:35Z</dc:date>
    </item>
  </channel>
</rss>

