[chef] Re: Re: Re: Re: Re: Re: Re: Re: berks upload error

[Michael Lindsay < >]

Hey all,

So I now have a fresh install of chefDK (knife -v Chef: 12.3.0, berks -v 3.2.4) and a brand new chef server (12.0.8).  berks update is still returning the same error.  When I `knife cookbook upload chef_handler -o ~/.berkshelf/cookbooks/`, I get this:

ERROR: Server returned error 500 for https://chef.DOMAIN.com/organizations/ORG/sandboxes/d9dcaaebaee9c6d69d55963db5afb9e4

Is this closer to the root of the problem?

On the server, I see the same erros as I do with berks:

2015-05-18_17:22:31.31151 [error] Checking presence of checksum: <<"5c059b160b3d288c0796ee1c964e0ca6">> for org <<"d324ac69246364aa17fdd9dcaaebaee9">> from bucket "bookshelf" has taken longer than 5000 ms

Followed by this:

2015-05-18_16:51:45.70811 [error] {<<"method=PUT; path=/organizations/ORG/sandboxes/d9dcaaebaee9e4daa96ffd80cb8245b5; status=500; ">>,{error,{throw,{checksum_check_error,23},[{chef_wm_named_sandbox,validate_checksums_uploaded,2,[{file,"src/chef_wm_named_sandbox.erl"},{line,142}]},{chef_wm_named_sandbox,from_json,2,[{file,"src/chef_wm_named_sandbox.erl"},{line,97}]},{webmachine_resource,resource_call,3,[{file,"src/webmachine_resource.erl"},{line,186}]},{webmachine_resource,do,3,[{file,"src/webmachine_resource.erl"},{line,142}]},{webmachine_decision_core,resource_call,1,[{file,"src/webmachine_decision_core.erl"},{line,48}]},{webmachine_decision_core,accept_helper,1,[{file,"src/webmachine_decision_core.erl"},{line,616}]},{webmachine_decision_core,decision,1,[{file,"src/webmachine_decision_core.erl"},{line,521}]},{webmachine_decision_core,handle_request,2,[{file,"src/webmachine_decision_core.erl"},{line,33}]}]}}}

I can get to the chef manage site and knife ssl check is still happy.  Any thoughts on where I should look next?  Is there any additional information I can provide that will help?

 - Michael

On Fri, May 15, 2015 at 11:32 AM, Michael Lindsay < " target="_blank"> > wrote:

Hey Daniel, 

Indeed, I had a number of things going on, among them an unpinned nodejs dependency.  I'm pretty well sorted now with our existing environment and I'm going to set up another client machine from scratch to be the one I talk to my new vpn chef server (until we cut over).  Will update on success or failure.

Thanks again!

 - Michael

On Fri, May 15, 2015 at 10:27 AM, Daniel DeLeo < " target="_blank"> > wrote:

On Thursday, May 14, 2015 at 2:28 PM, Michael Lindsay wrote:

> Sorry, more spamming my own thread....
>
> When I do berks update, I've started getting this error:
> Fetching 'nodejs' from " target="_blank"> (mailto: " target="_blank"> ):redguide/nodejs.git (at master)
> Ridley::Errors::FromFileParserError Could not parse `/var/folders/w5/1k5n_41n3fg_ph5nc4k3xwn80000gp/T/d20150514-32474-17tpmlb/metadata.rb': undefined method `source_url' for #<Ridley::Chef::Cookbook::Metadata:0x007f915c907de8>

I think `source_url` is a new addition to cookbook metadata that isn’t yet supported by the version of berkshelf you have.

> My colleague, who's knife/berks configuration do not appear to be totally broken is getting this:
> Fetching 'nodejs' from " target="_blank"> (mailto: " target="_blank"> ):redguide/nodejs.git (at master)
> The cookbook downloaded for nodejs (~> 2.2.0) did not satisfy the constraint.

This happens when you have a version constraint somewhere that says the nodejs cookbook has to be version ~> 2.2.0, but you’re pulling it from github and the version there doesn’t match that constraint.

> Not clear why this problem is cropping up now.

Neither of these seem related to your bookshelf problems, FWIW.

--
Daniel DeLeo