What is the basis of "Failed to acquire locks on requested sandboxes"?
Andy Jewell (242●3●63●74)
| asked Nov 19 '13, 5:55 p.m.
retagged Dec 16 '13, 5:49 p.m. by David Lafreniere (4.8k●7)
I get this error periodically using RTC 4.0.3 command line client, typically doing a status or an accept.
Failed to acquire locks on requested sandboxes
My standard yet ineffective approach to this is:
This occurs even when I'm the only user of the workspace and I've come into the workspace from a fresh reboot of my client PC. I don't do anything with file locks so I'm really not even sure what this error is telling me.
So that's my question:) What IS this telling me? What do I do to resolve it? I read one other note on the forum where Geoffery suggests increasing the timeout. However, my timeout is already at 2 minutes which I think is already excessive but is apparently how our administrators set it up.
Any suggestions on this error would be greatly appreciated!
- Andy
|
Be the first one to answer this question!
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
As I understand increasing the timeout does not help because it is fixed to 60000 ms.
Normally, I do stop the workspace daemon, having done 'lscm list daemons' followed by 'scm daemon stop'. Next time I get this issue I will try 'scm ls daemon' and see if it differs.
I'm not sure if it was the solution or not, but after listing the daemons: