Chef Server bootstrap fails on CentOS 6.2


#1

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


#2

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 vanfossr@oclc.org 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


#3

I am not sure that’s the issue. The services all start ok. The links
also look ok.

From: Bryan Baugher [mailto:bjbq4d@gmail.com]
Sent: Monday, March 05, 2012 7:53 AM
To: chef@lists.opscode.com
Subject: [chef] Re: Chef Server bootstrap fails on CentOS 6.2

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 vanfossr@oclc.org
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/aut
hentication/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/aut
hentication/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


#4

Hi Randy,

I did a test installation of Chef Server (0.10.8) on CentOS 6.2
following the instructions on the wiki0. The output of my entire
shell session is in this gist, including reboot.

https://raw.github.com/gist/1982742/16d9ca065fa3d9a7974ea8ddb0dcbad83373e1bf/gistfile1.txt

To note:

  • Ruby is from ‘base’, version 1.8.7.352-4.el6_2.
  • RubyGems 1.8.10 was installed from source.

The contents of the solo.rb and chef.json I used are in the output,
though I used the content from the server installation instructions
(with webui enabled).

Hope this helps!

On Sun, Mar 4, 2012 at 9:30 PM, Van Fossan,Randy vanfossr@oclc.org 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


#5

Thanks Joshua,

If I remove the CentOS repositories when installing Chef using the rbel repos, it seems to work. Although, I was getting chef 0.10.6 and had to upgrade to 0.10.8. It always proved problematic for me to use ruby 1.8.7 provided by the CentOS repos. I tried two different times.

Also, what version of couchdb did you end up with. I have tried upgrading our 0.11.2 version to 1.02 from the epel6 repo and chef no longer functions. It installed an updated erlang-ibrowse from that repo as well.

I will try again…
Randy

-----Original Message-----
From: Joshua Timberman [mailto:joshua@opscode.com]
Sent: Monday, March 05, 2012 8:39 PM
To: chef@lists.opscode.com
Subject: [chef] Re: Chef Server bootstrap fails on CentOS 6.2

Hi Randy,

I did a test installation of Chef Server (0.10.8) on CentOS 6.2 following the instructions on the wiki0. The output of my entire shell session is in this gist, including reboot.

https://raw.github.com/gist/1982742/16d9ca065fa3d9a7974ea8ddb0dcbad83373e1bf/gistfile1.txt

To note:

  • Ruby is from ‘base’, version 1.8.7.352-4.el6_2.
  • RubyGems 1.8.10 was installed from source.

The contents of the solo.rb and chef.json I used are in the output, though I used the content from the server installation instructions (with webui enabled).

Hope this helps!

On Sun, Mar 4, 2012 at 9:30 PM, Van Fossan,Randy vanfossr@oclc.org 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/a
uthentication/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/a
uthentication/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


#6

Hi Randy,

[root@centos6 ~]# rpm -q couchdb rabbitmq-server erlang ruby
couchdb-1.0.2-8.el6.x86_64
rabbitmq-server-2.6.1-1.el6.noarch
erlang-R14B-04.1.el6.x86_64
ruby-1.8.7.352-4.el6_2.x86_64

CouchDB is from EPEL, as are RabbitMQ and Erlang. Ruby is from updates.

Cheers!

On Tue, Mar 6, 2012 at 6:40 AM, Van Fossan,Randy vanfossr@oclc.org wrote:

Thanks Joshua,

If I remove the CentOS repositories when installing Chef using the rbel repos, it seems to work. Although, I was getting chef 0.10.6 and had to upgrade to 0.10.8. It always proved problematic for me to use ruby 1.8.7 provided by the CentOS repos. I tried two different times.

Also, what version of couchdb did you end up with. I have tried upgrading our 0.11.2 version to 1.02 from the epel6 repo and chef no longer functions. It installed an updated erlang-ibrowse from that repo as well.


#7

Thanks… I am in the process of reinstalling. However, RabbitMQ-server fails to start initially until I reboot… I am not sure what the problem is… Too little time, too many tangents… :O/

So far, This is what I have…
http://pastie.org/3534266

Did you notice in your install that your “yum install ruby ruby-devel ruby-ri ruby-rdoc ruby-shadow gcc gcc-c++ automake autoconf make curl dmidecode” did not install ruby shadow…
No package ruby-shadow available.

-----Original Message-----
From: Joshua Timberman [mailto:joshua@opscode.com]
Sent: Tuesday, March 06, 2012 1:43 PM
To: chef@lists.opscode.com
Subject: [chef] Re: RE: Re: Chef Server bootstrap fails on CentOS 6.2

Hi Randy,

[root@centos6 ~]# rpm -q couchdb rabbitmq-server erlang ruby
couchdb-1.0.2-8.el6.x86_64
rabbitmq-server-2.6.1-1.el6.noarch
erlang-R14B-04.1.el6.x86_64
ruby-1.8.7.352-4.el6_2.x86_64

CouchDB is from EPEL, as are RabbitMQ and Erlang. Ruby is from updates.

Cheers!

On Tue, Mar 6, 2012 at 6:40 AM, Van Fossan,Randy vanfossr@oclc.org wrote:

Thanks Joshua,

If I remove the CentOS repositories when installing Chef using the rbel repos, it seems to work. Although, I was getting chef 0.10.6 and had to upgrade to 0.10.8. It always proved problematic for me to use ruby 1.8.7 provided by the CentOS repos. I tried two different times.

Also, what version of couchdb did you end up with. I have tried upgrading our 0.11.2 version to 1.02 from the epel6 repo and chef no longer functions. It installed an updated erlang-ibrowse from that repo as well.