[chef] Re: Re: Re: Re: New errors after upgrading Chef clients to 11.6

[Russell Bateman < >]

Perfect. This fixed my problem. /etc/hosts didn't have my hostname spelled as the client/nodename in the web UI. I also reconfigured my Chef server, though it's unclear it needed it.

Thanks for your help, Daniel!

On 09/05/2013 04:51 PM, Daniel DeLeo wrote:

" type="cite">

On Thursday, September 5, 2013 at 7:10 AM, Russell Bateman wrote:

Ah, thanks for replying. I did see a post on stackoverflow.com discussing chef-server.rb, but the problem wasn't exactly or even related, I think, to mine. As it sits, my Chef server installation, which is 11.0.8-1, does not have this file. At /etc/chef, I see nothing. At /etc/chef-server, I see

admin.pem
chef-server-running.json
chef-server-secrets.json
chef-validator.pem
chef-webui.pem

Did I succeed in misinstalling? (I used dpkg on Ubuntu Precise server.) Note that the web UI works perfectly well at this point and, as I say below, other stuff works like knife and even chef-client from other nodes.

chef-server.rb isn't created by default and if your hostname and such are correct you can run chef-server without one (default settings used). The root of the issue here is that chef-server is distributing URLs based on the server hosts view of its own FQDN. You could edit etc/hosts to have the correct hostname you want to talk to the server as and run 'chef-server-ctl reconfigure' to solve the problem as well.

-- 

Daniel DeLeo