If CRX doesn't start, or if there are exceptions and stack traces in the log file that are related to persistence (such as TarPersistenceManager or FileDataStore).
Such problems can have many causes.
To help analyzing the problem, we need to know the following information:
Follow this process for each cluster node, as well as on the crx shared directory (unless the shared directory is within one of the cluster nodes). In the instructions below is usually the directory where the license.properties is found (the parent directory of crx-quickstart).
Note: make sure when you execute java -version that you are executing it against the same java executable that is used by the CRX or CQ5 instance.
To get all the data, run the the following commands in a shell:
cd <clusterNode1> java -version 2> infoJavaVersion.log find . -name "crx*.jar" > infoCrxVersion.log ls -alR > infoFileList.log zip -r clusterNode1.zip . -i */repository.xml */workspace.xml */*.log *.log */*.log.* rm info*
On Windows systems, perform the following steps: