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 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 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 likejava_bind
, which indicates that the port is already in use by another application.
- Search for common peer startup messages like
Problem starting when and the authentication service are installed on the same server
If and the authentication service are installed on the same server and fails to start, ensure that the authentication service is running before starting the service.
- Start the authentication service (see Starting and stopping product components and services).
- Log into the authentication service console to ensure that it is running.
- Start the service.
- Log into (see Logging into Grid Manager and Repository Manager).
Related Knowledge Articles
- A
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
, 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
Was this page helpful? Yes No
Submitting...
Thank you
Comments
Log in or register to comment.