Installation

Cannot install more than one Splunk Instance on Mac OS using .dmg

Lionel
Splunk Employee
Splunk Employee

Hello,

Every time, I install a a second instance of Splunk (same machine, just in a different directory), using the .dmg installer, my original instance gets corrupted and will not work. Multiple directories disappear and of course, I can't execute any of the commands.

My use case is to have two instance for testing purposes.

Thanks

Tags (2)
1 Solution

Mick
Splunk Employee
Splunk Employee

http://wiki.splunk.com/Community:Run_multiple_Splunks_on_one_machine

The link above will take you to instructions on how to successfully configure & run multiple instances on a single machine. The problem you are encountering is a known behaviour on Mac OS X. In running the install package for the second time, the OS inadvertently clobbers the original install, removing files and directories.

Usually it will leave the '$SPLUNK_HOME/etc' and '$SPLUNK_HOME/var' directories intact, so your configurations & data should still exist, but the instance will not be in a usable state and the best option at this point is to move what is left aside, download the .tgx package, extract it to the desired location and move your configs and data back over.

Assuming your 2nd instance installed succesfully when you ran the .dmg that caused this problem, you should now have 2 instances on one machine. Please read the steps in the article linked above to ensure that there are no conflicts between the instances.

View solution in original post

Mick
Splunk Employee
Splunk Employee

http://wiki.splunk.com/Community:Run_multiple_Splunks_on_one_machine

The link above will take you to instructions on how to successfully configure & run multiple instances on a single machine. The problem you are encountering is a known behaviour on Mac OS X. In running the install package for the second time, the OS inadvertently clobbers the original install, removing files and directories.

Usually it will leave the '$SPLUNK_HOME/etc' and '$SPLUNK_HOME/var' directories intact, so your configurations & data should still exist, but the instance will not be in a usable state and the best option at this point is to move what is left aside, download the .tgx package, extract it to the desired location and move your configs and data back over.

Assuming your 2nd instance installed succesfully when you ran the .dmg that caused this problem, you should now have 2 instances on one machine. Please read the steps in the article linked above to ensure that there are no conflicts between the instances.

dart
Splunk Employee
Splunk Employee

I use the .tar.gz downloads to have multiple instances, would that work for you?

Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Can’t Make It to Boston? Stream .conf25 and Learn with Haya Husain

Boston may be buzzing this September with Splunk University and .conf25, but you don’t have to pack a bag to ...

Splunk Lantern’s Guide to The Most Popular .conf25 Sessions

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

Unlock What’s Next: The Splunk Cloud Platform at .conf25

In just a few days, Boston will be buzzing as the Splunk team and thousands of community members come together ...