PingAuthorize

The server will not run setup

If the setup tool does not run properly, some of the most common reasons include the following.

A suitable Java environment is not available

The server requires that Java be installed on the system and made available to the server, and it must be installed prior to running setup. If the setup tool does not detect that a suitable Java environment is available, it will refuse to run.

To ensure that this does not happen, the setup tool should be invoked with an explicitly defined value for the JAVA_HOME environment variable that specifies the path to the Java installation that should be used. For example:

env JAVA_HOME=/ds/java ./setup

If the previous command doesn’t solve the issue, the value specified in the provided JAVA_HOME environment variable might have been overridden by another environment variable. In that case, try the following command, which should override any other environment variables that can be set:

env UNBOUNDID_JAVA_HOME="/ds/java" UNBOUNDID_JAVA_BIN="" ./setup

Unexpected arguments provided to the JVM

If the setup script attempts to launch the java command with an invalid set of Java arguments, it might prevent the JVM from starting. By default, no special options are provided to the JVM when running setup, but this might not be the case if either the JAVA_ARGS or UNBOUNDID_JAVA_ARGS environment variable is set. If the setup tool displays an error message that indicates that the Java environment could not be started with the provided set of arguments, then invoke the following command before trying to re-run setup:

unset JAVA_ARGS UNBOUNDID_JAVA_ARGS

The server has already been configured or used

The setup tool is only intended to provide the initial configuration for the server. It refuses to run if it detects that the setup tool has already been run, or if an attempt has been made to start the server prior to running the setup tool. This protects an existing server installation from being inadvertently updated in a manner that could harm an existing configuration or data set.

If the server has been previously used, and if you want to perform a fresh installation, it is recommended that you first remove the existing installation, create a new one, and run setup in that new installation. However, if you are confident that there is nothing of value in the existing installation (for example, if a previous attempt to run setup failed to complete successfully, but it will refuse to run again), follow these cleanup steps to allow the setup program to run:

  • Remove the config/config.ldif file and replace it with the config/update/config.ldif.<revision> file containing the initial configuration.

  • Remove any files or subdirectories below the db directory if they exist.

  • Remove the config/java.properties file if it exists.

  • Remove the lib/setup-java-home script (or lib\setup-java-home.bat file on Microsoft Windows) if it exists.