Troubleshoot: Configuration Wizard - Create an Additional Cluster Node
To change a value entered in the wizard, run the configuration again.
If run the wizard again, to save time, download the wizard selections you made to save time, then, cancel the configuration. Start the process over and upload the 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.
Actions Notes Run the step again Not applicable Skip the step If we 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 the cluster
Manual step errors occur outside the context of the wizard.
Actions Notes Run the step again Not applicable Skip the step If we 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.
Actions Notes Run the step again Not applicable Skip the step If we successfully completed the step before, then skip this step. Clean up step None required
Manual Step: Verify 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.
Actions Notes Run the step again Not applicable Skip the step If we successfully completed the step before, then skip this step. Clean up step None required
Create the profile for the secondary portal node
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 deployment manager 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...
app_server_root/logs/manageprofiles
Use the following table for manual instructions on recovering from a failure. If we prefer to use the Configuration Wizard option, Remove the WebSphere Portal profile, to remove the profile in the event of a failure, go to More options > Remove the WebSphere Portal profile and remove the profile. When the profile is removed successfully, we can run the Create an Additional Cluster Node configuration again.
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, we can skip it if we run the configuration process again. Clean up step If an unrecoverable error occurs and the create deployment manager profile 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 named manageprofiles.sh|bat.
Example:
/opt/IBM/WebSphere/AppServer/bin/manageprofiles.sh -delete -profileName dmgr01
- Delete the profile directory.
- Then, run the Create an Additional Cluster Node again.
Federate the node
If this step fails see the addNode.log to determine why the step failed. In most cases, we can correct the error condition and run the step again. We do not have to cancel or reset the configuration steps.
The log is in the /wp_profile/logs directory
Actions Notes Run the step again If the step did not complete successfully during the previous configuration, run it again. Skip the step If we successfully completed the step before, then skip this step. Clean up step Based on where the step failed during the addNode task, we might need to remove the node and run the step again. Run...
cd 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.
Actions Notes Run the step again We can run this step repeatedly without causing harm. Skip the step If we successfully completed the step before, then skip this step. Clean up step None required
Add a secondary node to the cluster
Actions Notes Run the step again We can run this step repeatedly without causing harm. Skip the step If we successfully completed the step before, then skip this step. Clean up step None required
Start the portal server
Actions Notes Run the step again We can run this step repeatedly without causing harm. Skip the step Not applicable Clean up step None required