- From: Steven Danna <
>
- To: <
>
- Subject: [chef] Re: ngx_openresty error?
- Date: Mon, 27 May 2013 13:33:25 -0700
Hi,
On 5/27/13 9:59 AM, Liam Kirsher wrote:
>
ngx_openresty must be required by one of my cookbooks (nginx,
>
application_nginx?), and there appears to be an error in the version
>
string, due to trailing '.'
>
> '0.9.' does not match 'x.y.z' or 'x.y'
>
So, that's one issue.
Updating the solve gem to 0.4.4 and then re-uploading your cookbooks
should resolve this issue. The cause is a bug in Chef Server that is
exercised by older versions of the solve gem.
>
>
But, what I /really/ don't understand here is why it's trying to load
>
ngx_openresty when I'm just using the tutorial cookbooks: ["apt",
>
"aliases", "apache2", "networking_basic"]
>
Oh. Wait, that must be an error coming from the opscode server.
>
>
Keep in mind that I'm new to Chef, so there's probably something obvious
>
I'm just not getting.
I think you might just be getting thrown off by the response headers in
the debug log. The following:
>
> [2013-05-27T16:02:54+00:00] DEBUG: server: ngx_openresty
simply means that the server responding to your api request is using
ngx_openresty. That is, Hosted Chef uses openresty as part of the
underlying infrastructure used to respond to your request.
The problem is likely a 2-digit version constraint in one of the
cookbooks in your run_list (or one of their dependencies). Reuploading
via `knife cookbook upload` or via berkshelf with a recent version of
the "solve" gem installed should resolve the issue.
Cheers,
Steven
--
Steven Danna
Systems Engineer, Opscode, Inc
GPG Key:
http://stevendanna.github.com/downloads/code/public.key
Attachment:
signature.asc
Description: OpenPGP digital signature
Archive powered by MHonArc 2.6.16.