# Post installation issues

**URL:** <https://discourse.chef.io/t/post-installation-issues/1252>\
**Category:** Chef Infra (archive)\
**Created:** [August 6, 2009, 11:52am UTC](https://discourse.chef.io/t/post-installation-issues/1252 "2009-08-06T11:52:09Z")\
**Posts on this page:** 18\
**Page:** 1

<div class="post-metadata">

**Author:** ![Adrien](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/adrien/32/916_2.png) [@Adrien](https://discourse.chef.io/u/Adrien)\
**Post date:** [August 6, 2009, 11:52am UTC](https://discourse.chef.io/t/post-installation-issues/1252/1 "2009-08-06T11:52:09Z")

</div>

Hello,

I am encountering a few problems with my first installation of Chef. I have  
installed Chef on a fresh install of Ubuntu 9.04, which uses universe  
repositories (this is on a linode server, fyi).

After installation, I have run the following commands to get started with Chef:  
aptitude update && aptitude safe-upgrade  
aptitude install ubuntu-standard build-essential git-core  
aptitude install ruby rubygems vim-ruby libreadline-ruby ruby1.8-dev  
libopenssl-ruby1.8 rdoc ri irb wget ssl-cert vim

I have added /var/lib/gems/1.8/bin/ to my PATH.

Then I installed Chef:  
gem sources -a [http://gems.opscode.com](http://gems.opscode.com) && gem install ohai chef

I created ~/chef.json:  
{ “chef”: { “server\_fqdn”: “[mylinode.server.com](http://mylinode.server.com)”}, “recipes”: “chef::server” }

And ~/solo.rb:  
file\_cache\_path "/tmp/chef-solo"  
cookbook\_path “/tmp/chef-solo/cookbooks”

After that, I ran this as root:  
chef-solo -c ~/solo.rb -j ~/chef.json -r  
[http://s3.amazonaws.com/chef-solo/bootstrap-latest.tar.gz](http://s3.amazonaws.com/chef-solo/bootstrap-latest.tar.gz)

The installation went smoothly. The only things was that couchdb hanged after  
starting. (See  
[https://cloud-support.engineyard.com/discussions/problems/284-deploy-hangs-on-running-custom-recipes-if-they-exist](https://cloud-support.engineyard.com/discussions/problems/284-deploy-hangs-on-running-custom-recipes-if-they-exist))  
But, running “/etc/init.d/couchdb restart” in another terminal fixed that  
issue, and Chef-server installation continued.

After installing Chef-server, I edited /etc/chef/server.rb to update  
authorized\_openid\_providers and authorized\_openid\_identifiers. Then restarted  
apache.

At that point, I can reach [https://mylinode.server.com](https://mylinode.server.com), I can log in using  
openid, but when I am redirected back from my openid provider, I get a server  
500 error.

The logs (/var/log/chef/server.log) contain this:  
~ Started request handling: Thu Aug 06 11:47:37 +0000 2009  
~ Params: {“action”=\>“index”, “controller”=\>“chef\_server\_slice/nodes”}  
~ 404 “Object Not Found” - (Net::HTTPServerException)  
/usr/lib/ruby/1.8/net/http.rb:2097:in `error!' /var/lib/gems/1.8/gems/chef-0.7.4/lib/chef/rest.rb:232:in`run\_request’  
/var/lib/gems/1.8/gems/chef-0.7.4/lib/chef/rest.rb:85:in `get_rest' /var/lib/gems/1.8/gems/chef-0.7.4/lib/chef/couchdb.rb:124:in`list’  
/var/lib/gems/1.8/gems/chef-0.7.4/lib/chef/node.rb:351:in `list' /var/lib/gems/1.8/gems/chef-server-slice-0.7.4/app/controllers/nodes.rb:31:in`index’  
/var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/abstract\_controller.rb:315:in  
`send' /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/abstract_controller.rb:315:in`\_call\_action’  
/var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/abstract\_controller.rb:289:in  
`_dispatch' /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/merb_controller.rb:252:in`\_dispatch’  
/var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/dispatcher.rb:100:in  
`dispatch_action' /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/dispatcher.rb:100:in`synchronize’  
/var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/dispatcher.rb:100:in  
`dispatch_action' /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/dispatcher.rb:74:in`handle’  
/var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/dispatcher.rb:36:in  
`handle' /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/rack/application.rb:17:in`call’  
/var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion\_passenger/rack/request\_handler.rb:91:in  
`process_request' /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstract_request_handler.rb:206:in`main\_loop’  
/var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion\_passenger/rack/application\_spawner.rb:118:in  
`run' /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/application_spawner.rb:69:in`spawn\_application’  
/var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion\_passenger/utils.rb:182:in  
`safe_fork' /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/application_spawner.rb:62:in`spawn\_application’  
/var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion\_passenger/rack/application\_spawner.rb:45:in  
`spawn_application' /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/spawn_manager.rb:158:in`spawn\_application’  
/var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion\_passenger/spawn\_manager.rb:286:in  
`handle_spawn_application' /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstract_server.rb:351:in` **send** ’  
/var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion\_passenger/abstract\_server.rb:351:in  
`main_loop' /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstract_server.rb:195:in`start\_synchronously’  
/var/lib/gems/1.8/gems/passenger-2.2.4/bin/passenger-spawn-server:61  
~ Params: {“action”=\>“index”, “controller”=\>“chef\_server\_slice/nodes”}  
~

Did I miss something during the installation process? Any hint is welcome.  
Thank you very much in advance.

Adrien.

---

<div class="post-metadata">

**Author:** ![Joel\_Merrick](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/joel_merrick/32/893_2.png) [@Joel\_Merrick](https://discourse.chef.io/u/Joel_Merrick)\
**Post date:** [August 6, 2009, 12:01pm UTC](https://discourse.chef.io/t/post-installation-issues/1252/2 "2009-08-06T12:01:15Z")

</div>

Is [mylinode.server.com](http://mylinode.server.com) the correct FQDN?

I tried to trick chef into using /etc/hosts but it failed spectacularly

–  
$ echo “kpfmAdpoofdufevq/dp/vl” | perl -pe ‘s/(.)/chr(ord($1)-1)/ge’

---

<div class="post-metadata">

**Author:** ![Arjuna\_Christensen](https://avatars.discourse-cdn.com/v4/letter/a/5f9b8f/32.png) [@Arjuna\_Christensen](https://discourse.chef.io/u/Arjuna_Christensen)\
**Post date:** [August 6, 2009, 12:20pm UTC](https://discourse.chef.io/t/post-installation-issues/1252/3 "2009-08-06T12:20:58Z")

</div>

Hiya,

On 6/08/2009, at 11:52 PM, [adrien@gn2.fr](mailto:adrien@gn2.fr) wrote:

> Hello,
> 
> I am encountering a few problems with my first installation of Chef.  
> I have  
> installed Chef on a fresh install of Ubuntu 9.04, which uses universe  
> repositories (this is on a linode server, fyi).  
> [snip]
> 
> The logs (/var/log/chef/server.log) contain this:  
> ~ Started request handling: Thu Aug 06 11:47:37 +0000 2009  
> ~ Params: {"action"=\>"index", "controller"=\>"chef\_server\_slice/nodes"}  
> ~ 404 "Object Not Found" - (Net::HTTPServerException)  
> /usr/lib/ruby/1.8/net/http.rb:2097:in `error!' /var/lib/gems/1.8/gems/chef-0.7.4/lib/chef/rest.rb:232:in `run\_request'  
> /var/lib/gems/1.8/gems/chef-0.7.4/lib/chef/rest.rb:85:in `get_rest' /var/lib/gems/1.8/gems/chef-0.7.4/lib/chef/couchdb.rb:124:in `list'  
> /var/lib/gems/1.8/gems/chef-0.7.4/lib/chef/node.rb:351:in `list' /var/lib/gems/1.8/gems/chef-server-slice-0.7.4/app/controllers/ nodes.rb:31:in `index'  
> /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/  
> abstract\_controller.rb:315:in  
> `send' /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/ abstract_controller.rb:315:in `\_call\_action'  
> /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/  
> abstract\_controller.rb:289:in  
> `_dispatch' /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/ merb_controller.rb:252:in `\_dispatch'  
> /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/  
> dispatcher.rb:100:in  
> `dispatch_action' /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/ dispatcher.rb:100:in `synchronize'  
> /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/  
> dispatcher.rb:100:in  
> `dispatch_action' /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/ dispatcher.rb:74:in `handle'  
> /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/  
> dispatcher.rb:36:in  
> `handle' /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/rack/ application.rb:17:in `call'  
> /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion\_passenger/rack/  
> request\_handler.rb:91:in  
> `process_request' /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/ abstract_request_handler.rb:206:in `main\_loop'  
> /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion\_passenger/rack/  
> application\_spawner.rb:118:in  
> `run' /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/ application_spawner.rb:69:in `spawn\_application'  
> /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion\_passenger/  
> utils.rb:182:in  
> `safe_fork' /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/ application_spawner.rb:62:in `spawn\_application'  
> /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion\_passenger/rack/  
> application\_spawner.rb:45:in  
> `spawn_application' /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/ spawn_manager.rb:158:in `spawn\_application'  
> /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion\_passenger/  
> spawn\_manager.rb:286:in  
> `handle_spawn_application' /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/ abstract_server.rb:351:in ` **send**'  
> /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion\_passenger/  
> abstract\_server.rb:351:in  
> `main_loop' /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/ abstract_server.rb:195:in `start\_synchronously'  
> /var/lib/gems/1.8/gems/passenger-2.2.4/bin/passenger-spawn-server:61  
> ~ Params: {"action"=\>"index", "controller"=\>"chef\_server\_slice/nodes"}  
> ~

That's a 404, and a normal part of the node registration process -  
would you be able to show the correct 500 error? Also please crank up  
the debug logging (-l debug / log\_level :debug)

> Did I miss something during the installation process? Any hint is  
> welcome.  
> Thank you very much in advance.
> 
> Adrien.

--  
AJ Christensen, Software Engineer  
Opscode, Inc.  
E: [aj@opscode.com](mailto:aj@opscode.com)

---

<div class="post-metadata">

**Author:** ![Adrien](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/adrien/32/916_2.png) [@Adrien](https://discourse.chef.io/u/Adrien)\
**Post date:** [August 6, 2009, 12:54pm UTC](https://discourse.chef.io/t/post-installation-issues/1252/4 "2009-08-06T12:54:50Z")

</div>

Thank you for your answer.

I believe the FQDN is set properly, as "hostname -f" returns the same  
hostname specified in my Chef configuration.

On 6 Aug 2009, at 13:01, Joel Merrick wrote:

> Is [mylinode.server.com](http://mylinode.server.com) the correct FQDN?
> 
> I tried to trick chef into using /etc/hosts but it failed  
> spectacularly
> 
> --  
> $ echo "kpfmAdpoofdufevq/dp/vl" | perl -pe 's/(.)/chr(ord($1)-1)/ge'

---

<div class="post-metadata">

**Author:** ![Adrien](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/adrien/32/916_2.png) [@Adrien](https://discourse.chef.io/u/Adrien)\
**Post date:** [August 6, 2009, 1:01pm UTC](https://discourse.chef.io/t/post-installation-issues/1252/5 "2009-08-06T13:01:59Z")

</div>

Hello,

I have only pasted the 404 error, because there is not 500 error in  
the log. Setting log\_level to :debug in /etc/chef/server.rb does not  
seem to produce more verbose logs. Should set that somewhere else? (I  
have rebooted the whole server to make sure everything was restarted).  
I am sorry not to be familiar with chef-server internal...

However, I have noticed this in the logs, when the chef-server starts:  
~ Failed loading ChefServerSlice (Connection refused - Connection  
refused connecting to stomp queue at localhost:61613, giving up)  
~ Parent pid: 18068  
~ Compiling routes...  
~ Could not find resource model Node  
~ Could not find resource model Role  
~ Could not find resource model Search  
~ Could not find resource model Cookbook  
~ Could not find resource model Registration  
~ Could not find resource model Registration  
~ Could not find resource model Registration  
~ Activating slice 'ChefServerSlice' ...

Cheers,

Adrien

On 6 Aug 2009, at 13:20, Arjuna Christensen wrote:

> Hiya,
> 
> On 6/08/2009, at 11:52 PM, [adrien@gn2.fr](mailto:adrien@gn2.fr) wrote:
> 
> > Hello,
> > 
> > I am encountering a few problems with my first installation of  
> > Chef. I have  
> > installed Chef on a fresh install of Ubuntu 9.04, which uses universe  
> > repositories (this is on a linode server, fyi).  
> > [snip]
> > 
> > The logs (/var/log/chef/server.log) contain this:  
> > ~ Started request handling: Thu Aug 06 11:47:37 +0000 2009  
> > ~ Params: {"action"=\>"index", "controller"=\>"chef\_server\_slice/  
> > nodes"}  
> > ~ 404 "Object Not Found" - (Net::HTTPServerException)  
> > /usr/lib/ruby/1.8/net/http.rb:2097:in `error!' /var/lib/gems/1.8/gems/chef-0.7.4/lib/chef/rest.rb:232:in `run\_request'  
> > /var/lib/gems/1.8/gems/chef-0.7.4/lib/chef/rest.rb:85:in `get_rest' /var/lib/gems/1.8/gems/chef-0.7.4/lib/chef/couchdb.rb:124:in `list'  
> > /var/lib/gems/1.8/gems/chef-0.7.4/lib/chef/node.rb:351:in `list' /var/lib/gems/1.8/gems/chef-server-slice-0.7.4/app/controllers/ nodes.rb:31:in `index'  
> > /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/  
> > abstract\_controller.rb:315:in  
> > `send' /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/ abstract_controller.rb:315:in `\_call\_action'  
> > /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/  
> > abstract\_controller.rb:289:in  
> > `_dispatch' /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/ merb_controller.rb:252:in `\_dispatch'  
> > /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/  
> > dispatcher.rb:100:in  
> > `dispatch_action' /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/ dispatcher.rb:100:in `synchronize'  
> > /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/  
> > dispatcher.rb:100:in  
> > `dispatch_action' /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/ dispatcher.rb:74:in `handle'  
> > /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/  
> > dispatcher.rb:36:in  
> > `handle' /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/rack/ application.rb:17:in `call'  
> > /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion\_passenger/rack/  
> > request\_handler.rb:91:in  
> > `process_request' /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/ abstract_request_handler.rb:206:in `main\_loop'  
> > /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion\_passenger/rack/  
> > application\_spawner.rb:118:in  
> > `run' /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/ application_spawner.rb:69:in `spawn\_application'  
> > /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion\_passenger/  
> > utils.rb:182:in  
> > `safe_fork' /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/ application_spawner.rb:62:in `spawn\_application'  
> > /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion\_passenger/rack/  
> > application\_spawner.rb:45:in  
> > `spawn_application' /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/ spawn_manager.rb:158:in `spawn\_application'  
> > /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion\_passenger/  
> > spawn\_manager.rb:286:in  
> > `handle_spawn_application' /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/ abstract_server.rb:351:in ` **send**'  
> > /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion\_passenger/  
> > abstract\_server.rb:351:in  
> > `main_loop' /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/ abstract_server.rb:195:in `start\_synchronously'  
> > /var/lib/gems/1.8/gems/passenger-2.2.4/bin/passenger-spawn-server:61  
> > ~ Params: {"action"=\>"index", "controller"=\>"chef\_server\_slice/  
> > nodes"}  
> > ~
> 
> That's a 404, and a normal part of the node registration process -  
> would you be able to show the correct 500 error? Also please crank  
> up the debug logging (-l debug / log\_level :debug)
> 
> > Did I miss something during the installation process? Any hint is  
> > welcome.  
> > Thank you very much in advance.
> > 
> > Adrien.
> 
> --  
> AJ Christensen, Software Engineer  
> Opscode, Inc.  
> E: [aj@opscode.com](mailto:aj@opscode.com)

---

<div class="post-metadata">

**Author:** ![Arjuna\_Christensen](https://avatars.discourse-cdn.com/v4/letter/a/5f9b8f/32.png) [@Arjuna\_Christensen](https://discourse.chef.io/u/Arjuna_Christensen)\
**Post date:** [August 6, 2009, 1:23pm UTC](https://discourse.chef.io/t/post-installation-issues/1252/6 "2009-08-06T13:23:04Z")

</div>

On 7/08/2009, at 1:01 AM, Adrien wrote:

> Hello,
> 
> I have only pasted the 404 error, because there is not 500 error in  
> the log. Setting log\_level to :debug in /etc/chef/server.rb does not  
> seem to produce more verbose logs. Should set that somewhere else?  
> (I have rebooted the whole server to make sure everything was  
> restarted). I am sorry not to be familiar with chef-server internal...
> 
> However, I have noticed this in the logs, when the chef-server starts:  
> ~ Failed loading ChefServerSlice (Connection refused - Connection  
> refused connecting to stomp queue at localhost:61613, giving up)

This error is indicating that your stompserver queue is down, you'll  
need to make sure it is running (as well as the chef-indexer) before  
running the server.

> ~ Parent pid: 18068  
> ~ Compiling routes...  
> ~ Could not find resource model Node  
> ~ Could not find resource model Role  
> ~ Could not find resource model Search  
> ~ Could not find resource model Cookbook  
> ~ Could not find resource model Registration  
> ~ Could not find resource model Registration  
> ~ Could not find resource model Registration  
> ~ Activating slice 'ChefServerSlice' ...
> 
> Cheers,
> 
> Adrien
> 
> On 6 Aug 2009, at 13:20, Arjuna Christensen wrote:
> 
> > Hiya,
> > 
> > On 6/08/2009, at 11:52 PM, [adrien@gn2.fr](mailto:adrien@gn2.fr) wrote:
> > 
> > > Hello,
> > > 
> > > I am encountering a few problems with my first installation of  
> > > Chef. I have  
> > > installed Chef on a fresh install of Ubuntu 9.04, which uses  
> > > universe  
> > > repositories (this is on a linode server, fyi).  
> > > [snip]
> > > 
> > > The logs (/var/log/chef/server.log) contain this:  
> > > ~ Started request handling: Thu Aug 06 11:47:37 +0000 2009  
> > > ~ Params: {"action"=\>"index", "controller"=\>"chef\_server\_slice/  
> > > nodes"}  
> > > ~ 404 "Object Not Found" - (Net::HTTPServerException)  
> > > /usr/lib/ruby/1.8/net/http.rb:2097:in `error!' /var/lib/gems/1.8/gems/chef-0.7.4/lib/chef/rest.rb:232:in `run\_request'  
> > > /var/lib/gems/1.8/gems/chef-0.7.4/lib/chef/rest.rb:85:in `get_rest' /var/lib/gems/1.8/gems/chef-0.7.4/lib/chef/couchdb.rb:124:in `list'  
> > > /var/lib/gems/1.8/gems/chef-0.7.4/lib/chef/node.rb:351:in `list' /var/lib/gems/1.8/gems/chef-server-slice-0.7.4/app/controllers/ nodes.rb:31:in `index'  
> > > /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/  
> > > abstract\_controller.rb:315:in  
> > > `send' /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/ abstract_controller.rb:315:in `\_call\_action'  
> > > /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/  
> > > abstract\_controller.rb:289:in  
> > > `_dispatch' /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/ merb_controller.rb:252:in `\_dispatch'  
> > > /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/  
> > > dispatcher.rb:100:in  
> > > `dispatch_action' /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/ dispatcher.rb:100:in `synchronize'  
> > > /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/  
> > > dispatcher.rb:100:in  
> > > `dispatch_action' /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/ dispatcher.rb:74:in `handle'  
> > > /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/  
> > > dispatcher.rb:36:in  
> > > `handle' /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/rack/ application.rb:17:in `call'  
> > > /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion\_passenger/rack/  
> > > request\_handler.rb:91:in  
> > > `process_request' /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/ abstract_request_handler.rb:206:in `main\_loop'  
> > > /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion\_passenger/rack/  
> > > application\_spawner.rb:118:in  
> > > `run' /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/ application_spawner.rb:69:in `spawn\_application'  
> > > /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion\_passenger/  
> > > utils.rb:182:in  
> > > `safe_fork' /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/ application_spawner.rb:62:in `spawn\_application'  
> > > /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion\_passenger/rack/  
> > > application\_spawner.rb:45:in  
> > > `spawn_application' /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/ spawn_manager.rb:158:in `spawn\_application'  
> > > /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion\_passenger/  
> > > spawn\_manager.rb:286:in  
> > > `handle_spawn_application' /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/ abstract_server.rb:351:in ` **send**'  
> > > /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion\_passenger/  
> > > abstract\_server.rb:351:in  
> > > `main_loop' /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/ abstract_server.rb:195:in `start\_synchronously'  
> > > /var/lib/gems/1.8/gems/passenger-2.2.4/bin/passenger-spawn-server:61  
> > > ~ Params: {"action"=\>"index", "controller"=\>"chef\_server\_slice/  
> > > nodes"}  
> > > ~
> > 
> > That's a 404, and a normal part of the node registration process -  
> > would you be able to show the correct 500 error? Also please crank  
> > up the debug logging (-l debug / log\_level :debug)
> > 
> > > Did I miss something during the installation process? Any hint is  
> > > welcome.  
> > > Thank you very much in advance.
> > > 
> > > Adrien.
> > 
> > --  
> > AJ Christensen, Software Engineer  
> > Opscode, Inc.  
> > E: [aj@opscode.com](mailto:aj@opscode.com)

--  
AJ Christensen, Software Engineer  
Opscode, Inc.  
E: [aj@opscode.com](mailto:aj@opscode.com)

---

<div class="post-metadata">

**Author:** ![Adrien](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/adrien/32/916_2.png) [@Adrien](https://discourse.chef.io/u/Adrien)\
**Post date:** [August 6, 2009, 2:19pm UTC](https://discourse.chef.io/t/post-installation-issues/1252/7 "2009-08-06T14:19:27Z")

</div>

Thanks for pointing that out.

It seems that I have a problem with runit not being able to start  
services properly.

# ps aux | grep runsv

root 11683 0.0 0.0 120 28 ? Ss 12:44 0:00  
runsvdir -P /etc/service log: ............  
root 12132 0.0 0.0 108 32 ? Ss 12:45 0:00 runsv  
stompserver  
root 15118 0.0 0.0 108 32 ? Ss 12:46 0:00 runsv  
chef-client  
root 15489 0.0 0.0 108 32 ? Ss 12:47 0:00 runsv  
chef-indexer

# sv restart stompserver

timeout: down: stompserver: 0s, normally up, want up

When I start stompserver and chef-indexer manually, chef-server works  
fine.

On 6 Aug 2009, at 14:23, Arjuna Christensen wrote:

> On 7/08/2009, at 1:01 AM, Adrien wrote:
> 
> > Hello,
> > 
> > I have only pasted the 404 error, because there is not 500 error in  
> > the log. Setting log\_level to :debug in /etc/chef/server.rb does  
> > not seem to produce more verbose logs. Should set that somewhere  
> > else? (I have rebooted the whole server to make sure everything was  
> > restarted). I am sorry not to be familiar with chef-server  
> > internal...
> > 
> > However, I have noticed this in the logs, when the chef-server  
> > starts:  
> > ~ Failed loading ChefServerSlice (Connection refused - Connection  
> > refused connecting to stomp queue at localhost:61613, giving up)
> 
> This error is indicating that your stompserver queue is down, you'll  
> need to make sure it is running (as well as the chef-indexer) before  
> running the server.
> 
> > ~ Parent pid: 18068  
> > ~ Compiling routes...  
> > ~ Could not find resource model Node  
> > ~ Could not find resource model Role  
> > ~ Could not find resource model Search  
> > ~ Could not find resource model Cookbook  
> > ~ Could not find resource model Registration  
> > ~ Could not find resource model Registration  
> > ~ Could not find resource model Registration  
> > ~ Activating slice 'ChefServerSlice' ...
> > 
> > Cheers,
> > 
> > Adrien
> > 
> > On 6 Aug 2009, at 13:20, Arjuna Christensen wrote:
> > 
> > > Hiya,
> > > 
> > > On 6/08/2009, at 11:52 PM, [adrien@gn2.fr](mailto:adrien@gn2.fr) wrote:
> > > 
> > > > Hello,
> > > > 
> > > > I am encountering a few problems with my first installation of  
> > > > Chef. I have  
> > > > installed Chef on a fresh install of Ubuntu 9.04, which uses  
> > > > universe  
> > > > repositories (this is on a linode server, fyi).  
> > > > [snip]
> > > > 
> > > > The logs (/var/log/chef/server.log) contain this:  
> > > > ~ Started request handling: Thu Aug 06 11:47:37 +0000 2009  
> > > > ~ Params: {"action"=\>"index", "controller"=\>"chef\_server\_slice/  
> > > > nodes"}  
> > > > ~ 404 "Object Not Found" - (Net::HTTPServerException)  
> > > > /usr/lib/ruby/1.8/net/http.rb:2097:in `error!' /var/lib/gems/1.8/gems/chef-0.7.4/lib/chef/rest.rb:232:in `run\_request'  
> > > > /var/lib/gems/1.8/gems/chef-0.7.4/lib/chef/rest.rb:85:in `get_rest' /var/lib/gems/1.8/gems/chef-0.7.4/lib/chef/couchdb.rb:124:in `list'  
> > > > /var/lib/gems/1.8/gems/chef-0.7.4/lib/chef/node.rb:351:in `list' /var/lib/gems/1.8/gems/chef-server-slice-0.7.4/app/controllers/ nodes.rb:31:in `index'  
> > > > /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/  
> > > > abstract\_controller.rb:315:in  
> > > > `send' /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/ abstract_controller.rb:315:in `\_call\_action'  
> > > > /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/  
> > > > abstract\_controller.rb:289:in  
> > > > `_dispatch' /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/ merb_controller.rb:252:in `\_dispatch'  
> > > > /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/  
> > > > dispatcher.rb:100:in  
> > > > `dispatch_action' /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/ dispatcher.rb:100:in `synchronize'  
> > > > /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/  
> > > > dispatcher.rb:100:in  
> > > > `dispatch_action' /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/ dispatcher.rb:74:in `handle'  
> > > > /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/  
> > > > dispatcher.rb:36:in  
> > > > `handle' /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/rack/ application.rb:17:in `call'  
> > > > /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion\_passenger/rack/  
> > > > request\_handler.rb:91:in  
> > > > `process_request' /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/ abstract_request_handler.rb:206:in `main\_loop'  
> > > > /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion\_passenger/rack/  
> > > > application\_spawner.rb:118:in  
> > > > `run' /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/ application_spawner.rb:69:in `spawn\_application'  
> > > > /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion\_passenger/  
> > > > utils.rb:182:in  
> > > > `safe_fork' /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/ application_spawner.rb:62:in `spawn\_application'  
> > > > /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion\_passenger/rack/  
> > > > application\_spawner.rb:45:in  
> > > > `spawn_application' /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/ spawn_manager.rb:158:in `spawn\_application'  
> > > > /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion\_passenger/  
> > > > spawn\_manager.rb:286:in  
> > > > `handle_spawn_application' /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/ abstract_server.rb:351:in ` **send**'  
> > > > /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion\_passenger/  
> > > > abstract\_server.rb:351:in  
> > > > `main_loop' /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/ abstract_server.rb:195:in `start\_synchronously'  
> > > > /var/lib/gems/1.8/gems/passenger-2.2.4/bin/passenger-spawn-server:  
> > > > 61  
> > > > ~ Params: {"action"=\>"index", "controller"=\>"chef\_server\_slice/  
> > > > nodes"}  
> > > > ~
> > > 
> > > That's a 404, and a normal part of the node registration process -  
> > > would you be able to show the correct 500 error? Also please crank  
> > > up the debug logging (-l debug / log\_level :debug)
> > > 
> > > > Did I miss something during the installation process? Any hint is  
> > > > welcome.  
> > > > Thank you very much in advance.
> > > > 
> > > > Adrien.
> > > 
> > > --  
> > > AJ Christensen, Software Engineer  
> > > Opscode, Inc.  
> > > E: [aj@opscode.com](mailto:aj@opscode.com)
> 
> --  
> AJ Christensen, Software Engineer  
> Opscode, Inc.  
> E: [aj@opscode.com](mailto:aj@opscode.com)

---

<div class="post-metadata">

**Author:** ![Adrien](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/adrien/32/916_2.png) [@Adrien](https://discourse.chef.io/u/Adrien)\
**Post date:** [August 6, 2009, 3:53pm UTC](https://discourse.chef.io/t/post-installation-issues/1252/8 "2009-08-06T15:53:04Z")

</div>

Ok, I have found the cause of this problem.

I installed rubygems using apt, therefore the path to gem binaries  
was /var/lib/gems/1.8/bin/. Although I added this to the PATH variable  
in /etc/profile, runit does not know about it (as /etc/profile is for  
login shells). Thus, stompserver, chef-index, etc could not be started  
by runit and Chef-server sent this error.

I have found two solutions:

- Add something like PATH=$PATH:/var/lib/gems/1.8/bin/ in each run  
file if runit services. (/etc/sv/\<service\_name\>/run)
- Install rubygems from source, which by default puts binaries in /  
usr/bin

Hope it helps someone else.

Thank you Arjuna and Joel for your help,

Adrien.

On 6 Aug 2009, at 14:23, Arjuna Christensen wrote:

> On 7/08/2009, at 1:01 AM, Adrien wrote:
> 
> > Hello,
> > 
> > I have only pasted the 404 error, because there is not 500 error in  
> > the log. Setting log\_level to :debug in /etc/chef/server.rb does  
> > not seem to produce more verbose logs. Should set that somewhere  
> > else? (I have rebooted the whole server to make sure everything was  
> > restarted). I am sorry not to be familiar with chef-server  
> > internal...
> > 
> > However, I have noticed this in the logs, when the chef-server  
> > starts:  
> > ~ Failed loading ChefServerSlice (Connection refused - Connection  
> > refused connecting to stomp queue at localhost:61613, giving up)
> 
> This error is indicating that your stompserver queue is down, you'll  
> need to make sure it is running (as well as the chef-indexer) before  
> running the server.
> 
> > ~ Parent pid: 18068  
> > ~ Compiling routes...  
> > ~ Could not find resource model Node  
> > ~ Could not find resource model Role  
> > ~ Could not find resource model Search  
> > ~ Could not find resource model Cookbook  
> > ~ Could not find resource model Registration  
> > ~ Could not find resource model Registration  
> > ~ Could not find resource model Registration  
> > ~ Activating slice 'ChefServerSlice' ...
> > 
> > Cheers,
> > 
> > Adrien
> > 
> > On 6 Aug 2009, at 13:20, Arjuna Christensen wrote:
> > 
> > > Hiya,
> > > 
> > > On 6/08/2009, at 11:52 PM, [adrien@gn2.fr](mailto:adrien@gn2.fr) wrote:
> > > 
> > > > Hello,
> > > > 
> > > > I am encountering a few problems with my first installation of  
> > > > Chef. I have  
> > > > installed Chef on a fresh install of Ubuntu 9.04, which uses  
> > > > universe  
> > > > repositories (this is on a linode server, fyi).  
> > > > [snip]
> > > > 
> > > > The logs (/var/log/chef/server.log) contain this:  
> > > > ~ Started request handling: Thu Aug 06 11:47:37 +0000 2009  
> > > > ~ Params: {"action"=\>"index", "controller"=\>"chef\_server\_slice/  
> > > > nodes"}  
> > > > ~ 404 "Object Not Found" - (Net::HTTPServerException)  
> > > > /usr/lib/ruby/1.8/net/http.rb:2097:in `error!' /var/lib/gems/1.8/gems/chef-0.7.4/lib/chef/rest.rb:232:in `run\_request'  
> > > > /var/lib/gems/1.8/gems/chef-0.7.4/lib/chef/rest.rb:85:in `get_rest' /var/lib/gems/1.8/gems/chef-0.7.4/lib/chef/couchdb.rb:124:in `list'  
> > > > /var/lib/gems/1.8/gems/chef-0.7.4/lib/chef/node.rb:351:in `list' /var/lib/gems/1.8/gems/chef-server-slice-0.7.4/app/controllers/ nodes.rb:31:in `index'  
> > > > /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/  
> > > > abstract\_controller.rb:315:in  
> > > > `send' /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/ abstract_controller.rb:315:in `\_call\_action'  
> > > > /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/  
> > > > abstract\_controller.rb:289:in  
> > > > `_dispatch' /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/ merb_controller.rb:252:in `\_dispatch'  
> > > > /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/  
> > > > dispatcher.rb:100:in  
> > > > `dispatch_action' /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/ dispatcher.rb:100:in `synchronize'  
> > > > /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/  
> > > > dispatcher.rb:100:in  
> > > > `dispatch_action' /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/ dispatcher.rb:74:in `handle'  
> > > > /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/  
> > > > dispatcher.rb:36:in  
> > > > `handle' /var/lib/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/rack/ application.rb:17:in `call'  
> > > > /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion\_passenger/rack/  
> > > > request\_handler.rb:91:in  
> > > > `process_request' /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/ abstract_request_handler.rb:206:in `main\_loop'  
> > > > /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion\_passenger/rack/  
> > > > application\_spawner.rb:118:in  
> > > > `run' /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/ application_spawner.rb:69:in `spawn\_application'  
> > > > /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion\_passenger/  
> > > > utils.rb:182:in  
> > > > `safe_fork' /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/ application_spawner.rb:62:in `spawn\_application'  
> > > > /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion\_passenger/rack/  
> > > > application\_spawner.rb:45:in  
> > > > `spawn_application' /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/ spawn_manager.rb:158:in `spawn\_application'  
> > > > /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion\_passenger/  
> > > > spawn\_manager.rb:286:in  
> > > > `handle_spawn_application' /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/ abstract_server.rb:351:in ` **send**'  
> > > > /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion\_passenger/  
> > > > abstract\_server.rb:351:in  
> > > > `main_loop' /var/lib/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/ abstract_server.rb:195:in `start\_synchronously'  
> > > > /var/lib/gems/1.8/gems/passenger-2.2.4/bin/passenger-spawn-server:  
> > > > 61  
> > > > ~ Params: {"action"=\>"index", "controller"=\>"chef\_server\_slice/  
> > > > nodes"}  
> > > > ~
> > > 
> > > That's a 404, and a normal part of the node registration process -  
> > > would you be able to show the correct 500 error? Also please crank  
> > > up the debug logging (-l debug / log\_level :debug)
> > > 
> > > > Did I miss something during the installation process? Any hint is  
> > > > welcome.  
> > > > Thank you very much in advance.
> > > > 
> > > > Adrien.
> > > 
> > > --  
> > > AJ Christensen, Software Engineer  
> > > Opscode, Inc.  
> > > E: [aj@opscode.com](mailto:aj@opscode.com)
> 
> --  
> AJ Christensen, Software Engineer  
> Opscode, Inc.  
> E: [aj@opscode.com](mailto:aj@opscode.com)

---

<div class="post-metadata">

**Author:** ![Joel\_Merrick](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/joel_merrick/32/893_2.png) [@Joel\_Merrick](https://discourse.chef.io/u/Joel_Merrick)\
**Post date:** [August 6, 2009, 3:59pm UTC](https://discourse.chef.io/t/post-installation-issues/1252/9 "2009-08-06T15:59:14Z")

</div>

On Thu, Aug 6, 2009 at 4:53 PM, Adrien[adrien@gn2.fr](mailto:adrien@gn2.fr) wrote:

> - Install rubygems from source, which by default puts binaries in /usr/bin

100% - I'd stick well clear of using dpkg gems. They range from broken  
to erm, broken. 🙂

Joel

--  
$ echo "kpfmAdpoofdufevq/dp/vl" | perl -pe 's/(.)/chr(ord($1)-1)/ge'

---

<div class="post-metadata">

**Author:** ![Adam\_Jacob](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/adam_jacob/32/292_2.png) [@Adam\_Jacob](https://discourse.chef.io/u/Adam_Jacob)\
**Post date:** [August 6, 2009, 6:16pm UTC](https://discourse.chef.io/t/post-installation-issues/1252/10 "2009-08-06T18:16:45Z")

</div>

On Thu, Aug 6, 2009 at 8:53 AM, Adrien[adrien@gn2.fr](mailto:adrien@gn2.fr) wrote:

> Ok, I have found the cause of this problem.  
> I installed rubygems using apt, therefore the path to gem binaries  
> I have found two solutions:
> 
> - Add something like PATH=$PATH:/var/lib/gems/1.8/bin/ in each run file if  
> runit services. (/etc/sv/\<service\_name\>/run)
> - Install rubygems from source, which by default puts binaries in /usr/bin  
> Hope it helps someone else.  
> Thank you Arjuna and Joel for your help,  
> Adrien.

Due to the tireless work of Joshua Timberman, AJ, Bryan McLellan and  
Thom May, we should have a repository with proper debian packages for  
Chef soon, which will make this much easier. 🙂

Yay!

Adam

--  
Opscode, Inc.  
Adam Jacob, CTO  
T: (206) 508-7449 E: [adam@opscode.com](mailto:adam@opscode.com)

---

<div class="post-metadata">

**Author:** ![Graeme\_Mathieson](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/graeme_mathieson/32/914_2.png) [@Graeme\_Mathieson](https://discourse.chef.io/u/Graeme_Mathieson)\
**Post date:** [August 7, 2009, 8:59am UTC](https://discourse.chef.io/t/post-installation-issues/1252/11 "2009-08-07T08:59:39Z")

</div>

Hi,

On 6 Aug 2009, at 20:16, Adam Jacob wrote:

> Due to the tireless work of Joshua Timberman, AJ, Bryan McLellan and  
> Thom May, we should have a repository with proper debian packages for  
> Chef soon, which will make this much easier. 🙂

That's awesome. 🙂 I don't suppose this will include a "proper"  
Debian package of Ruby Enterprise Edition for, say, Ubuntu 9.04? I'm  
currently trying to coerce some local Debian developers into doing one  
for me, but I don't want to duplicate effort. 🙂

(When I say "proper", I mean one that completely "Provides" and  
"Replaces" the stock Ruby so it coexists with the rest of the Debian  
system, and provides a /etc/alternatives mechanism for choosing which  
Ruby to use. Not sticking it in /opt/local.)

G

---

<div class="post-metadata">

**Author:** ![Joshua\_Timberman](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/joshua_timberman/32/424_2.png) [@Joshua\_Timberman](https://discourse.chef.io/u/Joshua_Timberman)\
**Post date:** [August 7, 2009, 6:22pm UTC](https://discourse.chef.io/t/post-installation-issues/1252/12 "2009-08-07T18:22:59Z")

</div>

-----BEGIN PGP SIGNED MESSAGE-----  
Hash: SHA1

On Aug 7, 2009, at 2:59 AM, Graeme Mathieson wrote:

> That's awesome. 🙂 I don't suppose this will include a "proper"  
> Debian package of Ruby Enterprise Edition for, say, Ubuntu 9.04? I'm  
> currently trying to coerce some local Debian developers into doing  
> one for me, but I don't want to duplicate effort. 🙂

No, we're not attempting to package REE for Debian, just Chef and  
Chef's requirements. The best source of information on that would be  
the debian-ruby mailing list and #debian-ruby IRC channel (on  
[irc.oftc.net](http://irc.oftc.net)).

* * *

Opscode, Inc  
Joshua Timberman, Senior Solutions Engineer  
C: 720.878.4322 E: [joshua@opscode.com](mailto:joshua@opscode.com)

-----BEGIN PGP SIGNATURE-----  
Version: GnuPG v1.4.9 (Darwin)

iEYEARECAAYFAkp8cQMACgkQO97WSdVpzT3JfACfQSBhA/OVU8D1k0h+OKuOCTLt  
BDgAnjimvvqjeAL6dD5GTGU3el1JOzfk  
=LuEd  
-----END PGP SIGNATURE-----

---

<div class="post-metadata">

**Author:** ![Joe\_Van\_Dyk](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/joe_van_dyk/32/853_2.png) [@Joe\_Van\_Dyk](https://discourse.chef.io/u/Joe_Van_Dyk)\
**Post date:** [August 7, 2009, 7:08pm UTC](https://discourse.chef.io/t/post-installation-issues/1252/13 "2009-08-07T19:08:34Z")

</div>

On Fri, Aug 7, 2009 at 11:22 AM, Joshua Timberman[joshua@opscode.com](mailto:joshua@opscode.com) wrote:

> -----BEGIN PGP SIGNED MESSAGE-----  
> Hash: SHA1
> 
> On Aug 7, 2009, at 2:59 AM, Graeme Mathieson wrote:
> 
> > That's awesome. 🙂 I don't suppose this will include a "proper" Debian  
> > package of Ruby Enterprise Edition for, say, Ubuntu 9.04? I'm currently  
> > trying to coerce some local Debian developers into doing one for me, but I  
> > don't want to duplicate effort. 🙂
> 
> No, we're not attempting to package REE for Debian, just Chef and Chef's  
> requirements. The best source of information on that would be the  
> debian-ruby mailing list and #debian-ruby IRC channel (on [irc.oftc.net](http://irc.oftc.net)).

It would be awesome if all the chef requirements could be packaged up  
in the chef package (maybe call it chef-deps). Not sure how much  
extra work that would be though.

--  
Joe Van Dyk  
[http://fixieconsulting.com](http://fixieconsulting.com)

---

<div class="post-metadata">

**Author:** ![Bryan\_McLellan](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/bryan_mclellan/32/81_2.png) [@Bryan\_McLellan](https://discourse.chef.io/u/Bryan_McLellan)\
**Post date:** [August 7, 2009, 7:54pm UTC](https://discourse.chef.io/t/post-installation-issues/1252/14 "2009-08-07T19:54:07Z")

</div>

What deps? The gem dependencies? Those have all been individually  
packaged as debian packages so that other packages may use them as  
well. Installing the chef package will install the dependencies as  
debs instead of gems.

On 8/7/09, Joe Van Dyk [joe@fixieconsulting.com](mailto:joe@fixieconsulting.com) wrote:

> On Fri, Aug 7, 2009 at 11:22 AM, Joshua Timberman[joshua@opscode.com](mailto:joshua@opscode.com) wrote:
> 
> > -----BEGIN PGP SIGNED MESSAGE-----  
> > Hash: SHA1
> > 
> > On Aug 7, 2009, at 2:59 AM, Graeme Mathieson wrote:
> > 
> > > That's awesome. 🙂 I don't suppose this will include a "proper" Debian  
> > > package of Ruby Enterprise Edition for, say, Ubuntu 9.04? I'm currently  
> > > trying to coerce some local Debian developers into doing one for me, but  
> > > I  
> > > don't want to duplicate effort. 🙂
> > 
> > No, we're not attempting to package REE for Debian, just Chef and Chef's  
> > requirements. The best source of information on that would be the  
> > debian-ruby mailing list and #debian-ruby IRC channel (on [irc.oftc.net](http://irc.oftc.net)).
> 
> It would be awesome if all the chef requirements could be packaged up  
> in the chef package (maybe call it chef-deps). Not sure how much  
> extra work that would be though.
> 
> --  
> Joe Van Dyk  
> [http://fixieconsulting.com](http://fixieconsulting.com)

--  
Sent from my mobile device

---

<div class="post-metadata">

**Author:** ![Joe\_Van\_Dyk](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/joe_van_dyk/32/853_2.png) [@Joe\_Van\_Dyk](https://discourse.chef.io/u/Joe_Van_Dyk)\
**Post date:** [August 7, 2009, 8:11pm UTC](https://discourse.chef.io/t/post-installation-issues/1252/15 "2009-08-07T20:11:23Z")

</div>

ruby, couchdb, ohai, json, etc.

Joe

On Fri, Aug 7, 2009 at 12:54 PM, Bryan McLellan[btm@loftninjas.org](mailto:btm@loftninjas.org) wrote:

> What deps? The gem dependencies? Those have all been individually  
> packaged as debian packages so that other packages may use them as  
> well. Installing the chef package will install the dependencies as  
> debs instead of gems.
> 
> On 8/7/09, Joe Van Dyk [joe@fixieconsulting.com](mailto:joe@fixieconsulting.com) wrote:
> 
> > On Fri, Aug 7, 2009 at 11:22 AM, Joshua Timberman[joshua@opscode.com](mailto:joshua@opscode.com) wrote:
> > 
> > > -----BEGIN PGP SIGNED MESSAGE-----  
> > > Hash: SHA1
> > > 
> > > On Aug 7, 2009, at 2:59 AM, Graeme Mathieson wrote:
> > > 
> > > > That's awesome. 🙂 I don't suppose this will include a "proper" Debian  
> > > > package of Ruby Enterprise Edition for, say, Ubuntu 9.04? I'm currently  
> > > > trying to coerce some local Debian developers into doing one for me, but  
> > > > I  
> > > > don't want to duplicate effort. 🙂
> > > 
> > > No, we're not attempting to package REE for Debian, just Chef and Chef's  
> > > requirements. The best source of information on that would be the  
> > > debian-ruby mailing list and #debian-ruby IRC channel (on [irc.oftc.net](http://irc.oftc.net)).
> > 
> > It would be awesome if all the chef requirements could be packaged up  
> > in the chef package (maybe call it chef-deps). Not sure how much  
> > extra work that would be though.
> > 
> > --  
> > Joe Van Dyk  
> > [http://fixieconsulting.com](http://fixieconsulting.com)
> 
> --  
> Sent from my mobile device

--  
Joe Van Dyk  
[http://fixieconsulting.com](http://fixieconsulting.com)

---

<div class="post-metadata">

**Author:** ![Joshua\_Timberman](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/joshua_timberman/32/424_2.png) [@Joshua\_Timberman](https://discourse.chef.io/u/Joshua_Timberman)\
**Post date:** [August 7, 2009, 8:29pm UTC](https://discourse.chef.io/t/post-installation-issues/1252/16 "2009-08-07T20:29:57Z")

</div>

-----BEGIN PGP SIGNED MESSAGE-----  
Hash: SHA1

We're tracking all the Debian and Ubuntu packaging efforts in CHEF-63:

```
https://tickets.opscode.com/browse/CHEF-63

```

In the Chef packages, we require ruby1.8 as changes for 1.9 aren't  
quite in yet. CouchDB has packages in Debian 5 and Ubuntu 8.10+. Ohai  
is packaged by Bryan and is currently version 0.3.0, with 0.3.2 on  
deck. JSON is packaged by Debian as libjson-ruby. See the ticket for  
progress details on other requirements of Chef and Chef Server.

On Aug 7, 2009, at 2:11 PM, Joe Van Dyk wrote:

> ruby, couchdb, ohai, json, etc.
> 
> Joe
> 
> On Fri, Aug 7, 2009 at 12:54 PM, Bryan McLellan[btm@loftninjas.org](mailto:btm@loftninjas.org)  
> wrote:
> 
> > What deps? The gem dependencies? Those have all been individually  
> > packaged as debian packages so that other packages may use them as  
> > well. Installing the chef package will install the dependencies as  
> > debs instead of gems.
> > 
> > On 8/7/09, Joe Van Dyk [joe@fixieconsulting.com](mailto:joe@fixieconsulting.com) wrote:
> > 
> > > On Fri, Aug 7, 2009 at 11:22 AM, Joshua  
> > > Timberman[joshua@opscode.com](mailto:joshua@opscode.com) wrote:
> > > 
> > > > -----BEGIN PGP SIGNED MESSAGE-----  
> > > > Hash: SHA1
> > > > 
> > > > On Aug 7, 2009, at 2:59 AM, Graeme Mathieson wrote:
> > > > 
> > > > > That's awesome. 🙂 I don't suppose this will include a "proper"  
> > > > > Debian  
> > > > > package of Ruby Enterprise Edition for, say, Ubuntu 9.04? I'm  
> > > > > currently  
> > > > > trying to coerce some local Debian developers into doing one for  
> > > > > me, but  
> > > > > I  
> > > > > don't want to duplicate effort. 🙂
> > > > 
> > > > No, we're not attempting to package REE for Debian, just Chef and  
> > > > Chef's  
> > > > requirements. The best source of information on that would be the  
> > > > debian-ruby mailing list and #debian-ruby IRC channel (on  
> > > > [irc.oftc.net](http://irc.oftc.net)).
> > > 
> > > It would be awesome if all the chef requirements could be packaged  
> > > up  
> > > in the chef package (maybe call it chef-deps). Not sure how much  
> > > extra work that would be though.
> > > 
> > > --  
> > > Joe Van Dyk  
> > > [http://fixieconsulting.com](http://fixieconsulting.com)
> > 
> > --  
> > Sent from my mobile device
> 
> --  
> Joe Van Dyk  
> [http://fixieconsulting.com](http://fixieconsulting.com)

* * *

Opscode, Inc  
Joshua Timberman, Senior Solutions Engineer  
C: 720.878.4322 E: [joshua@opscode.com](mailto:joshua@opscode.com)

-----BEGIN PGP SIGNATURE-----  
Version: GnuPG v1.4.9 (Darwin)

iEYEARECAAYFAkp8jsUACgkQO97WSdVpzT2ocgCeOC144eNemQDGJq3nJUaO4qAu  
bPwAn3IAzhWC2c2fs+ygARnDZKD3R3K5  
=ZPKx  
-----END PGP SIGNATURE-----

---

<div class="post-metadata">

**Author:** ![Bryan\_McLellan](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/bryan_mclellan/32/81_2.png) [@Bryan\_McLellan](https://discourse.chef.io/u/Bryan_McLellan)\
**Post date:** [August 8, 2009, 7:13am UTC](https://discourse.chef.io/t/post-installation-issues/1252/17 "2009-08-08T07:13:07Z")

</div>

'apt-get install chef' will install all the magic. native packaging 4TW! 😃

On 8/7/09, Joe Van Dyk [joe@fixieconsulting.com](mailto:joe@fixieconsulting.com) wrote:

> ruby, couchdb, ohai, json, etc.
> 
> Joe
> 
> On Fri, Aug 7, 2009 at 12:54 PM, Bryan McLellan[btm@loftninjas.org](mailto:btm@loftninjas.org) wrote:
> 
> > What deps? The gem dependencies? Those have all been individually  
> > packaged as debian packages so that other packages may use them as  
> > well. Installing the chef package will install the dependencies as  
> > debs instead of gems.
> > 
> > On 8/7/09, Joe Van Dyk [joe@fixieconsulting.com](mailto:joe@fixieconsulting.com) wrote:
> > 
> > > On Fri, Aug 7, 2009 at 11:22 AM, Joshua Timberman[joshua@opscode.com](mailto:joshua@opscode.com)  
> > > wrote:
> > > 
> > > > -----BEGIN PGP SIGNED MESSAGE-----  
> > > > Hash: SHA1
> > > > 
> > > > On Aug 7, 2009, at 2:59 AM, Graeme Mathieson wrote:
> > > > 
> > > > > That's awesome. 🙂 I don't suppose this will include a "proper" Debian  
> > > > > package of Ruby Enterprise Edition for, say, Ubuntu 9.04? I'm currently  
> > > > > trying to coerce some local Debian developers into doing one for me,  
> > > > > but  
> > > > > I  
> > > > > don't want to duplicate effort. 🙂
> > > > 
> > > > No, we're not attempting to package REE for Debian, just Chef and Chef's  
> > > > requirements. The best source of information on that would be the  
> > > > debian-ruby mailing list and #debian-ruby IRC channel (on [irc.oftc.net](http://irc.oftc.net)).
> > > 
> > > It would be awesome if all the chef requirements could be packaged up  
> > > in the chef package (maybe call it chef-deps). Not sure how much  
> > > extra work that would be though.
> > > 
> > > --  
> > > Joe Van Dyk  
> > > [http://fixieconsulting.com](http://fixieconsulting.com)
> > 
> > --  
> > Sent from my mobile device
> 
> --  
> Joe Van Dyk  
> [http://fixieconsulting.com](http://fixieconsulting.com)

--  
Sent from my mobile device

---

<div class="post-metadata">

**Author:** ![Graeme\_Mathieson](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/graeme_mathieson/32/914_2.png) [@Graeme\_Mathieson](https://discourse.chef.io/u/Graeme_Mathieson)\
**Post date:** [August 9, 2009, 6:56am UTC](https://discourse.chef.io/t/post-installation-issues/1252/18 "2009-08-09T06:56:01Z")

</div>

On 7 Aug 2009, at 20:22, Joshua Timberman wrote:

> No, we're not attempting to package REE for Debian, just Chef and  
> Chef's requirements.

Cool, I shall continue to coerce Mark then. 🙂

G