[chef] Re: Re: Re: Chefspec Errno::ENOMEM

["Stewart, Curtis" < >]

Thanks for the responses Julian and Ranjib.

I’ll see if the 11.10 version of chef would resolve some issues.

And I haven’t considered using the ruby api directly, we install s3cmd with our baseos on all machines and I thought using it would be the best option.

I’ll look into a library that uses a pi’s.

Thanks again,

Curtis

On Feb 11, 2014, at 3:38 PM, Ranjib Dey < "> > wrote:

Hi Curtis, 

out of curiosity , any reason you dont want to use the aws-sdk's ruby api directly to enlist and get all the objects md5? wont it be much cleaner? 

On the shellout error, this will be problematic if large number of files are in the bucket, as you are parsing the entire stdout content,

http://docs.aws.amazon.com/AWSRubySDK/latest/AWS/S3/S3Object.html

On Tue, Feb 11, 2014 at 1:10 PM, Julian C. Dunn < " target="_blank"> > wrote:

Only thing I can think of is this:

https://tickets.opscode.com/browse/CHEF-4794

- Julian

On Tue, Feb 11, 2014 at 4:58 PM, Stewart, Curtis
< "> > wrote:
> On a handful of recipes, we're getting the following errors and cannot seem
> to avoid them.  The pattern appears to be with any `Mixlib::ShellOut`
> commands.
>
> Working in a chef-repo.
>
> chef-client v11.8.0
> chefspec v3.1.4
>
> We're currently running specs on our entire repo through a Jenkins server.
>
> recipe code:
>
> cmd1 = Mixlib::ShellOut.new("s3cmd info #{node['app']['s3_source']} | grep
> MD5 | awk '{print $3}'").run_command
>
> error:
>
>  Errno::ENOMEM:
>        Cannot allocate memory - fork(2)
>
>
>
> Thanks,
> Curtis
>



--
[ Julian C. Dunn < "> >          * Sorry, I'm    ]
[ WWW: http://www.aquezada.com/staff/julian    * only Web 1.0  ]
[ gopher://sdf.org/1/users/keymaker/           * compliant!    ]
[ PGP: 91B3 7A9D 683C 7C16 715F 442C 6065 D533 FDC2 05B9       ]