KNAC1703-W

Because a communication failure was detected on an execution host, the status of the execution agent was changed to Unconnectable.

For a physical host, JP1_DEFAULT is indicated in logical-host-name.

(S)

Changes the status of the execution agent to Unconnectable, and then executes the subsequent processing.

(O)

The probable causes are:

• The name of the execution host cannot be resolved.

• The maximum number of file descriptors that can be used by the agent monitoring process was reached.

• No ports are available on the manager host.

• The execution host is not running.

• JP1/AJS3 is not running on the execution host.

• A firewall rejected the connection.

To check the execution agents that recovered, use the ajsagtshow command. Remove the causes of the communication failure. Then, wait until recovery of the indicated execution agent is confirmed by a communication recovery check. Alternatively, use the ajsagtalt command to change the status of the execution agent to Not checked.

If, even after you remove the cause of a failure, the status of execution agents that are operating normally is Unconnectable, a timeout might have occurred in the processing that checks the communication status. Based on the number of execution agents that are in the Unconnectable status, increase the amount of time before a communication connection timeout occurs (the value specified for the environment setting parameter AGMCONNECTTIMEOUT). Increase the value by about 5 to 10 seconds for every 100 execution agents. After changing the value specified for the environment setting parameter AGMCONNECTTIMEOUT, restart the JP1/AJS3 service. After the JP1/AJS3 service restarts, execute the ajsagtcheck command, and then make sure that a timeout does not occur in the processing that checks the communication status.