Skip to Content
Information
Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Restarting CLM components in the CLM Self-Checker

If you see problems restarting components in the CLM Self-Checker, review the following troubleshooting tips:

  • Stackinformation.properties file is not created on the Platform Manager host if NSH is not installed.
  • On a multi-VM stack, Stackinformation.properties is not created on the Platform Manager host if the RSCD agent service of any of the hosts where CLM components are deployed  is not reachable.  
  • If Stackinformation.properties is not created on Platform Manager host, the Restart All Components button is hidden on the CLM Self-Checker. If you do not see Restart All Components, troubleshoot the possible reasons why the StackInformation file is not created on the Platform Manager host. Possible reasons include:
    • RSCD agent service of any of the machines where CLM components are deployed  is not reachable.  
    • RSCD agent should be running on the same port which is same as Self Check RSCD agent port. Check the following line in the C:\Windows\rsc\secure file:
      default:port=4750:protocol=5:tls_mode=encryption_only:encryption=tls

    • Port value should be same on all the components.
    • The components machines are not reachable through NSH. You can use an agentinfo command to verify. 
  • When the Restart is in-progress:
    • Platform Manager waits for the Enterprise AR  service to be running, But if the Enterprise AR service is still not started after 10 attempts, Platform Manger starts with a warning message.
    • Health Check is stopped in the background to avoid false alarms. The stopped health status is displayed with different color scheme (Gray) which informs you that the Restart is in progress and Health checks are paused. After CLM is up and running after restart, Health Check is resumed.
  • If the Restart could not be completed because the Self Checker tomcat server has crashed, you are notified the next time that you log on to the Self Checker with a Restart was aborted message. If you see this error, the cloud administrator must click  Restart All Components again.  This action restarts the CLM stack from the beginning because the Self Checker does not store the history of the Restart Stack process.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Cloud Lifecycle Management 4.7