Following message may be seen in the tracelog.txt file at regular intervals. (Message below is a subset of the complete error in the log.)
20160421 03:58:51.423 [essential] [WARN] DM.InputProcessor_679: XXXXXX is invalid agent. Message: xxx
20160421 03:58:51.429 [essential] [ERROR] DM.InputProcessor_680: Exception: Key not available for node XXXXXX.
com.cybermation.espresso.library.crypto.CryptoException: Key not available for node XXXXXX.
Running agents will send AFMs to the scheduler in attempts to establish a connection. If the agent is not defined in the scheduler the AFM will not be accepted and the error will be recorded in the tracelog.txt file.
3 options to resolve this.
A) Define the agent in the scheduler.
B) Stop the offending agent from running.
C) Correct agents communication.manager settings to point to a different scheduler.