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 javaand 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
ERRORmessages likejava_bind, which indicates that the port is already in use by another application.
- Search for common peer startup messages like
Overview
Content Tools
Apps
Reporter Replacement
com.bmc.atlassian.bmc-util-plugin-2.section.label
Tasks