Troubleshooting: Create an additional cluster node

Adding a node to a cluster is part of setting up a clustered environment. If you encounter a failure during the configuration process, determine whether you can run the step again, skip the step, or if you must clean up the step. For some failed steps, learn how to correct the issue and recover from the failure.

Each potential step in the configuration is included. Because the steps vary depending on your selections, the steps are not numbered. Find the step that failed to learn more about correcting and recovering from the failure. If you need to change a value that you entered in the wizard, then you must run the configuration again.

Tip: If you must go through the wizard again, download the wizard selections that you made to save time. Then, cancel the configuration. Start the process over and upload your saved selections. Correct or enter values for the parameters that caused the failure.

Manual Step: Install profile templates

Manual step errors occur outside the context of the wizard.

Table 1. Appropriate actions for Manual Step: Install profile templatesIf you must run a configuration again, the table helps you determine what actions are appropriate.
Actions	Notes
Run the step again	Not applicable
Skip the step	If you successfully completed the step before, then skip this step.
Clean up step	None required

Manual Step: Install portal binary files on the server where you plan to add a node to your cluster

Manual step errors occur outside the context of the wizard.

Table 2. Appropriate actions for Manual Step: Install portal binary files on the server where you plan to add a node to your clusterIf you must run a configuration again, the table helps you determine what actions are appropriate.
Actions	Notes
Run the step again	Not applicable
Skip the step	If you successfully completed the step before, then skip this step.
Clean up step	None required

Manual Step: Copy the database drivers from the primary node to the additional node

Manual step errors occur outside the context of the wizard.

Table 3. Appropriate actions for Manual Step: Copy the database drivers from the primary node to the additional nodeIf you must run a configuration again, the table helps you determine what actions are appropriate.
Actions	Notes
Run the step again	Not applicable
Skip the step	If you successfully completed the step before, then skip this step.
Clean up step	None required

Manual Step: Verify that the portal node and deployment manager system clocks are within 5 minutes of each other

Manual step errors occur outside the context of the wizard.

Table 4. Appropriate actions forManual Step: Verify that the portal node and deployment manager system clocks are within 5 minutes of each otherIf you must run a configuration again, the table helps you determine what actions are appropriate.
Actions	Notes
Run the step again	Not applicable
Skip the step	If you successfully completed the step before, then skip this step.
Clean up step	None required

Create the profile for the secondary portal node

About this task:

If the step fails, see the logs for the manageprofiles command to determine why the step failed. The wizard uses the portal profile templates to create the HCL Digital Experience profile. An error might result from a problem with the profile templates. The error message in the log provides more information.

The log files are in the app_server_root/logs/manageprofiles directory.

Use the following table for manual instructions on recovering from a failure. If you prefer to use the Configuration Wizard option, Remove the HCL Digital Experience profile, to remove the profile in the event of a failure, go to More options > Remove the HCL Digital Experience profile and remove the profile. When the profile is removed successfully, you can run the Create an Additional Cluster Node configuration again.

Table 5. Appropriate actions for step: Create the profile for the secondary portal nodeIf you must run a configuration again, the table helps you determine what actions are appropriate.
Actions	Notes
Run the step again	Run the step again, if it did not complete successfully before.
Skip the step	If this step was successful, you can skip it if you run the configuration process again.
Clean up step	If an unrecoverable error occurs and the secondary node profile creation step fails, remove the profile. Use the manageprofiles command to remove the profile. The command file is in the app_server_root/bin directory. The command file is a script that is named manageprofiles.sh\|bat. Example: `/opt/IBM/WebSphere/AppServer/bin/manageprofiles.sh -delete -profileName wp_profile_2` Note: If the step fails, see the logs for the `manageprofiles` command to determine why the step failed. The wizard uses the portal profile templates to create the secondary node profile. An error might result from a problem with the profile templates. The error message in the log provides more information. Delete the profile directory. Then, run the Create an Additional Cluster Node again.

Federate the node

About this task:

If this step fails see the addNode.log to determine why the step failed. In most cases, you can correct the error condition and run the step again. You do not have to cancel or reset the configuration steps.

The log is in the /wp_profile/logs directory.

Table 6. Appropriate actions for step: Federate the nodeIf you must run a configuration again, the table helps you determine what actions are appropriate.
Actions	Notes
Run the step again	If the step did not complete successfully during the previous configuration, run it again.
Skip the step	If you successfully completed the step before, then skip this step.
Clean up step	Based on where the step failed during the addNode task, you might need to remove the node and run the step again. Run the removeNode command from the wp_profile/bin directory. Example: `wp_profile/bin/removeNode.sh`

Configure the dynamic cluster node

If this step fails, click View Results to see the applicable section of the ConfigTrace.log.

Table 7. Appropriate actions for step: Configure the dynamic cluster nodeIf you must run a configuration again, the table helps you determine what actions are appropriate.
Actions	Notes
Run the step again	You can run this step repeatedly without causing harm.
Skip the step	If you successfully completed the step before, then skip this step.
Clean up step	None required

Add a secondary node to the cluster

Table 8. Appropriate actions for step: Add a secondary node to the clusterIf you must run a configuration again, the table helps you determine what actions are appropriate.
Actions	Notes
Run the step again	You can run this step repeatedly without causing harm.
Skip the step	If you successfully completed the step before, then skip this step.
Clean up step	None required

Start the portal server

Table 9. Appropriate actions for step: Start the portal serverIf you must run a configuration again, the table helps you determine what actions are appropriate.
Actions	Notes
Run the step again	You can run this step repeatedly without causing harm.
Skip the step	Not applicable
Clean up step	None required