I have an application platform deployed to AWS, that has four seperate AMI's. This platform was torn down and rebuilt yesterday, but the AppD agents were not reinstalled on the AMI's as I do not have them included in the Cloud Formation templates.
M...
I am in the process of orchestrating our AppD agent installations and I'm running into an issue. I'll outline the process then provide the error messages.
The orchestration is Chef, so my recipie is a modified version of cookbooks from GitHub. The mo...
That's the root of my question. If we can set an availablity metric on a node shouldn't that node actually have an agent installed? The Nodes showing in my applications tier are not the correct host name, and i haven't installed any agents on any nod...
I've destroyed that EC2 isntance, and as I mentioned we have made the choice to not use the AppD direction for obfuscating the account key at this time.
The file will open in text or browser with out issues and displays all values, its only when the agent attempts to de-obfuscate the store key that it fails, if we remove the obfuscation the agent starts normally, as soon as we walkt rhough the docume...
Just following up on this.
It appears that the error message is not really a XML formating issues as more that this is an incorrectly obfuscated text value that cannot be read by the agent.
Caused by: com.singularity.ee.util.security.credentialstor...