My BMC Atrium Orchestrator (BAO) / TrueSight Orchestration peer fails to start or act properly. Possible symptoms include the following:
- BAO cannot register with BMC Atrium Single Sign-On:
SEVERE 15-09-01 01:01:01.001 com.bmc.atrium.sso.common.CertificateUtils.captureServerCert().Thread-1:Failed to connect with AtriumSSO server: javax.net.ssl.SSLException: Received fatal alert: unexpected_message
BAO peers fail to join the grid:
01 Sep 2015 01:01:01,001 [Thread=AMP - Grid Framework - Advertisement Processor - 123456] WARN TopologyParticipantProxiesManager Error occurred when connecting to peer [MyCDP] in topology [JMS_DISCOVERY] in grid [management].
Summary: No message available. The exception was of type: java.io.IOException
Caused by:
Summary: connect timed out
Caused by:
Summary: connect timed out
- The peer takes several hours to start after this message in catalina.out:
Initializing Atrium SSO logging directory.
Atrium SSO logging directory not specified, using default.
Atrium SSO default logging directory: /opt/bmc/CDP/tomcat/logs
OpenSSO debug level not set.
- The peer does not write any information to its log files.
- Users cannot see information in the Repository or Grid Manager after they log in.