Chef-3854


#1

Hello,

Does anyone have advice on how to deal with this issue?
http://tickets.opscode.com/browse/CHEF-3854

Beyond setting a sleep value between runs?

thanks,

Luke


#2

On Thursday, May 30, 2013 at 1:49 PM, Luke Tymowski wrote:

Hello,

Does anyone have advice on how to deal with this issue?
http://tickets.opscode.com/browse/CHEF-3854

Beyond setting a sleep value between runs?

thanks,

Luke
I think this will be fixed by an update to mixlib-shellout. Chef 11 uses flock on a lock file to prevent simultaneous chef runs, but the lock can leak out to processes that chef starts. An upcoming release to mixlib-shellout protects against leaked resources, which should allow chef’s locking mechanism to work correctly.

There is a prerelease gem of mixlib shell out 1.2.0 available, you can install it with gem install mixlib-shellout --pre. If you’re installing chef via omnibus package, gem is in /opt/chef/embedded/bin.


Daniel DeLeo


#3

I think this will be fixed by an update to mixlib-shellout. Chef 11 uses
flock on a lock file to prevent simultaneous chef runs, but the lock can
leak out to processes that chef starts. An upcoming release to
mixlib-shellout protects against leaked resources, which should allow
chef’s locking mechanism to work correctly.

There is a prerelease gem of mixlib shell out 1.2.0 available, you can
install it with gem install mixlib-shellout --pre. If you’re installing
chef via omnibus package, gem is in /opt/chef/embedded/bin.

Thank you. I’ll give that a try.