- From: Jeff Blaine <
>
- To:
- Subject: [chef] Re: Re: Sending HTTP Request ... NoMethodError: undefined method `closed?' for nil:NilClass
- Date: Mon, 08 Jul 2013 16:55:47 -0400
On 7/8/2013 4:37 PM, Daniel DeLeo wrote:
*Groan* Some Ruby net/http bug is blowing up the thing that's supposed
to give you a pretty/humane error message. As best I can tell, you're
getting a HTTP 400 back from the server. Anything in the server logs
(`chef-server-ctl tail` if you're on Chef 11)?
Daniel,
Thanks for the reply.
Nothing of use in chef-server-ctl tail. The request never reached the
Chef server from what I can tell.
I did, however, solve this instance of this ugliness. I learned (perhaps
now that it is documented?) of the no_proxy client.rb setting and
configured things to make use of that the first time around and forever
afterwards via the chef-client cookbook we were already using.
It still does not explain how everything has been working fine for 5
months without the use of no_proxy. I don't see myself digging into that
further though due to lack of time.
Archive powered by MHonArc 2.6.16.