Workload Automation Agent is not starting

Products

• CA Workload Automation AE - Business Agents (AutoSys)
• CA Workload Automation AE - Scheduler (AutoSys)
• CA Workload Automation Agent

Issue/Introduction

Issue

The agent 11.3 when started runs for a few seconds and stops automatically. This happened because the agent was configured to act as an FTP server while the port 21 was already in use.

Environment

CA Workload Automation Agent for I5 R11.3

Installed on AS400/i5 platform

Cause

The problem was identified by reviewing the defaultlog_agent.log.

 

main.MainThread.CybFtpPluginDriver.runApplication[:132] - CybFtpPluginDriver terminated:

cybermation.library.communications.CybConversationException: The socket name is already in use.

main.MainThread.CybAgentDriver.runApplication[:373] - cybermation.library.plugins.CybPluginException: Plugin instantiation failed

 

The agentparm.txt had the following entries

# FTP specific

ftp.serverport=21

 

This caused the agent to act as a FTP server to listen on port 21.

There was already a generic FTP server listening on port 21.

Since  port 21 was already in use the agent could not start.

 

Resolution/Workaround

The resolution is to configure the agent as a ftp client.

Made the following changes to to the agentparm.txt

#ftp.serverport=21

ftp.noserver=true

Commented out the first line and added the second and restarted the agent. This made the agent behave as a FTP client.

 

Additional Information:

You can also run the agent as another ftp server, but you have to use another port

 

Environment

Release: ATSYHA99000-11.3.6-Workload Automation AE-High Availability Option
Component: