ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Autosys Agent status missing

book

Article ID: 236909

calendar_today

Updated On:

Products

CA Workload Automation AE

Issue/Introduction

The Autosys agent communication check failed and the status shows as missing.

The agent's receiver.log (<Agent_Install_Dir>/log) has the following message captured.

03/14/2022 23:46:32.593+0800 2 TCP/IP Controller Plugin.Receiver pool thread <Regular:1>.CybReceiverChannel.a[:253] - Exiting conversation
03/14/2022 23:46:32.593+0800 2 TCP/IP Controller Plugin.Receiver pool thread <Regular:1>.CybReceiverChannel.a[:158] - Conversation from 10.10.10.14:36514 to 10.10.10.201:7520 arrived
03/14/2022 23:46:32.593+0800 1 TCP/IP Controller Plugin.Receiver pool thread <Regular:1>.CybReceiverChannel.a[:234] - cybermation.library.communications.CybConversationException: Unexpected encryption type. None received. AES expected.
                                                                                                                      at cybermation.library.communications.protocol.CybCommunicationProtocolDynamic.receiveData(CybCommunicationProtocolDynamic.java:634)
                                                                                                                      at cybermation.library.communications.protocol.CybCommunicationProtocolDynamic.receiveMessage(CybCommunicationProtocolDynamic.java:365)
                                                                                                                      at cybermation.library.communications.CybConversation.receiveMessage(CybConversation.java:460)
                                                                                                                      at cybermation.commplugins.tcpip.receiver.CybReceiverChannel.a(CybReceiverChannel.java:174) 
                                                                                                                  at cybermation.commplugins.tcpip.receiver.CybReceiverChannel.call(CybReceiverChannel.java:139)
                                                                                                                      at cybermation.commplugins.tcpip.receiver.CybReceiverChannel.call(CybReceiverChannel.java:51)
                                                                                                                      at cybermation.commplugins.tcpip.receiver.CybReceiverScheduler$CallableWrapper.call(CybReceiverScheduler$CallableWrapper.java:353)
                                                                                                                    at cybermation.commplugins.tcpip.receiver.CybReceiverScheduler$CallableWrapper.call(CybReceiverScheduler$CallableWrapper.java:317)
                                                                                                                      at java.util.concurrent.FutureTask.run(FutureTask.java:266)
                                                                                                                      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
                                                                                                                      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
                                                                                                                      at java.lang.Thread.run(Thread.java:821)
03/14/2022 23:46:32.594+0800 2 TCP/IP Controller Plugin.Receiver pool thread <Regular:1>.CybReceiverChannel.a[:253] - Exiting conversation

 

Cause

The failure in communication is due to an encryption mismatch between Agent configuration and the server-side agent definition.

Environment

Release : 12.0

Component : AUTOSYS SYSTEM AGENT

Resolution

1. As per the error captured in the agent's reciever.log, the server-side configuration is sending the message with no encryption (NONE). Whereas the agent is configured with AES.

To resolve the problem check with the infrastructure team on the communication encryption requirements. If NONE encryption is okay to be used, follow the below procedure -

Take a backup of the file agentparm.txt

 Leave empty value for the following property (Remove the value):

     security.cryptkey=

2. Save the file

3. Restart the agent services

https://techdocs.broadcom.com/us/en/ca-enterprise-software/intelligent-automation/workload-automation-system-agent/12-0/configuring/set-up-security/configure-the-agent-for-no-encryption.html 

Additional Information

Setup Encryption between agent and server -

https://techdocs.broadcom.com/us/en/ca-enterprise-software/intelligent-automation/autosys-workload-automation/12-0-01/administrating/ae-administration/configure-ca-workload-automation-ae-to-work-with-ca-wa-agent-for-unix-linux-windows-or-i5-os/modify-the-encryption-type-and-encryption-key-on-ca-workload-automation-ae.html