A similar alarm like this may show up:
Or while checking FGLAM\logs\HostAgents\x.x.x.x\WindowsAgent\Monitor@server.com_yyyy-mm-dd_hhmmss_001.log, the following message can be observed:
As an example in Infrastructure Agent, when creating a credential, by default if the policy is enabled, it will add FailureRatePolicy(3 times/1hour) to each credential. So when the agentmonitor host connection is broken, after 3 times, it will mark the credential policy not valid, then the Fglam(Foglight Agent Manager) will mark the credential as unusable. The connection might be failure if you have too many agent instances connecting.
Then check the hosts dashboard or agent log again.
Note: When you enter the database credentials, that configuration will be stored in the agent's properties. Only the OS credentials will be stored in the lock-box (Credentials management dashboard).
Also in Windows from command prompt the following command can be ran to check that the username is not locked at the domain level:
net user Usernamex /domain.com
Note: Change Usernamex for the username you use in Foglight.
Change domain.com for your domain.
© 2021 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Conditions d’utilisation Confidentialité