IBM 51, Руководство по устранению неисправностей

Страница: 208 / 248

BTC4043E The command-line interface command
failed. A communication error occurred.
Verify that the common agent is
registered and active on port
port_number .
Explanation: This message is displayed when
command-line interface command invocation fails due
to a communication problem with the common agent.
The communication failure might be caused by one of
the following reasons:
v
The common agent is not active.
v
The common agent does not have valid security
credentials.
v
An attempt was made to contact the common agent
on an incorrect port.
v
The connection established with the common agent
was terminated.
System action: If the common agent is running, it will
continue to run. It will continue to listen for incoming
connections and command-line interface requests.
Administrator Response: Verify that the common
agent is both active and registered, and that the correct
port was specified for command-line interface
command invocation. If the problem persists, contact
customer support.
BTC4044W The common agent port in the
properties file is not an integer. The
default port, port_number , will be used.
Explanation: The command-line interface attempts to
determine the port on which to contact the common
agent by reading the contents of its properties file. This
warning is displayed if the value associated with the
port property in the common agent properties file is
not an integer. The port must be an integer.
System action:
The command-line interface will
attempt to contact the common agent on the specified
default common agent port.
Administrator Response: Set the value associated
with the ep.port property in the common agent
properties file to the port on which the common agent
runs.
BTC4045E The connection from IP_address was
rejected.
Explanation: Another entity attempted to connect to
the common agent, but was rejected. The connection
was probably rejected because of one of the following
reasons:
v
The common agent does not have valid credentials,
which might means it failed to register, or a time
synchronization issue exists between the common
agent and the agent manager.
v
The entity that tried to connect to the common agent
does not have either a valid resource manager or
valid agent manager credentials. Note:
Communication between common agents is not
allowed.
v The entity that attempted to connect to the common
agent did not send the information required to
establish the connection.
v An I/O error occurred.
System action: After rejecting the incoming
connection, the common agent returned began to
listening on the port specified in its properties file.
Administrator Response: Verify that both the common
agent and the entity that is attempting to contact it, has
valid credentials. If the problem persists, contact
customer support.
BTC4046I config_file
Explanation: No additional information is available
for this message.
BTC4047I service_name
Explanation: No additional information is available
for this message.
BTC5000I The monitoring service was successfully
started and deployed.
Explanation: The monitoring service was successfully
started and deployed.
BTC5001I The monitoring service was successfully
stopped and undeployed.
Explanation: The monitoring service was successfully
stopped and undeployed.
BTC5002I The subagent subagent bundle has been
successfully registered as a status
provider.
Explanation: The specified subagent bundle was
successfully registered as a status provider. The
subagent bundle can now begin providing status to the
common agent. No user action is necessary.
BTC5006I The process_name status collection
process is starting.
Explanation:
No additional information is available
for this message.
196
Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide