# RE: Re: Chef Server bootstrap fails on CentOS 6.2

**URL:** <https://discourse.chef.io/t/re-re-chef-server-bootstrap-fails-on-centos-6-2/2628>\
**Category:** Chef Infra (archive)\
**Created:** [March 5, 2012, 4:34pm UTC](https://discourse.chef.io/t/re-re-chef-server-bootstrap-fails-on-centos-6-2/2628 "2012-03-05T16:34:59Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Van\_Fossan\_Randy](https://avatars.discourse-cdn.com/v4/letter/v/8797f3/32.png) [@Van\_Fossan\_Randy](https://discourse.chef.io/u/Van_Fossan_Randy)\
**Post date:** [March 5, 2012, 4:34pm UTC](https://discourse.chef.io/t/re-re-chef-server-bootstrap-fails-on-centos-6-2/2628/1 "2012-03-05T16:34:59Z")

</div>

Has anyone gotten chef-server 0.10.8 installed on CentOS6.x ? I have  
tried and tried and have no luck in getting it installed and running  
correctly. I have followed the WIKI steps and no luck. We do  
currently have a chef-server on CentOS 5.7 but are having issues with  
couchdb and a few other items. We can get couchdb to work correctly on  
CentOS 6.x

I guess, I will use the rbel repo (RHEL 6) install (chef 0.10.6 and  
couchdb 0.11.2) and then upgrade couchdb from the epel repos. Then  
finally upgrading chef with gem upgrade…

This is really a pain. Trying to get a stable chef-server installed on  
CentOS 6.2…

Anyone else have this kind of trouble on CentOS 6.2?

Randy

From: Van Fossan,Randy  
Sent: Monday, March 05, 2012 9:55 AM  
To: [chef@lists.opscode.com](mailto:chef@lists.opscode.com)  
Subject: RE: [chef] Re: Chef Server bootstrap fails on CentOS 6.2

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](mailto:bjbq4d@gmail.com)]  
Sent: Monday, March 05, 2012 7:53 AM  
To: [chef@lists.opscode.com](mailto: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](http://tickets.opscode.com/browse/COOK-886).

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

---

<div class="post-metadata">

**Author:** ![Chris](https://avatars.discourse-cdn.com/v4/letter/c/958977/32.png) [@Chris](https://discourse.chef.io/u/Chris)\
**Post date:** [March 5, 2012, 4:50pm UTC](https://discourse.chef.io/t/re-re-chef-server-bootstrap-fails-on-centos-6-2/2628/2 "2012-03-05T16:50:58Z")

</div>

Is there any reason you couldn't split off Couchdb?  
Run the API/UI/Solr/Expander on your Centos 5.7 node and Couchdb on the 6.2  
node.

On Mon, Mar 5, 2012 at 8:34 AM, Van Fossan,Randy [vanfossr@oclc.org](mailto:vanfossr@oclc.org) wrote:

> Has anyone gotten chef-server 0.10.8 installed on CentOS6.x ? I have  
> tried and tried and have no luck in getting it installed and running  
> correctly. I have followed the WIKI steps and no luck. We do currently  
> have a chef-server on CentOS 5.7 but are having issues with couchdb and a  
> few other items. We can get couchdb to work correctly on CentOS 6.x\*\*\*\*
> 
> * * *
> 
> I guess, I will use the rbel repo (RHEL 6) install (chef 0.10.6 and  
> couchdb 0.11.2) and then upgrade couchdb from the epel repos. Then finally  
> upgrading chef with gem upgrade..\*\*\*\*
> 
> * * *
> 
> This is really a pain. Trying to get a stable chef-server installed on  
> CentOS 6.2.. \*\*\*\*
> 
> * * *
> 
> Anyone else have this kind of trouble on CentOS 6.2?\*\*\*\*
> 
> * * *
> 
> Randy\*\*\*\*
> 
> * * *
> 
> _From:_ Van Fossan,Randy  
> _Sent:_ Monday, March 05, 2012 9:55 AM  
> _To:_ [chef@lists.opscode.com](mailto:chef@lists.opscode.com)  
> _Subject:_ RE: [chef] Re: Chef Server bootstrap fails on CentOS 6.2\*\*\*\*
> 
> * * *
> 
> 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](mailto:bjbq4d@gmail.com)]  
> _Sent:_ Monday, March 05, 2012 7:53 AM  
> _To:_ [chef@lists.opscode.com](mailto: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.](http://tickets.opscode.com/browse/COOK-886.)\*\*\*\*
> 
> * * *
> 
> On Sun, Mar 4, 2012 at 10:30 PM, Van Fossan,Randy [vanfossr@oclc.org](mailto: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](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\*\*\*\*

--  
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent  
permitted by applicable law.

---

<div class="post-metadata">

**Author:** ![Van\_Fossan\_Randy](https://avatars.discourse-cdn.com/v4/letter/v/8797f3/32.png) [@Van\_Fossan\_Randy](https://discourse.chef.io/u/Van_Fossan_Randy)\
**Post date:** [March 5, 2012, 4:54pm UTC](https://discourse.chef.io/t/re-re-chef-server-bootstrap-fails-on-centos-6-2/2628/3 "2012-03-05T16:54:02Z")

</div>

I suppose, I could split it off. I do not know exactly what I would  
need to change to point the chef-server to the new couchdb server. I  
am not sure what to do for rabbitmq-server either.

Please advise.

From: Chris [[mailto:grocerylist@gmail.com](mailto:grocerylist@gmail.com)]  
Sent: Monday, March 05, 2012 11:51 AM  
To: [chef@lists.opscode.com](mailto:chef@lists.opscode.com)  
Subject: [chef] Re: RE: Re: Chef Server bootstrap fails on CentOS 6.2

Is there any reason you couldn’t split off Couchdb?

Run the API/UI/Solr/Expander on your Centos 5.7 node and Couchdb on the  
6.2 node.

On Mon, Mar 5, 2012 at 8:34 AM, Van Fossan,Randy [vanfossr@oclc.org](mailto:vanfossr@oclc.org)  
wrote:

Has anyone gotten chef-server 0.10.8 installed on CentOS6.x ? I have  
tried and tried and have no luck in getting it installed and running  
correctly. I have followed the WIKI steps and no luck. We do  
currently have a chef-server on CentOS 5.7 but are having issues with  
couchdb and a few other items. We can get couchdb to work correctly on  
CentOS 6.x

I guess, I will use the rbel repo (RHEL 6) install (chef 0.10.6 and  
couchdb 0.11.2) and then upgrade couchdb from the epel repos. Then  
finally upgrading chef with gem upgrade…

This is really a pain. Trying to get a stable chef-server installed on  
CentOS 6.2…

Anyone else have this kind of trouble on CentOS 6.2?

Randy

From: Van Fossan,Randy  
Sent: Monday, March 05, 2012 9:55 AM  
To: [chef@lists.opscode.com](mailto:chef@lists.opscode.com)  
Subject: RE: [chef] Re: Chef Server bootstrap fails on CentOS 6.2

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](mailto:bjbq4d@gmail.com)]  
Sent: Monday, March 05, 2012 7:53 AM  
To: [chef@lists.opscode.com](mailto: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](http://tickets.opscode.com/browse/COOK-886).

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

–  
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent  
permitted by applicable law.

---

<div class="post-metadata">

**Author:** ![Chris](https://avatars.discourse-cdn.com/v4/letter/c/958977/32.png) [@Chris](https://discourse.chef.io/u/Chris)\
**Post date:** [March 5, 2012, 4:58pm UTC](https://discourse.chef.io/t/re-re-chef-server-bootstrap-fails-on-centos-6-2/2628/4 "2012-03-05T16:58:59Z")

</div>

We had problems with Couchdb on Centos 5.x as well, so we split it off  
along with rabbit/solr/expander to an Ubuntu node. To point the API at the  
new node you'll need to make sure the Couch binds to the network interface  
not just the loopback. You'll also need to change server.rb and add  
couchdb\_url "[http://couchdbserver:5984](http://couchdbserver:5984)".  
If you split off solr/rabbit you need to add:

solr\_url "[http://solrserver:8983](http://solrserver:8983)

ampq\_host  
ampq\_port  
ampq\_user  
ampq\_pass  
ampq\_vhost

On Mon, Mar 5, 2012 at 8:54 AM, Van Fossan,Randy [vanfossr@oclc.org](mailto:vanfossr@oclc.org) wrote:

> I suppose, I could split it off. I do not know exactly what I would need  
> to change to point the chef-server to the new couchdb server. I am not  
> sure what to do for rabbitmq-server either.\*\*\*\*
> 
> * * *
> 
> Please advise.\*\*\*\*
> 
> * * *
> 
> _From:_ Chris [[mailto:grocerylist@gmail.com](mailto:grocerylist@gmail.com)]  
> _Sent:_ Monday, March 05, 2012 11:51 AM  
> _To:_ [chef@lists.opscode.com](mailto:chef@lists.opscode.com)  
> _Subject:_ [chef] Re: RE: Re: Chef Server bootstrap fails on CentOS 6.2\*\*\*  
> \*
> 
> * * *
> 
> Is there any reason you couldn't split off Couchdb?\*\*\*\*
> 
> Run the API/UI/Solr/Expander on your Centos 5.7 node and Couchdb on the  
> 6.2 node.\*\*\*\*
> 
> On Mon, Mar 5, 2012 at 8:34 AM, Van Fossan,Randy [vanfossr@oclc.org](mailto:vanfossr@oclc.org)  
> wrote:\*\*\*\*
> 
> Has anyone gotten chef-server 0.10.8 installed on CentOS6.x ? I have  
> tried and tried and have no luck in getting it installed and running  
> correctly. I have followed the WIKI steps and no luck. We do currently  
> have a chef-server on CentOS 5.7 but are having issues with couchdb and a  
> few other items. We can get couchdb to work correctly on CentOS 6.x\*\*\*\*
> 
> * * *
> 
> I guess, I will use the rbel repo (RHEL 6) install (chef 0.10.6 and  
> couchdb 0.11.2) and then upgrade couchdb from the epel repos. Then finally  
> upgrading chef with gem upgrade..\*\*\*\*
> 
> * * *
> 
> This is really a pain. Trying to get a stable chef-server installed on  
> CentOS 6.2.. \*\*\*\*
> 
> * * *
> 
> Anyone else have this kind of trouble on CentOS 6.2?\*\*\*\*
> 
> * * *
> 
> Randy\*\*\*\*
> 
> * * *
> 
> _From:_ Van Fossan,Randy  
> _Sent:_ Monday, March 05, 2012 9:55 AM  
> _To:_ [chef@lists.opscode.com](mailto:chef@lists.opscode.com)  
> _Subject:_ RE: [chef] Re: Chef Server bootstrap fails on CentOS 6.2\*\*\*\*
> 
> * * *
> 
> 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](mailto:bjbq4d@gmail.com)]  
> _Sent:_ Monday, March 05, 2012 7:53 AM  
> _To:_ [chef@lists.opscode.com](mailto: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.](http://tickets.opscode.com/browse/COOK-886.)\*\*\*\*
> 
> * * *
> 
> On Sun, Mar 4, 2012 at 10:30 PM, Van Fossan,Randy [vanfossr@oclc.org](mailto: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](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\*\*\*\*
> 
> * * *
> 
> * * *
> 
> --  
> Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent  
> permitted by applicable law.\*\*\*\*

--  
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent  
permitted by applicable law.

---

<div class="post-metadata">

**Author:** ![Bryan\_Berry](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/bryan_berry/32/213_2.png) [@Bryan\_Berry](https://discourse.chef.io/u/Bryan_Berry)\
**Post date:** [March 5, 2012, 5:31pm UTC](https://discourse.chef.io/t/re-re-chef-server-bootstrap-fails-on-centos-6-2/2628/5 "2012-03-05T17:31:39Z")

</div>

I have gotten chef server 10.6 running on two different rhel 6.2 servers. I  
can't recall your particular problem, but given the time I could probably  
figure it out. I thought it had to do with a path issue  
On Mar 5, 2012 5:35 PM, "Van Fossan,Randy" [vanfossr@oclc.org](mailto:vanfossr@oclc.org) wrote:

> Has anyone gotten chef-server 0.10.8 installed on CentOS6.x ? I have  
> tried and tried and have no luck in getting it installed and running  
> correctly. I have followed the WIKI steps and no luck. We do currently  
> have a chef-server on CentOS 5.7 but are having issues with couchdb and a  
> few other items. We can get couchdb to work correctly on CentOS 6.x\*\*\*\*
> 
> * * *
> 
> I guess, I will use the rbel repo (RHEL 6) install (chef 0.10.6 and  
> couchdb 0.11.2) and then upgrade couchdb from the epel repos. Then finally  
> upgrading chef with gem upgrade..\*\*\*\*
> 
> * * *
> 
> This is really a pain. Trying to get a stable chef-server installed on  
> CentOS 6.2.. \*\*\*\*
> 
> * * *
> 
> Anyone else have this kind of trouble on CentOS 6.2?\*\*\*\*
> 
> * * *
> 
> Randy\*\*\*\*
> 
> * * *
> 
> _From:_ Van Fossan,Randy  
> _Sent:_ Monday, March 05, 2012 9:55 AM  
> _To:_ [chef@lists.opscode.com](mailto:chef@lists.opscode.com)  
> _Subject:_ RE: [chef] Re: Chef Server bootstrap fails on CentOS 6.2\*\*\*\*
> 
> * * *
> 
> 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](mailto:bjbq4d@gmail.com)]  
> _Sent:_ Monday, March 05, 2012 7:53 AM  
> _To:_ [chef@lists.opscode.com](mailto: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.](http://tickets.opscode.com/browse/COOK-886.)\*\*\*\*
> 
> * * *
> 
> On Sun, Mar 4, 2012 at 10:30 PM, Van Fossan,Randy [vanfossr@oclc.org](mailto: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](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\*\*\*\*

---

<div class="post-metadata">

**Author:** ![Van\_Fossan\_Randy](https://avatars.discourse-cdn.com/v4/letter/v/8797f3/32.png) [@Van\_Fossan\_Randy](https://discourse.chef.io/u/Van_Fossan_Randy)\
**Post date:** [March 5, 2012, 5:39pm UTC](https://discourse.chef.io/t/re-re-chef-server-bootstrap-fails-on-centos-6-2/2628/6 "2012-03-05T17:39:18Z")

</div>

One thing I notice is that on CentOS 6.x the gems are installed in  
/usr/lib64/ruby/gems/1.8/gems/ as opposed to  
/usr/lib/ruby/gems/1.8/gems/ on CentOS 5.7 in which ruby and gems were  
installed from .

If I unsubscribed to the base and update repo’s (or disabled them), I  
could try the rbel versions of ruby… That might help…??

Randy

From: Bryan Berry [[mailto:bryan.berry@gmail.com](mailto:bryan.berry@gmail.com)]  
Sent: Monday, March 05, 2012 12:32 PM  
To: [chef@lists.opscode.com](mailto:chef@lists.opscode.com)  
Subject: [chef] Re: RE: Re: Chef Server bootstrap fails on CentOS 6.2

I have gotten chef server 10.6 running on two different rhel 6.2  
servers. I can’t recall your particular problem, but given the time I  
could probably figure it out. I thought it had to do with a path issue

On Mar 5, 2012 5:35 PM, “Van Fossan,Randy” [vanfossr@oclc.org](mailto:vanfossr@oclc.org) wrote:

Has anyone gotten chef-server 0.10.8 installed on CentOS6.x ? I have  
tried and tried and have no luck in getting it installed and running  
correctly. I have followed the WIKI steps and no luck. We do  
currently have a chef-server on CentOS 5.7 but are having issues with  
couchdb and a few other items. We can get couchdb to work correctly on  
CentOS 6.x

I guess, I will use the rbel repo (RHEL 6) install (chef 0.10.6 and  
couchdb 0.11.2) and then upgrade couchdb from the epel repos. Then  
finally upgrading chef with gem upgrade…

This is really a pain. Trying to get a stable chef-server installed on  
CentOS 6.2…

Anyone else have this kind of trouble on CentOS 6.2?

Randy

From: Van Fossan,Randy  
Sent: Monday, March 05, 2012 9:55 AM  
To: [chef@lists.opscode.com](mailto:chef@lists.opscode.com)  
Subject: RE: [chef] Re: Chef Server bootstrap fails on CentOS 6.2

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](mailto:bjbq4d@gmail.com)]  
Sent: Monday, March 05, 2012 7:53 AM  
To: [chef@lists.opscode.com](mailto: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](http://tickets.opscode.com/browse/COOK-886).

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

---

<div class="post-metadata">

**Author:** ![Van\_Fossan\_Randy](https://avatars.discourse-cdn.com/v4/letter/v/8797f3/32.png) [@Van\_Fossan\_Randy](https://discourse.chef.io/u/Van_Fossan_Randy)\
**Post date:** [March 5, 2012, 7:55pm UTC](https://discourse.chef.io/t/re-re-chef-server-bootstrap-fails-on-centos-6-2/2628/7 "2012-03-05T19:55:09Z")

</div>

Chris,

I tried changing the setting below and it did not work… I wanted to  
make sure that it could communicate correctly with the parameters you  
specified before pointing it to a new server. What am I missing?

/etc/couchdb/local.ini

[httpd]

port = 5984

bind\_address = ip\_of\_current\_chefserver (note this is currently the  
same server)

; Uncomment next line to trigger basic-auth popup on unauthorized  
requests.

;WWW-Authenticate = Basic realm=“administrator”

# cat /etc/chef/server.rb

log\_level :info

log\_location STDOUT

ssl\_verify\_mode :verify\_none

chef\_server\_url “[http://mychef.myco.org:4000](http://mychef.myco.org:4000)”

signing\_ca\_path “/var/chef/ca”

couchdb\_url “http:// [mychef.myco.org:5984](http://mychef.myco.org:5984)”

couchdb\_database ‘chef’

Thanks

Randy

From: Chris [[mailto:grocerylist@gmail.com](mailto:grocerylist@gmail.com)]  
Sent: Monday, March 05, 2012 11:59 AM  
To: [chef@lists.opscode.com](mailto:chef@lists.opscode.com)  
Subject: [chef] Re: RE: Re: RE: Re: Chef Server bootstrap fails on  
CentOS 6.2

We had problems with Couchdb on Centos 5.x as well, so we split it off  
along with rabbit/solr/expander to an Ubuntu node. To point the API at  
the new node you’ll need to make sure the Couch binds to the network  
interface not just the loopback. You’ll also need to change server.rb  
and add couchdb\_url “[http://couchdbserver:5984](http://couchdbserver:5984)”.

If you split off solr/rabbit you need to add:

solr\_url "[http://solrserver:8983](http://solrserver:8983)

ampq\_host

ampq\_port

ampq\_user

ampq\_pass

ampq\_vhost

On Mon, Mar 5, 2012 at 8:54 AM, Van Fossan,Randy [vanfossr@oclc.org](mailto:vanfossr@oclc.org)  
wrote:

I suppose, I could split it off. I do not know exactly what I would  
need to change to point the chef-server to the new couchdb server. I  
am not sure what to do for rabbitmq-server either.

Please advise.

From: Chris [[mailto:grocerylist@gmail.com](mailto:grocerylist@gmail.com)]  
Sent: Monday, March 05, 2012 11:51 AM  
To: [chef@lists.opscode.com](mailto:chef@lists.opscode.com)  
Subject: [chef] Re: RE: Re: Chef Server bootstrap fails on CentOS 6.2

Is there any reason you couldn’t split off Couchdb?

Run the API/UI/Solr/Expander on your Centos 5.7 node and Couchdb on the  
6.2 node.

On Mon, Mar 5, 2012 at 8:34 AM, Van Fossan,Randy [vanfossr@oclc.org](mailto:vanfossr@oclc.org)  
wrote:

Has anyone gotten chef-server 0.10.8 installed on CentOS6.x ? I have  
tried and tried and have no luck in getting it installed and running  
correctly. I have followed the WIKI steps and no luck. We do  
currently have a chef-server on CentOS 5.7 but are having issues with  
couchdb and a few other items. We can get couchdb to work correctly on  
CentOS 6.x

I guess, I will use the rbel repo (RHEL 6) install (chef 0.10.6 and  
couchdb 0.11.2) and then upgrade couchdb from the epel repos. Then  
finally upgrading chef with gem upgrade…

This is really a pain. Trying to get a stable chef-server installed on  
CentOS 6.2…

Anyone else have this kind of trouble on CentOS 6.2?

Randy

From: Van Fossan,Randy  
Sent: Monday, March 05, 2012 9:55 AM  
To: [chef@lists.opscode.com](mailto:chef@lists.opscode.com)  
Subject: RE: [chef] Re: Chef Server bootstrap fails on CentOS 6.2

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](mailto:bjbq4d@gmail.com)]  
Sent: Monday, March 05, 2012 7:53 AM  
To: [chef@lists.opscode.com](mailto: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](http://tickets.opscode.com/browse/COOK-886).

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

–  
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent  
permitted by applicable law.

–  
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent  
permitted by applicable law.

---

<div class="post-metadata">

**Author:** ![Chris](https://avatars.discourse-cdn.com/v4/letter/c/958977/32.png) [@Chris](https://discourse.chef.io/u/Chris)\
**Post date:** [March 5, 2012, 8:11pm UTC](https://discourse.chef.io/t/re-re-chef-server-bootstrap-fails-on-centos-6-2/2628/8 "2012-03-05T20:11:55Z")

</div>

I set mine to 0.0.0.0, which worked for me.

On Mon, Mar 5, 2012 at 11:55 AM, Van Fossan,Randy [vanfossr@oclc.org](mailto:vanfossr@oclc.org) wrote:

> Chris,\*\*\*\*
> 
> I tried changing the setting below and it did not work.. I wanted to  
> make sure that it could communicate correctly with the parameters you  
> specified before pointing it to a new server. What am I missing?\*\*\*\*
> 
> * * *
> 
> /etc/couchdb/local.ini\*\*\*\*
> 
> [httpd]\*\*\*\*
> 
> port = 5984\*\*\*\*
> 
> bind\_address = ip\_of\_current\_chefserver (note this is currently the same  
> server)\*\*\*\*
> 
> ; Uncomment next line to trigger basic-auth popup on unauthorized requests.
> 
> * * *
> 
> ;WWW-Authenticate = Basic realm="administrator"\*\*\*\*
> 
> * * *
> 
> # cat /etc/chef/server.rb\*\*\*\*
> 
> log\_level :info\*\*\*\*
> 
> log\_location STDOUT\*\*\*\*
> 
> ssl\_verify\_mode :verify\_none\*\*\*\*
> 
> chef\_server\_url "[http://mychef.myco.org:4000](http://mychef.myco.org:4000)"\*\*\*\*
> 
> * * *
> 
> signing\_ca\_path "/var/chef/ca"\*\*\*\*
> 
> couchdb\_url "http:// [mychef.myco.org:5984](http://mychef.myco.org:5984)"\*\*\*\*
> 
> couchdb\_database 'chef'\*\*\*\*
> 
> * * *
> 
> * * *
> 
> Thanks\*\*\*\*
> 
> Randy\*\*\*\*
> 
> * * *
> 
> _From:_ Chris [[mailto:grocerylist@gmail.com](mailto:grocerylist@gmail.com)]  
> _Sent:_ Monday, March 05, 2012 11:59 AM  
> _To:_ [chef@lists.opscode.com](mailto:chef@lists.opscode.com)  
> _Subject:_ [chef] Re: RE: Re: RE: Re: Chef Server bootstrap fails on  
> CentOS 6.2\*\*\*\*
> 
> * * *
> 
> We had problems with Couchdb on Centos 5.x as well, so we split it off  
> along with rabbit/solr/expander to an Ubuntu node. To point the API at the  
> new node you'll need to make sure the Couch binds to the network interface  
> not just the loopback. You'll also need to change server.rb and add  
> couchdb\_url "[http://couchdbserver:5984](http://couchdbserver:5984)". \*\*\*\*
> 
> If you split off solr/rabbit you need to add:\*\*\*\*
> 
> * * *
> 
> solr\_url "[http://solrserver:8983](http://solrserver:8983)\*\*\*\*
> 
> * * *
> 
> ampq\_host \*\*\*\*
> 
> ampq\_port\*\*\*\*
> 
> ampq\_user\*\*\*\*
> 
> ampq\_pass\*\*\*\*
> 
> ampq\_vhost \*\*\*\*
> 
> On Mon, Mar 5, 2012 at 8:54 AM, Van Fossan,Randy [vanfossr@oclc.org](mailto:vanfossr@oclc.org)  
> wrote:\*\*\*\*
> 
> I suppose, I could split it off. I do not know exactly what I would need  
> to change to point the chef-server to the new couchdb server. I am not  
> sure what to do for rabbitmq-server either.\*\*\*\*
> 
> * * *
> 
> Please advise.\*\*\*\*
> 
> * * *
> 
> _From:_ Chris [[mailto:grocerylist@gmail.com](mailto:grocerylist@gmail.com)]  
> _Sent:_ Monday, March 05, 2012 11:51 AM  
> _To:_ [chef@lists.opscode.com](mailto:chef@lists.opscode.com)  
> _Subject:_ [chef] Re: RE: Re: Chef Server bootstrap fails on CentOS 6.2\*\*\*  
> \*
> 
> * * *
> 
> Is there any reason you couldn't split off Couchdb?\*\*\*\*
> 
> Run the API/UI/Solr/Expander on your Centos 5.7 node and Couchdb on the  
> 6.2 node.\*\*\*\*
> 
> On Mon, Mar 5, 2012 at 8:34 AM, Van Fossan,Randy [vanfossr@oclc.org](mailto:vanfossr@oclc.org)  
> wrote:\*\*\*\*
> 
> Has anyone gotten chef-server 0.10.8 installed on CentOS6.x ? I have  
> tried and tried and have no luck in getting it installed and running  
> correctly. I have followed the WIKI steps and no luck. We do currently  
> have a chef-server on CentOS 5.7 but are having issues with couchdb and a  
> few other items. We can get couchdb to work correctly on CentOS 6.x\*\*\*\*
> 
> * * *
> 
> I guess, I will use the rbel repo (RHEL 6) install (chef 0.10.6 and  
> couchdb 0.11.2) and then upgrade couchdb from the epel repos. Then finally  
> upgrading chef with gem upgrade..\*\*\*\*
> 
> * * *
> 
> This is really a pain. Trying to get a stable chef-server installed on  
> CentOS 6.2.. \*\*\*\*
> 
> * * *
> 
> Anyone else have this kind of trouble on CentOS 6.2?\*\*\*\*
> 
> * * *
> 
> Randy\*\*\*\*
> 
> * * *
> 
> _From:_ Van Fossan,Randy  
> _Sent:_ Monday, March 05, 2012 9:55 AM  
> _To:_ [chef@lists.opscode.com](mailto:chef@lists.opscode.com)  
> _Subject:_ RE: [chef] Re: Chef Server bootstrap fails on CentOS 6.2\*\*\*\*
> 
> * * *
> 
> 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](mailto:bjbq4d@gmail.com)]  
> _Sent:_ Monday, March 05, 2012 7:53 AM  
> _To:_ [chef@lists.opscode.com](mailto: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.](http://tickets.opscode.com/browse/COOK-886.)\*\*\*\*
> 
> * * *
> 
> On Sun, Mar 4, 2012 at 10:30 PM, Van Fossan,Randy [vanfossr@oclc.org](mailto: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](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\*\*\*\*
> 
> * * *
> 
> * * *
> 
> --  
> Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent  
> permitted by applicable law.\*\*\*\*
> 
> * * *
> 
> * * *
> 
> --  
> Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent  
> permitted by applicable law.\*\*\*\*

--  
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent  
permitted by applicable law.