Explanation | The XD Agent service has successfully completed initialization. |
Action | None |
Explanation | The XD Agent service has successfully started. |
Action | None |
Explanation | The Agent is being federated to deployment manager. |
Action | None |
Explanation | The Agent with same node name already exists in the cell. |
Action | None |
Explanation | The Agent name is changed to new name to avoid conflict with already existing nodes. |
Action | None |
Explanation | The Agent is successfully federated into the cell. |
Action | None |
Explanation | Unable to contact the server to federate. Server may be down. |
Action | Make sure deployment manager is running before running addAgent step. |
Explanation | Error happened while federating the agent into deployment manager. |
Action | Check the addAgent.log file in logs folder for errors. |
Explanation | The XD Agent service is disabled. |
Action | None |
Explanation | The XD Agent service is stopped. |
Action | None |
Explanation | Current name of the agent is Default, it will be changed to host name. |
Action | None |
Explanation | Agent is federated into the cell. Check the logs for errors. |
Action | Check the logs for errors and take appropriate action. |
Explanation | addAgent script was run with wrong arguments. |
Action | Specify correct arguments. |
Explanation | Error while writing to the log file. |
Action | Make sure log file location is writable. |
Explanation | Trace information is logged to the specified file. |
Action | Check the logs for informational messages and errors. |
Explanation | Current node is already federated into cell, so it cannot be federate again. |
Action | Run removeNode first. |
Explanation | Discovery service throws BackingStoreException to indicate there has been some error doing discovery, so retry again. |
Action | None |
Explanation | Agent is being stopped. Check the logs for errors. |
Action | Check the logs for errors and take appropriate action. |
Explanation | Error while stopping the agent. Check the logs for errors. |
Action | Check the logs for errors and take appropriate action. |
Explanation | Stop command is issued successfully. Check the logs for errors. |
Action | Check the logs for errors and take appropriate action. |
Explanation | Unable to locate the file that is required. |
Action | Contact IBM support. |
Explanation | Error while adding node to the cell. |
Action | Check the logs for errors. |
Explanation | Node is not part of any cell, so removeNode will not have any affect. |
Action | None |
Explanation | Error happened while removing node from cell, check logs for error. |
Action | Check the logs for errors. |
Explanation | Error happened while contacting master repository. Check logs for errors. |
Action | Check the logs for errors. |
Explanation | Removing federated agent from the master repository. |
Action | None |
Explanation | Removed the agent successfully from the cell. |
Action | None |
Explanation | Security configuration is missing on the agent. |
Action | Check if security xml exists on the agent. |
Explanation | Newer version of the repository is found on the master node. |
Action | None |
Explanation | Agent is launched. Check log file for any errors. |
Action | None |
Explanation | Agent launched successfully. Check logs for useful messages. |
Action | None |
Explanation | Agent launched with errors. Check log files for more information. |
Action | None |
Explanation | Port is updated to handle port conflicts of agent. |
Action | None |
Explanation | An instance of the agent may be already running on the port. |
Action | Stop the running agent to issue start again. |
Explanation | Security is enabled on deployment manager, requires username to successfully federate/unfederate/sync the agent. |
Action | Specify -username <username> to the addAgent/removeAgent/syncAgent script. |
Explanation | Security is enabled on deployment manager, requires password to successfully federate/unfederate/sync the agent. |
Action | Specify -password <password> to the addAgent/removeAgent/syncAgent script. |
Explanation | An instance of the agent may not be running on the port. |
Action | Start the agent to issue stop again. |
Explanation | Security is enabled, so channels will be started in ssl mode. |
Action | None. |
Explanation | Security is enabled, so channels will be started in ssl mode. |
Action | None. |
Explanation | Error happened during federation, so rolling back the federation process. |
Action | Check the logs for error messages. |
Explanation | Error during roll back of federation steps. |
Action | Check the logs for error messages. |
Explanation | The XD Agent service has successfully started. |
Action | None |
Explanation | Host and port information not specified to the command. Information will be read from local configuration repository. |
Action | None. |
Explanation | startMWServer script was run with wrong arguments. |
Action | Specify correct arguments. |
Explanation | stopMWServer script was run with wrong arguments. |
Action | Specify correct arguments. |
Explanation | mwServerStatus script was run with wrong arguments. |
Action | Specify correct arguments. |
Explanation | An exception was caught in the specified method. |
Action | None |
Explanation | Unexpected Error happened. |
Action | None |
Explanation | The XD Agent HAController has successfully completed initialization. |
Action | None |
Explanation | The XD Agent HAController has successfully started. |
Action | None |
Explanation | The XD Agent CatalogServer Cluster has successfully completed initialization. |
Action | None |
Explanation | The XD Agent CatalogServer cluster has successfully started. |
Action | None |
Explanation | This node manages CatalogServer cluster |
Action | None |
Explanation | This node does not manage CatalogServer cluster |
Action | None |
Explanation | The XD Agent HAController has successfully started. |
Action | None |
Explanation | The specified server was successfully started. |
Action | None |
Explanation | The specified server is already running. |
Action | None |
Explanation | The specified server was successfully stopped. |
Action | None |
Explanation | The specified server is not running. |
Action | None |
Explanation | The specified server was successfully terminated. |
Action | None |
Explanation | The specified server was ended. |
Action | None |
Explanation | The agent reattached to the specified server successfully. |
Action | None |
Explanation | When attempting to reattach, the agent found to the specified server was not started. |
Action | None |
Explanation | The agent''s attempt to reattach to the specified server failed. |
Action | None |
Explanation | The specified server is running. |
Action | None |
Explanation | The specified server is not running. |
Action | None |
Explanation | Error while trying to invoke action on the server. |
Action | None |
Explanation | Error while trying to invoke action on the server. |
Action | None |
Explanation | Server not found to invoke the operation. |
Action | Make sure server exists before issuing a command. |
Explanation | Tried to remove agent while agent is still running. |
Action | Stop the agent to remove it from the cell. |
Explanation | The specified server was successfully started. |
Action | None |
Explanation | Server process id is displayed. |
Action | None |
Explanation | Attach to a process using the process id from an earlier start |
Action | None |
Explanation | Unable to attach to the process |
Action | None |
Explanation | Error happened launching the server. Check logs for error messages. |
Action | Check the server logs and take necessary action to correct the problem. |
Explanation | Node is being synchronized with the master repository. Check the logs for errors. |
Action | Check the logs for errors and take appropriate action. |
Explanation | syncAgent script was run with wrong arguments. |
Action | Specify correct arguments. |
Explanation | Error happened while synchronizing configuration of the agent with deployment manager. |
Action | Check the syncAgent.log file in logs folder for errors. |
Explanation | The Agent successfully synchronized configuration with the cell manager. |
Action | None |
Explanation | The deployment manager logic decided that a different operation is required |
Action | None |
Explanation | Remote agent discovered new config information |
Action | None |
Explanation | Remote agent discovered new foreign element |
Action | None |