[chef] Re: Re: Re: bluepill error uninitialized constant Daemonization (NameError)

[Sachin Sagar Rai < >]

Hi, I am really frustrated with the installation of the chef-server via the cookbook.

I almost tried every possible way to installing chef-server and every time I face a new error. Is it just me or anybody else too? Or am I so stupid enough!!

Due to the installation problem with the rubygems n bluepill way, I tried to install using the default recipe.

Here too, I failed with the error: [Sun, 19 Feb 2012 17:09:59 +0000] FATAL: Errno::ECONNREFUSED: http_request[compact chef couchDB] (chef-server::default line 24) had an error: Errno::ECONNREFUSED: Connection refused - connect(2)

This time the chef_server role I modified is:

name "chef_server"

description "Setup a chef-server on an instance"

run_list(

  "recipe[chef-server]"

)

override_attributes(

  :chef_server => {

    :init_style => 'init',

    :webui_enabled => true

  }

)

and the debug-log at: https://gist.github.com/1864698

Why isn't it stable enough or I might be lacking the experience?

Sometimes it gets so frustrating!!!

-------------------------------------------

@millisami
~ Sachin Sagar Rai
Ruby on Rails Developer
http://tfm.com.np
http://nepalonrails.tumblr.com

Sent with Sparrow

On Sunday, February 19, 2012 at 3:48 AM, Joshua Timberman wrote:

On Sat, Feb 18, 2012 at 6:15 AM, Akzhan Abdulin

< "> > wrote:

This is problem that refs bluepill/131, bluepill/132, bluepill/136 (Author

of Daemons gem have changed undocumented API that was used by bluepill).

Should be worarounded by bluepill 0.56 that restricts using of daemons gem.

Per the daemons gem author:

Date: 2012-02-17 12:31

Sender: Thomas Uehlinger

While the Daemonize module was never part of daemons' API (for

example no documentation refers to it), I agree that the change

of name was unnecessary. Therefore I had immediately reverted

that change and released 1.1.8. bluepill should therefore work

without problems with 1.1.8. After now also having yanked 1.1.7,

I don't see a reason to bump to 1.2 as there are now no breaking

gems in 1.1.*.

Via its tracker:

http://rubyforge.org/tracker/index.php?func=detail&aid=29516&group_id=524&atid=2084

I posted this to the bluepill issue as well.

--

Opscode, Inc

Joshua Timberman, Technical Program Manager

IRC, Skype, Twitter, Github: jtimberman