I should've mentioned this before:
We've been experiencing this since we upgraded to BBSSA v220.127.116.115 a year and a half ago.
The servers in question have all been running the appropriate agent.
We have upgraded to v8.2 Sp2 on 11/2 and we have yet been able to upgrade the server's agents.
One of the servers has recently locked out again, and since the "current remedy" was to uninstall & reinstall the agent, we installed the 8.2 Sp2 agent.Verbose logging is enabled and we'll have to see if that makes any difference.
Cecil, to modify agent logging, rolling over, log size, etc - this is done in c:\windows\rsc\log4crc.txt
When troubleshooting such problem, first thing to do is to identify the exact point in time when the agent was locked out. You can find this in Event Viewer
Second, provided that your rscd logs were rolled over, I would review the appserver logs at that time to see if you ran any activity (jobs, some live browse operation, etc) against that server.
Once you narrow on the activity, I would try to reproduce the issue (i.e. try to lock out the agent). If you are able to reproduce, then it should be much easier from there on how to resolve.
regarding the problems with the BladeLogicRSCD account locking up
you know this discussion ?
Several 8.1.X.XXX agent versions have (had) this problem. Check this discussion please for details.
There are some known issues w/ the 8.1 agent and locking. cecil - you are having the lock problem w/ the 8.2 agent as well?
can you try a couple things:
- what is the 'crashonauditfail' setting set to on the box?
- before you started the 8.2 agent, did you delete the BladeLogicRSCD account and the HKLM\Security\SAM\BladeLogic registry key ?
Bill, we finally had a chance, yesterday, to install the 8.2 SP2 agent on a server that has been "locking". We're "waiting" for it to "lock" right now...