| 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, <
">
> 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
--
AJ Christensen, Software Engineer
|