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

[Chris < >]

I set mine to 0.0.0.0, which worked for me.

On Mon, Mar 5, 2012 at 11:55 AM, Van Fossan,Randy < "> > 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"

 

signing_ca_path    "/var/chef/ca"

couchdb_url        "http:// mychef.myco.org:5984"

couchdb_database   'chef'

 

 

Thanks

  Randy

 

From: Chris [mailto: " target="_blank"> ]
Sent: Monday, March 05, 2012 11:59 AM
To: " target="_blank">
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". 

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

 

solr_url "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 < " target="_blank"> > 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: " target="_blank"> ]
Sent: Monday, March 05, 2012 11:51 AM
To: " target="_blank">
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 < " target="_blank"> > 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: " target="_blank">
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 " target="_blank">[mailto:
Sent: Monday, March 05, 2012 7:53 AM
To: " target="_blank">
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 < " target="_blank"> > 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

 

--
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.