[chef] Re: Re: Chef12 - problem with chef-server-ctl org*


Chronological Thread 
  • From: Tiago Cruz < >
  • To: " " < >
  • Subject: [chef] Re: Re: Chef12 - problem with chef-server-ctl org*
  • Date: Mon, 8 Dec 2014 11:42:50 -0200

Hi Steven,

After

# rpm -e opscode-reporting
# chef-server-ctl reconfigure

The 'org' commands back to work  :)



On Mon, Dec 8, 2014 at 11:36 AM, Steven Danna < " target="_blank"> > wrote:
Hi,

It appears that the upstream for the organization (and other)
endpoints is pointing at opscode_account.  Opscode-account is the old
Enterprise Chef server that would have handled these accounts, but in
Chef Server 12, they should be handled by erchef.  Two possibilities
that I can think of here. One possibility is that you have old nginx
config on disk somewhere (or a pre-upgrade nginx still listening on
443) But, I believe from your other emails that you're upgrading from
open source 11, so that is unlikely.  Another possibility is that the
darklaunch configuration is incorrect. Darklaunch controls whether
particular features are turned on and certain routing decisions. Could
you send us a copy of the tarball generated by `chef-sever-ctl
gather-logs` off-list?

Cheers,

Steven

On Fri, Dec 5, 2014 at 7:17 PM, Tiago Cruz < "> > wrote:
> Hello,
>
> I created a new user:
>
> # chef-server-ctl user-create teste teste teste "> teste123
>
> Tried to put this new guy on my organization created during the upgrade:
>
> # chef-server-ctl org-user-add myorg teste
> ERROR: bad gateway
> Response: <html>
> <head><title>502 Bad Gateway</title></head>
> <body bgcolor="white">
> <center><h1>502 Bad Gateway</h1></center>
> <hr><center>ngx_openresty/1.4.3.6</center>
> </body>
> </html>
>
>
> Logs:
>
> ==> /var/log/opscode/nginx/error.log <==
> 2014/12/05 14:04:12 [error] 639#0: *252 no resolver defined to resolve
> opscode_account, client: 127.0.0.1, server: chef.infra.myorg.com.br,
> request: "POST /organizations/myorg/association_requests HTTP/1.1", host:
> "127.0.0.1:443"
>
> ==> /var/log/opscode/nginx/access.log <==
> 127.0.0.1 - - [05/Dec/2014:14:04:12 -0500]  "POST
> /organizations/myorg/association_requests HTTP/1.1" 502 "0.040" 182 "-"
> "Chef Knife/11.12.2 (ruby-1.9.3-p547; ohai-7.4.0; x86_64-linux;
> +http://opscode.com)" "-" "-" "-" "11.12.2" "algorithm=sha1;version=1.0;"
> "pivotal" "2014-12-05T19:04:12Z" "O4TqHyxsBd83E2SpWYkQXy0qoRM=" 1081
>
>
> -----
>
> And also:
>
> ~]# chef-server-ctl org-list
> ERROR: bad gateway
> Response: <html>
> <head><title>502 Bad Gateway</title></head>
> <body bgcolor="white">
> <center><h1>502 Bad Gateway</h1></center>
> <hr><center>ngx_openresty/1.4.3.6</center>
> </body>
> </html>
>
>
>
> Logs:
>
> ==> /var/log/opscode/nginx/error.log <==
> 2014/12/05 14:03:41 [error] 639#0: *250 no resolver defined to resolve
> opscode_account, client: 127.0.0.1, server: chef.infra.myorg.com.br,
> request: "GET /organizations HTTP/1.1", host: "127.0.0.1:443"
>
> ==> /var/log/opscode/nginx/access.log <==
> 127.0.0.1 - - [05/Dec/2014:14:03:41 -0500]  "GET /organizations HTTP/1.1"
> 502 "0.000" 182 "-" "Chef Knife/11.12.2 (ruby-1.9.3-p547; ohai-7.4.0;
> x86_64-linux; +http://opscode.com)" "-" "-" "-" "11.12.2"
> "algorithm=sha1;version=1.0;" "pivotal" "2014-12-05T19:03:41Z"
> "2jmj7l5rSw0yVb/vlWAYkK/YBwk=" 983
>
> Do you have some idea how to fix this?
>
> Thanks a lot!



--
-- Tiago Cruz




Archive powered by MHonArc 2.6.16.

§