Manager unable to connect agent. Logs show message about "Bad padding"
Article ID: 48392
Updated On:
Products
Issue/Introduction
The scheduler is not able to connect to the agent. The agent logs show error similar to this:
02/12/2014 13:52:37.673 EST-0500 1 TCP/IP Controller Plugin.Receiver pool thread .CybReceiverChannel.receive[:233] -
cybermation.library.communications.CybConversationException: Bad padding at cybermation.library.communications.protocol.CybCommunicationProtocolRevision....
You can also see errors in agent's receiver and transmitter logs like below;
receiver log:
08/05/2022 10:58:31.090-0400 1 TCP/IP Controller Plugin.Receiver pool thread <Regular:2>.CybReceiverChannel.a[:214] - Can't parse the message: cybermation.library.communications.CybConversationWrongMessageException: Undecipherable message .NAK sent:
transmitter.log:
08/05/2022 10:55:17.444-0400 1 TCP/IP Controller Plugin.Transmitter pool thread <Regular:1>.CybTargetHandlerChannel.a[:617] - Error sending message to CAWA_MANAGER:
cybermation.library.communications.CybConversationException: Unexpected encryption type. None received. DES expected.
Environment
Release: 11.3, 12.0
Component: Workload Automation Agent
Cause
The encryption key used between manager and agent does not match. The same key and cipher must be defined on both sides.
Resolution
By default, the Workload Automation Agent keeps the key in cryptkey.txt file (default location: agent installation directory).
A new key file can be generated by using the keygen utility in the agent install directory.
Usage: keygen 0xkey cipher
Example:
./keygen 0x0987654321FEDCBA DES (Linux/UNIX)
keygen.bat 0x0987654321FEDCBA DES (Windows)
Note: 0x must be added to the key. The manger side does not need to have 0x, only the hexadecimal key.
After generating the new cryptkey.txt file, restart the agent for changes to take affect.
Additional Information
Feedback
