- From: Daniel DeLeo <
>
- To:
- Subject: [chef] Re: chef-client issues: trying to connect to localhost
- Date: Sat, 8 Jan 2011 17:03:28 -0800
Most likely you haven't configured your proxy to set the correct
HTTP_X_FORWARDED_HOST header.
On Sat, Jan 8, 2011 at 4:29 PM, Kirk Richey
<
>
wrote:
>
The gist is here
>
https://gist.github.com/771256
>
>
##
>
# Node:
>
# Rackspace Cloud Server
>
# Ubuntu 10.04 LTS
>
# Hosted Chef Server
>
# Package install 10.04
>
#
>
http://wiki.opscode.com/display/chef/Package+Installation+on+Debian+and+Ubuntu
>
# Using nginx for ssl
>
# http://warwickp.com/2010/10/hosting-chef-server-behind-nginx-proxy
>
##
>
>
>
# Bootstrap works with no problems
>
$ knife bootstrap XXX.XXX.XXX.XXX -x root -P XXXXX -d ubuntu10.04-apt -l
>
debug
>
>
# New node shows up
>
$ knife node list
>
[
>
"local-workstation.local",
>
"web-app"
>
]
>
>
>
$ knife node run_list add web-app 'role[base]'
>
{
>
"run_list": [
>
"role[base]"
>
]
>
}
>
>
# Confirm run list
>
knife node show web-app -r
>
{
>
"run_list": [
>
"role[base]"
>
]
>
}
>
>
>
# And the fuckary begins
>
>
# Doesn't work
>
web-app $ chef-client -l debug
>
>
# It shits out this error
>
retriable_rest_request: Connection refused - Connection refused connecting
>
to localhost:4000 for
>
/cookbooks/runit/0.14.1/files/ac87b692389b0d9d99e628a9f25fba19, giving up
>
(Errno::ECONNREFUSED)
>
>
# I have no clue why the chef-run is trying to connect to localhost:4000
>
instead of my chef server.
>
# I examined the debug output from the chef run. And I found this...
>
>
X-Ops-UserId:web-app'
>
Header hash: {"X-Ops-Content-Hash"=>"2jmj7l5rSw0yVb/vlWAYkK/YBwk=",
>
"X-Ops-Authorization-1"=>"4wnsQ+...", "X-Ops-Userid"=>"web-app",
>
"X-Ops-Sign"=>"version=1.0", "X-Ops-Authorization-2"=>"nfg...",
>
"X-Ops-Authorization-3"=>"cfHD...", "X-Ops-Authorization-4"=>"DxbX...",
>
"X-Ops-Authorization-5"=>"xie...", "X-Ops-Authorization-6"=>"lGdE...",
>
"X-Ops-Timestamp"=>"2011-01-08T18:39:41Z"}
>
[Sat, 08 Jan 2011 18:39:41 +0000] DEBUG: Sending HTTP Request via GET to
>
chef.my-chef-server.com:443/nodes/web-app/cookbooks
>
[Sat, 08 Jan 2011 18:39:42 +0000] DEBUG: Cookbooks to load:
>
{"runit"=>#<Chef::CookbookVersion:0x7fe831bc8b78 @file_vendor=nil,
>
@couchdb_rev=nil, @definition_filenames=["runit_service.rb"],
>
@manifest_records_by_path={"templates/gentoo/runit-start.sh.erb"=>{"name"=>"runit-start.sh.erb",
>
>
"url"=>"http://localhost:4000/cookbooks/runit/0.14.1/files/bd03533917da171167995131c075ea43",
>
"checksum"=>"bd03533917da171167995131c075ea43",
>
"path"=>"templates/gentoo/runit-start.sh.erb", "specificity"=>"gentoo"}....
>
>
# I'm clueless to why these cookbooks have
>
"url"=>"http://localhost:4000/..." instead of my chef server url
>
# /etc/chef/client.rb contains the correct chef server url
>
>
web-app $ chef-client -c /etc/chef/client.rb
>
# Fails for the same localhost reasons
>
>
# THIS WORKS
>
web-app $ chef-client -S http://chef.my-chef-server.com:4000
>
# The logs show the cookbooks have
>
"url"=>"http://chef.my-chef-server.com:4000" instead of localhost
>
>
##
>
# Nginx on my chef server is an apt-get install
>
# And my chef server web ui works
>
##
>
>
##
>
# ANY HALP WUD BE GREATLY APPRECIATD
>
##
>
>
>
>
>
>
>
>
>
Archive powered by MHonArc 2.6.16.