Posts tagged "Bootstrapping"

If you are attempting a clustered installation of LiveCycle ES, you may experience errors during the bootstrapping phase of LiveCycle Configuration Manager (LCM) with the following exception in the LCM log:

In a clustered environment, the cluster caching must be configured correctly and working before the database initialization can complete successfully.

Solution

The cluster caching should be configured using one of the options below, depending on whether you are using UDP or TCP caching:
A) UDP caching uses the following Java argument to set a port number: -Dadobe.cache.multicast-port=<port number>
The multicast port must be unique to the LiveCycle ES cluster (that is, the port must not be used by any other cluster on the same network). It is recommended that you configure the same <port number> on all nodes in the LiveCycle ES cluster.

B) TCP caching uses the following Java argument: -Dadobe.cache.cluster-locators=<IPaddress>[<port number>],<IPaddress><port number>]
Configure, as a comma-separated list, the locators for all nodes of the cluster. The value for <IPaddress> is the IP address of the computer running the locator, and the value for <portnumber> is any unused port between 1 and 65535 (the port must not be used by any other cluster on the same network). It is recommended that you configure the same <port number> for all locators.

Troubleshooting

Here are some further troubleshooting tips for LCM errors related to the DB initialization step:

ensure the DB privileges for the DB user match what is specified in the installation documentation

ensure sure the user that is starting the application server has R/W access to the GDS and LC TEMP directories (Bootstrap will fail if the permissions are incorrect)

it may be necessary to drop the DB and re-create it if there was an error the first time