With 3.6.0 and later, the installer checks if any environment variables are setup (either LAE or Analyze). This could cause a problem if you have added a call to .profile.lavastorm to either .bashrc or .profile. For version 3.6.0 and later, you'll need remove that so that the Analyze environment variables are not setup before calling launchData360Analyze.sh.
Consequently, while upgrading to, or installing Data360 Analyze version 3.6.x, users may see this error while running the installer:
The Lavastorm Analytics Engine (LAE) environment has already been initialized. Please ensure that this is not the case prior to installing Data360 Analyze.
This error usually occurs when you source the .profile.lavastorm file before running Analyze. If you are sourcing .profile.lavastorm prior to launch you will need to stop doing this. It's likely it is being sourced in the .bash_profile file found in the users home directory.
If so, you'll need to perform the following steps to overcome it:
> open that file
> comment out or remove the line where it is being sourced
> start a new session to clear any environment variables that were set
> Run launchData360analyze.sh and the error should no longer appear.
RUNNING LAE ON THE SAME BOX:
If you're running LAE on the same machine, you'll need to add something to the startup script, whereby it will source .profile.lavastorm from LAE somewhere else, and not just a generic source as soon as you login as the user. Pre 3.6.0, it was possible to source it as soon as you went to the user, but that is no longer the case.