After a new Remote Agent installation, autoping fails with error.

Article Id: 50702
Status: Published
Updated On: 21-03-2018 06:12
Legacy Id: TEC543568
Products:
CA Workload Automation AE - Business Agents (AutoSys) , CA Workload Automation AE - Scheduler (AutoSys) , CA Workload Automation Agent
Issue/Introduction:

Description:

After a new Remote Agent installation, autoping fails with error:

caught signal #14 auto_alarm=12
read failed stream socket: Interrupted system call
ERROR: AutoPing WAS NOT SUCCESSFUL!

Solution:

There are several possible reasons: Here is the checklist:

  1. Are you able to ping from the Remote Agent (RA) to the Server (EP) and vice versa?

  2. Are both the EP and RA configured with the same value for the "AutoRemPort"?

  3. Is the configured port for Remote Agent open in both directions (Firewalls)?

  4. Does the "AutoRemDir" configured on the EP points to a valid directory on the Agent?

  5. Do you have "write" privileges on "AutoRemDir" directory on the Agent?

  6. Have you recycled the inetd demon after installing the Agent?

  7. Do you see any auto_rem* log files created on the Agent?

    If you find an auto_rem* log verify the errors reported in the file.

    This will provide more information on the reason why autoping does not work correctly.

Environment:

Release: ATSY1C99000-4.5-AutoSys-Job Management-Class 1 Remote Agent
Component: