Post-provision script fails to execute

In IBM® Platform Cluster Manager Community Edition, a post-provision script fails to execute. The following ERROR cluster event is logged: Failed to execute the command: /opt/pcm/ego/pcmtools/ pcmloader "<script_name>" due to an internal error: (error code=10).

Symptoms

The post-provision script did not have enough time to execute.

Causes

The EGO wait time is not long enough.

Diagnosing the problem

From the Clusters tab, click the Clusters item and select the cluster in provisioning state. Navigate to the Events tab in the bottom pane. The following ERROR event is logged:

Failed to execute the command: /opt/pcm/ego/pcmtools/ pcmloader "<script_name>" due to an internal error: (error code=10).

.

Resolving the problem

System administrator response: To resolve this error, ensure that the compute node has enough memory and increase the EGO wait time. To increase the EGO wait time, increase the value of the ego.allocWaitingSec parameter in the pcmdConfig.xml file. Additionally you can tune the ego.allocWaitingSec parameter. Completing the following steps to resolve this issue:

  1. Open the pcmdConfig.xml configuration file in the /opt/pcm/pcmd/conf directory.
  2. Locate the ego.allocWaitingSec parameter and increase it from 120 to 300.
    <Parameter name="ego.allocWaitingSec">300</Parameter>
  3. Locate the ego.activityRetries parameter and increase it from 5 to 10.
    <Parameter name="ego.activityRetries">10</Parameter>
  4. Try running the post-provision script again.
  5. If the post-provision script fails again, rerun the post-provision scripts on the failed server using the pcm_run_cluster_script command.

  • Parent topic: Troubleshooting for clusters