Check the Secure file located under rsc folder.
if it does not work, try installing the agent, if single server giving the problem.
Please share contents of secure file & rscd.log.
Also try agentinfo against that server & share the result of it..+
I notice in the ticket that you have opened for this issue, it has been recommended to uninstall and reinstall the RSCD agent.
In your diagnostic steps, i agree with SIddu and Aryan about confirming the settings in the secure file and what errors appear in the rscd.log.
Can you please share them here as well as with the support engineer working on your ticket?
Checked and confirmed, the secure file has same contents as the working servers and tried re-installing RSCD agent as well
RSCD logs contain repeated entries listed below
ca39535cef195856d45d 0000000114 07/04/13 08:42:10.060 WARN rscd - ITN76 1664 SYSTEM (Not_available): (Not_available): Main: Wait Timeout. Starting AgentHouseKeeping.
1 of 1 people found this helpful
We had an similar issue (although not the same error message), which was related to ASLR mechanisms enabled on Windows Server 2008 R2.
In order to get this resolved we had to disable the FIPS algorithm.
This can be done be renaming the openssl.cnf file in the RSCD_DIR\share directory to something like openssl.bak.
Maybe it's worth a try.
(Remember to restart the Agent)
This issue was due to network latency, connection from the Appserver to Target was taking lots of time than required.