Explanation | The server has been elected as the host leader on the specified port. |
Action | This message is for information purposes only. No action is required. |
Explanation | The server has been elected as a host follower on the specified port. |
Action | This message is for information purposes only. No action is required. |
Explanation | The server is no longer the host leader on the specified port. |
Action | This message is for information purposes only. No action is required. |
Explanation | The server is no longer a host follower on the specified port. |
Action | This message is for information purposes only. No action is required. |
Explanation | The configured host leader election port has changed. |
Action | This message is for information purposes only. No action is required. |
Explanation | The host leader was deactivated or its configured port was changed and the network port used for host leader elections could not be closed. The network port is in an indeterminate state. |
Action | If host leader elections on this host and the indicated port fail, the interface may need to be reset, or a different port used. Consult FFDC logs for more information on the failure error. |
Explanation | The IP address or host name of the server could not be determined. |
Action | Check the server's network configuration. |
Explanation | The specified password cannot be correctly encoded. |
Action | Check FFDC log for the root cause of the error. |
Explanation | This message indicates the SSH keys are being generated. This action can take a few moments. |
Action | This message is for information purposes only. No action is required. |
Explanation | This message indicates the SSH keys have been successfully generated. |
Action | This message is for information purposes only. No action is required. |
Explanation | There was an error while processing or generating the SSH keys. The current user may not have permissions to write or read a specific file or directory. |
Action | Ensure the user which has started the server has the correct permissions to access the SSH files. |
Explanation | The specified algorithm is required for SSH key generation. |
Action | Change server.xml to use user generated SSH key pair or password authentication. |
Explanation | The server's host information was successfully published to the collective repository. |
Action | This message is for information purposes only. No action is required. |
Explanation | Unable to publish the server's host information to the collective repository. |
Action | This message indicates the error which caused the publishing error. |
Explanation | The server's paths were successfully published to the collective repository. |
Action | This message is for information purposes only. No action is required. |
Explanation | Unable to publish the server's paths to the collective repository. |
Action | This message indicates the error which caused the publishing error. |
Explanation | The server state was successfully published to the collective repository. |
Action | This message is for information purposes only. No action is required. |
Explanation | The server may not be able to be managed remotely. |
Action | This message indicates the error which caused the publishing error. |
Explanation | sshPrivateKey and userPassword have been specified. Set either sshPrivateKey or userPassword, but not both. Key-based authentication will be used and the userPassword will be ignored. |
Action | Set either sshPrivateKey or userPassword, but not both. |
Explanation | An sshPublicKeyPath has been set without a corresponding sshPrivateKey. |
Action | Either remove the sshPublicKeyPath property or specify the corresponding sshPrivateKey. |
Explanation | The private key is required for key-based authentication. |
Action | Either remove the sshPrivateKeyPassword property or specify the corresponding sshPrivateKey. |
Explanation | The attribute useSudo for element <hostAuthInfo> is set to false, but other sudo options are set. sudo will not be used and the other options will be ignored. |
Action | Either set useSudo to true, or unset the other sudo options. |
Explanation | No credentials have been set for the <hostAuthInfo> configuration. Default SSH key configuration will be used. |
Action | This message is for information purposes only. |
Explanation | The remote host authentication has been configured successfully. |
Action | This message is for information purposes only. |
Explanation | The specified SSH public key file does not exist or is not a regular file. Check that the path is correct and that file does exist. The private key file does exist and will be used for authentication. |
Action | Check that the path is correct and that file does exist. |
Explanation | The specified SSH private key file does not exist or is not a regular file. Check that the path is correct and that file does exist. Key-based authentication can not be completed without a private key. |
Action | Check that the path is correct and that file does exist. |
Explanation | The specified key pair is incomplete. The SSH private key does not exist or is not a regular file. Check that the path is correct and that file does exist. Key-based authentication can not be completed without a private key. |
Action | Check that the path is correct and that file exists. |
Explanation | Unable to publish the JMX endpoint information for this server. This server's MBeans will not be able to be managed through the collective. A configuration or other type of warning or error has occurred. |
Action | A configuration or other type of warning or error has occurred. Check the previous warning or error messages for possible corrective action. |
Explanation | An internal error has occurred. |
Action | See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | No configuration exists for the default_host virtual host. |
Action | Configure an HTTP endpoint for the default_host virtual host. |
Explanation | A configuration error has occurred: the HTTPS port for the HTTP endpoint for default_host virtual host in server configuration is not valid or disabled. |
Action | Check that the HTTP endpoint for default_host virtual host has the HTTPS port configured and the value is valid. |
Explanation | The X509 certificate presented for authentication is not a certificate issued by a WebSphere Application Server collective. The certificate is not valid for authentication to the collective as a collective member. |
Action | The certificate was not recognized as a WebSphere Application Server collective certificate. Check the certificate used by the authenticating caller. |
Explanation | The X509 certificate presented for authentication is not a collective controller certificate issued by a WebSphere Application Server collective controller. The certificate is not valid for authentication to the collective member. |
Action | The certificate was not recognized as a WebSphere Application Server collective controller certificate. Check the certificate used by the authenticating caller. |