Thanks for the help. I installed chef from github including all of the
chef mixlib-authentication mixlib-cli mixlib-config mixlib-log
The patch you send appears to be in place. I built the shellout gem using
gem build and installed it using gem install. The problem is still there.
While I don’t appear to have a memory problem, both CPUs in my Mac are
pegged at 100% of system time. Are there any similar places that could
force the same problem? Are there any logs that would help?
On Wed, Mar 7, 2012 at 5:48 PM, David Leaver firstname.lastname@example.org wrote:
This is probably what you are experiencing:
The patch on the ticket fixed the issue for me
We experienced this on physical machines (lucid 64bit), it is a bit of a
race condition by the looks.
From: email@example.com [mailto:firstname.lastname@example.org]
Sent: Thursday, 8 March 2012 9:41 a.m.
Subject: [chef] Resource consumption on chef-solo
Hey Chef Lists,
I am running chef-solo on the standard vagrant lucid32 box. My host OSes
are either Mac Lion or Ubuntu (10.04 32 bit). I’m running into a serious
resource consumption error and I’m wondering if you’ve seen this before.
Several of the larger packages in my setup (build-essentials, python-dev,
others) seem to freeze my computer. I got bored after watching both CPUs
pegged and RAM full for 9 minutes. I’ve tested the actual apt instruction
on the VM (i.e. apt-get install -q -y python-dev) and it runs very quickly.
I’ve also run the exact same cookbooks on a VM on the Ubuntu host and found
Therefore, it appears to be a problem that only manifests on some machines
running chef-solo in a virtual machine.