[chef] Re: Chef Server bootstrap fails on CentOS 6.2

[Bryan Baugher < >]

You may have run into this http://tickets.opscode.com/browse/COOK-886.

On Sun, Mar 4, 2012 at 10:30 PM, Van Fossan,Randy < "> > wrote:

The bootstrap method for installing chef-server is not working on CentOS 6.2.   I have tried 4 times now.     I have tried manually installing ruby 1.9.2-p290 and gems.  I have also tried using ruby that comes with CentOS 6.x and then installing the gems and it will not work.

Also of note is that after erlang is installed RabbitMQ-server will not start until the server is rebooted.   I then rerun the bootstrap and it runs to completion, but you can never get logged into the server's webui or connect via knife.   The ports are showing up (checked with netstat)

/var/log/chef/server.log
See ->  http://pastie.org/3523373

I then stopped the chef-server and chef-server-webui and started the chef-server on the command line..
If I try and start the chef-server on the command line, I get the following text..

# chef-server -N -e production
Merb root at: /usr/lib64/ruby/gems/1.8/gems/chef-server-api-0.10.8
 ~ No Gemfile found! If you're generating new app with merb-gen this is fine, otherwise run: bundle init to create Gemfile
Loading init file from ./config/init.rb
[Sun, 04 Mar 2012 22:51:22 -0500] INFO: Loading roles
/usr/lib64/ruby/gems/1.8/gems/mixlib-authentication-1.1.4/lib/mixlib/authentication/http_authentication_request.rb:25: warning: already initialized constant MANDATORY_HEADERS
/usr/lib64/ruby/gems/1.8/gems/mixlib-authentication-1.1.4/lib/mixlib/authentication/signatureverification.rb:28: warning: already initialized constant SignatureResponse
merb : chef-server (api) : worker (port 4000) ~ Starting Thin at port 4000
merb : chef-server (api) : worker (port 4000) ~ Using Thin adapter on host 0.0.0.0 and port 4000.
merb : chef-server (api) : worker (port 4000) ~ Successfully bound to port 4000


Help...

Randy

-Bryan