ERROR cannot read info: lock timeout exceeded

[Tim Penhey]

On 26/09/15 22:02, Mark Shuttleworth wrote:
> On 25/09/15 15:43, Tim Van Steenburgh wrote:
>>
>>> Generating separate JUJU_HOMEs will insulate your from bug
>>> https://bugs.launchpad.net/juju-core/+bug/1467331
>>
>> Thanks, I'm going to try this approach and see what happens. Although, it
>> seems
>> to me that if it's safe to have multiple JUJU_HOMEs, all "doing stuff"
>> concurrently,
>> it would also be possible to have one lock per env, instead of one global
>> lock. Can
>> anyone on the core team explain why there is one global lock? I'm just
>> curious.
> 
> Also, is there is any implication for the new multi-environment Juju
> servers?

This is all client side caching of information. Nothing to do with the
server side.

Tim