<?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: Splunk upgrade with odd path in Installation</title>
    <link>https://community.splunk.com/t5/Installation/Splunk-upgrade-with-odd-path/m-p/564705#M10580</link>
    <description>&lt;P&gt;You can untar to a temp folder and move like below; (Make sure have a backup before upgrade)&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;cd /tmp
tar xzvf /path/to/splunk-install.tgz
mv splunk /opt/Splunk/splunkenterprise&lt;/LI-CODE&gt;</description>
    <pubDate>Wed, 25 Aug 2021 13:02:14 GMT</pubDate>
    <dc:creator>scelikok</dc:creator>
    <dc:date>2021-08-25T13:02:14Z</dc:date>
    <item>
      <title>Splunk upgrade with odd path</title>
      <link>https://community.splunk.com/t5/Installation/Splunk-upgrade-with-odd-path/m-p/564598#M10572</link>
      <description>&lt;P&gt;I am working on upgrading a deployment server which is typically an easy task. My issue is that this particular environment has a strange path instead of the usual /opt/splunk/etc. This environment has /opt/Splunk/splunkenterprise/etc/. I feel like if i run the upgrade as i normally do untarring the file to /opt, it could create some issues. does anyone have insight as to if this should be upgraded "business as usual" or if the command needs modification? I am worried that untarring in under /opt will cause issues with other possible dependencies to particular file paths.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 24 Aug 2021 18:24:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Splunk-upgrade-with-odd-path/m-p/564598#M10572</guid>
      <dc:creator>jerm1020rq</dc:creator>
      <dc:date>2021-08-24T18:24:31Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk upgrade with odd path</title>
      <link>https://community.splunk.com/t5/Installation/Splunk-upgrade-with-odd-path/m-p/564606#M10573</link>
      <description>&lt;P&gt;Just create a symlink named /opt/splunk which points to your odd path:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;ln -s /opt/Splunk/splunkenterprise /opt/splunk&lt;/LI-CODE&gt;&lt;P&gt;&lt;BR /&gt;Make sure it's owned by your Splunk OS user and then continue on with your upgrade.&lt;/P&gt;</description>
      <pubDate>Tue, 24 Aug 2021 20:24:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Splunk-upgrade-with-odd-path/m-p/564606#M10573</guid>
      <dc:creator>codebuilder</dc:creator>
      <dc:date>2021-08-24T20:24:40Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk upgrade with odd path</title>
      <link>https://community.splunk.com/t5/Installation/Splunk-upgrade-with-odd-path/m-p/564705#M10580</link>
      <description>&lt;P&gt;You can untar to a temp folder and move like below; (Make sure have a backup before upgrade)&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;cd /tmp
tar xzvf /path/to/splunk-install.tgz
mv splunk /opt/Splunk/splunkenterprise&lt;/LI-CODE&gt;</description>
      <pubDate>Wed, 25 Aug 2021 13:02:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Splunk-upgrade-with-odd-path/m-p/564705#M10580</guid>
      <dc:creator>scelikok</dc:creator>
      <dc:date>2021-08-25T13:02:14Z</dc:date>
    </item>
  </channel>
</rss>

