CDP fails to start

This section lists the settings and properties that you can verify to troubleshoot problems that can prevent the CDP server from starting.

• Ensure that you installed BMC Atrium Orchestrator on a supported platform and operating system and that the system meets the minimum requirements as specified in BMC Remedy and BMC Atrium Product Compatibility Matrices.
• Ensure that the server component is running as a user with Administrator or root permissions.
• Ensure you can communicate with the server; for example, try to ping the server computer.
• Ensure that the server is properly stopped before restarting:
  • On Windows, check the services list or the Task Manager.
  • On UNIX or Linux, enter ps -ef|grep java and look for an entry with the BMC Atrium Orchestrator installation path.
• Ensure that your computer has the minimum amount of contiguous memory. If the JVM cannot allocate contiguous memory, the server will fail to start.
• Review the grid.log file to verify that you do not have any port conflicts.
• Review the catalina out or cataling.log file for server errors.
• Review the grid.log file for port conflicts.
  • Search for common peer startup messages like No store configured.
  • Search for ERROR messages like java_bind, which indicates that the port is already in use by another application.

Problem starting BAO when BAO and the authentication service are installed on the same server

If BAO and the authentication service are installed on the same server and BAO fails to start, ensure that the authentication service is running before starting the BAO service.

1. Start the authentication service (see Starting-and-stopping-product-components-and-services).
2. Log into the authentication service console to ensure that it is running.
3. Start the BAO service.
4. Log into BAO (see Logging-into-Grid-Manager-and-Repository-Manager).

BMC Atrium Orchestrator peer does not start after installation or BMC Atrium Orchestrator does not run properly when using Atrium Single Sign-On

The symptoms may be that BAO fails to register with BMC Atrium Single Sign-On or that peers take several hours to start. This may be due to inadequate system entropy.
See the BMC Atrium Single Sign-On System requirements page for more information. You can also find information in a Knowledge Article listed later in this page.

Related Knowledge Articles

• A BMC Atrium Orchestrator (BAO) peer will not restart properly after the machine on which it is installed runs out of disk space. The service will start, but Grid Manager never comes online and the peer does not process any workflows.
  See the following Knowledge Article for the steps to resolve the issue:
  Peer fails to start after exhausted disk space KA000095977
• When starting BMC Atrium Orchestrator, Grid Manager does not load as expected.
   See the following Knowledge Article for the steps to resolve the issue:
  "Unable to read Archive from file" when starting peer KA000078960

• A BMC Atrium Orchestrator peer does not start after installation or BMC Atrium Orchestrator does not run properly. 
  Symptoms may be that BAO fails to register with BMC Atrium Single Sign-On or that peers take several hours to start.
  This may be due to inadequate system entropy.
  See the following Knowledge Article for more information and the steps to resolve the issue: 
  Actions fail in Atrium Orchestrator due to low system entropy KA000066336