Key not available for node WIN2K12AGT

Document ID : KB000010264
Last Modified Date : 14/02/2018
Show Technical Document Details
Introduction:

In an effort to maintain a healthy operating environment, one thing to be cognizant of is shutting down agents that are no longer being used in your environment. In the errors.txt file of you Workload Automation DE Manager, you will see messages indicating "Key not available for node...." The full context of this message will be provided in the Background section of this document.

Background:

Customer's may see messages similar to:

20170426 09:30:59.355 [essential] [ERROR] DM.InputProcessor_1: Exception: Key not available for node LNXWASUPPORT.

com.cybermation.espresso.library.crypto.CryptoException: Key not available for node LNXWASUPPORT.

        at cybermation.library.communications.CybKeyObtainerImpl.getKey(CybKeyObtainerImpl.java:64)

        at cybermation.library.communications.listener.CybFIPSDecryptionListener.decrypt(CybFIPSDecryptionListener.java:298)

        at cybermation.library.communications.listener.CybFIPSDecryptionListener.communicationReceive(CybFIPSDecryptionListener.java:134)

        at cybermation.library.communications.CybConversationMulticaster.dispatch(CybConversationMulticaster.java:161)

        at cybermation.library.communications.CybConversation.receiveBinary(CybConversation.java:463)

        at cybermation.library.communications.CybConversation.receiveText(CybConversation.java:656)

        at cybermation.distributedmanager.communications.CybDistributedManagerInputSession.run(CybDistributedManagerInputSession.java:129)

        at com.cybermation.library.concurrent.CybThreadPool$ThreadPoolThread.run(CybThreadPool.java:662)

 

This message is indicative of an agent spoofing the Scheduling Manager. That is to say that the Agent is still aware of the Manager and is trying to establish a connection with it. However, the Manager does not have a valid agent definition any longer for the agent because someone either removed it or it was never defined.

Instructions:

To resolve this issue, you will need to do one of two things:

  1. Add the agent to the Manager. You will need to ensure that you have the valid encryption key for the agent. If you do not have the key, then you can always generate a new one using the keygen utility on the agent. For information on how to use keygen utility to generate a new key, please reference https://docops.ca.com/ca-workload-automation-agent/11-3/en/administrating/set-up-security/set-up-security-between-the-agent-and-the-scheduling-manager
  2. Shut the agent down on the node in question and disable it from starting. If the agent is not planned to be used again, then uninstall it altogether.