I have Splunk v6.0 installed under a custom directory "/splunk6". So my directory structure is something like this below:
splunk6/bin
splunk6/etc
splunk6/include
splunk6/lib
splunk6/openssl
...
I understand the documented/typical way to upgrade is to untar the new bits in the existing installation directory. This would work if the home directory name was "splunk", since the tarball has the contents like this below:
splunk/
splunk/include/
splunk/openssl/
...
How should I perform the upgrade if my home directory name is different (i.e. "splunk6") from the default ("splunk")?
You can also (this is the way i did) create a symbolic link and then perform upgrade.
I have several splunk instance with a common root dir (let's say /opt/splunk/instance_A /opt/splunk/instance_B, and so on)
I just create a symbolic link to /opt/splunk/splunk corresponding to the instance i need to upgrade and then achieve it. (untar in the instance common root dir)
You can also (this is the way i did) create a symbolic link and then perform upgrade.
I have several splunk instance with a common root dir (let's say /opt/splunk/instance_A /opt/splunk/instance_B, and so on)
I just create a symbolic link to /opt/splunk/splunk corresponding to the instance i need to upgrade and then achieve it. (untar in the instance common root dir)
Just wanted to add for those not familiar with symbolic link (also known as a soft link or symlink). The approach does work.
This suggestion helped me perform the upgrade successfully. Thanks!
Try adding "-C" option to your untar command.
tar xvfz splunk-6.0.1-189883-Linux-x86_64.tgz -C /splunk6
This command creates the "splunk" directory inside "splunk6", so the bits end up getting extracted under "/splunk6/splunk". This doesn't work for the upgrade.
When I've had that happen I just move the dir contents back out of that folder and pretend I didn't make a mistake. lol