500 on client run


#1

Hi all,

for some reason my chef-client runs on all machines on which they’ve worked for
months have started returning a 500, with the server log showing the following
after I run ‘sudo -E chef-client’ on the client:

~ Started request handling: Tue Dec 22 18:51:13 -0500 2009
~ Params: {“format”=>nil, “action”=>“show”, “id”=>“qafe01_example_com”,
“controller”=>“chef_server_slice/nodes”}
~ Cannot load node qafe01.example.com - (Merb::ControllerExceptions::NotFound)
/usr/lib64/ruby/gems/1.8/gems/chef-server-slice-0.7.8/app/controllers/nodes.rb:39:in
show' /usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/abstract_controller.rb:315:insend’
/usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/abstract_controller.rb:315:in
_call_action' /usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/abstract_controller.rb:289:in_dispatch’
/usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/merb_controller.rb:252:in
_dispatch' /usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/dispatcher.rb:100:indispatch_action’
/usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/dispatcher.rb:100:in
synchronize' /usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/dispatcher.rb:100:indispatch_action’
/usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/dispatcher.rb:74:in
handle' /usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/dispatcher.rb:36:inhandle’
/usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/rack/application.rb:17:in
call' /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/request_handler.rb:91:inprocess_request’
/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstract_request_handler.rb:206:in
main_loop' /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/application_spawner.rb:118:inrun’
/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/application_spawner.rb:69:in
spawn_application' /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/utils.rb:182:insafe_fork’
/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/application_spawner.rb:62:in
spawn_application' /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/application_spawner.rb:45:inspawn_application’
/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/spawn_manager.rb:158:in
spawn_application' /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/spawn_manager.rb:286:inhandle_spawn_application’
/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstract_server.rb:351:in
__send__' /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstract_server.rb:351:inmain_loop’
/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstract_server.rb:195:in
`start_synchronously’
/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/bin/passenger-spawn-server:61
~ Params: {“format”=>nil, “action”=>“show”, “id”=>“qafe01.example.com”,
“controller”=>“chef_server_slice/nodes”}
~

The web UI works fine, and registration and validations are also OK (i.e. if I
delete the node and its registration, and then re-run the client, I get a 401
and can then validate – after that I start getting a 500 again). The server
version is 0.7.8, and I’ve tried every client version from 0.7.4 to 0.7.14
(also switched around ohai versions on both machines). Any ideas on what’s
going wrong here? As far as I know no configurations have been changed.

thanks!
Kristof


#2

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

This looks like a couchdb issue - what version are you running?

Adam

kredei@avenue100.com wrote:

Hi all,

for some reason my chef-client runs on all machines on which they’ve worked for
months have started returning a 500, with the server log showing the following
after I run ‘sudo -E chef-client’ on the client:

~ Started request handling: Tue Dec 22 18:51:13 -0500 2009
~ Params: {“format”=>nil, “action”=>“show”, “id”=>“qafe01_example_com”,
“controller”=>“chef_server_slice/nodes”}
~ Cannot load node qafe01.example.com - (Merb::ControllerExceptions::NotFound)
/usr/lib64/ruby/gems/1.8/gems/chef-server-slice-0.7.8/app/controllers/nodes.rb:39:in
show' /usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/abstract_controller.rb:315:insend’
/usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/abstract_controller.rb:315:in
_call_action' /usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/abstract_controller.rb:289:in_dispatch’
/usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/merb_controller.rb:252:in
_dispatch' /usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/dispatcher.rb:100:indispatch_action’
/usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/dispatcher.rb:100:in
synchronize' /usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/dispatcher.rb:100:indispatch_action’
/usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/dispatcher.rb:74:in
handle' /usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/dispatcher.rb:36:inhandle’
/usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/rack/application.rb:17:in
call' /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/request_handler.rb:91:inprocess_request’
/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstract_request_handler.rb:206:in
main_loop' /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/application_spawner.rb:118:inrun’
/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/application_spawner.rb:69:in
spawn_application' /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/utils.rb:182:insafe_fork’
/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/application_spawner.rb:62:in
spawn_application' /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/application_spawner.rb:45:inspawn_application’
/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/spawn_manager.rb:158:in
spawn_application' /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/spawn_manager.rb:286:inhandle_spawn_application’
/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstract_server.rb:351:in
__send__' /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstract_server.rb:351:inmain_loop’
/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstract_server.rb:195:in
`start_synchronously’
/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/bin/passenger-spawn-server:61
~ Params: {“format”=>nil, “action”=>“show”, “id”=>“qafe01.example.com”,
“controller”=>“chef_server_slice/nodes”}
~

The web UI works fine, and registration and validations are also OK (i.e. if I
delete the node and its registration, and then re-run the client, I get a 401
and can then validate – after that I start getting a 500 again). The server
version is 0.7.8, and I’ve tried every client version from 0.7.4 to 0.7.14
(also switched around ohai versions on both machines). Any ideas on what’s
going wrong here? As far as I know no configurations have been changed.

thanks!
Kristof


Opscode, Inc.
Adam Jacob, CTO
T: (206) 508-7449 E: adam@opscode.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJLMWLGAAoJEK+ksDjf4JoCPRQH+gIU9AcG354pJFhEd+7ClErD
A0xQiVKty0q0psP4f11KYhA3QrIwvs79IXPTOjLsJcjNnH+wOd35branbR/RJlRe
XjrzZnNIb1ZddUaqyTQ5sRjMx5kIs8XgIqVviFKt016IpC33/6cA8XcrMP1ZZ1Y6
Es/DKMkz6szrIxv4k0gpHaAxx9uo7BQm14D4LldBbxXelZKQf6gVSwc0mYro9qEU
bdzdshDaJYkbCZYd877scF7gnvXM5/9n2a9+JH3GO1+TxWqoAcOwdxbPkAxETirI
/oofw60P6bQmjy6ctymsj9MWjgwK1WmSfZ5AnNrUd4KfliglmF8ZQbaT658mMwc=
=3miA
-----END PGP SIGNATURE-----


#3

Might sound silly, but make sure you haven’t run out of disk space on the Chef server.

Adam Jacob wrote:

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

This looks like a couchdb issue - what version are you running?

Adam

kredei@avenue100.com wrote:

Hi all,

for some reason my chef-client runs on all machines on which they’ve worked for
months have started returning a 500, with the server log showing the following
after I run ‘sudo -E chef-client’ on the client:

~ Started request handling: Tue Dec 22 18:51:13 -0500 2009
~ Params: {“format”=>nil, “action”=>“show”, “id”=>“qafe01_example_com”,
“controller”=>“chef_server_slice/nodes”}
~ Cannot load node qafe01.example.com - (Merb::ControllerExceptions::NotFound)
/usr/lib64/ruby/gems/1.8/gems/chef-server-slice-0.7.8/app/controllers/nodes.rb:39:in
show' /usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/abstract_controller.rb:315:insend’
/usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/abstract_controller.rb:315:in
_call_action' /usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/abstract_controller.rb:289:in_dispatch’
/usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/merb_controller.rb:252:in
_dispatch' /usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/dispatcher.rb:100:indispatch_action’
/usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/dispatcher.rb:100:in
synchronize' /usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/dispatcher.rb:100:indispatch_action’
/usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/dispatcher.rb:74:in
handle' /usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/dispatcher.rb:36:inhandle’
/usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/rack/application.rb:17:in
call' /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/request_handler.rb:91:inprocess_request’
/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstract_request_handler.rb:206:in
main_loop' /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/application_spawner.rb:118:inrun’
/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/application_spawner.rb:69:in
spawn_application' /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/utils.rb:182:insafe_fork’
/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/application_spawner.rb:62:in
spawn_application' /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/application_spawner.rb:45:inspawn_application’
/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/spawn_manager.rb:158:in
spawn_application' /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/spawn_manager.rb:286:inhandle_spawn_application’
/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstract_server.rb:351:in
__send__' /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstract_server.rb:351:inmain_loop’
/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstract_server.rb:195:in
`start_synchronously’
/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/bin/passenger-spawn-server:61
~ Params: {“format”=>nil, “action”=>“show”, “id”=>“qafe01.example.com”,
“controller”=>“chef_server_slice/nodes”}
~

The web UI works fine, and registration and validations are also OK (i.e. if I
delete the node and its registration, and then re-run the client, I get a 401
and can then validate – after that I start getting a 500 again). The server
version is 0.7.8, and I’ve tried every client version from 0.7.4 to 0.7.14
(also switched around ohai versions on both machines). Any ideas on what’s
going wrong here? As far as I know no configurations have been changed.

thanks!
Kristof


Opscode, Inc.
Adam Jacob, CTO
T: (206) 508-7449 E: adam@opscode.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJLMWLGAAoJEK+ksDjf4JoCPRQH+gIU9AcG354pJFhEd+7ClErD
A0xQiVKty0q0psP4f11KYhA3QrIwvs79IXPTOjLsJcjNnH+wOd35branbR/RJlRe
XjrzZnNIb1ZddUaqyTQ5sRjMx5kIs8XgIqVviFKt016IpC33/6cA8XcrMP1ZZ1Y6
Es/DKMkz6szrIxv4k0gpHaAxx9uo7BQm14D4LldBbxXelZKQf6gVSwc0mYro9qEU
bdzdshDaJYkbCZYd877scF7gnvXM5/9n2a9+JH3GO1+TxWqoAcOwdxbPkAxETirI
/oofw60P6bQmjy6ctymsj9MWjgwK1WmSfZ5AnNrUd4KfliglmF8ZQbaT658mMwc=
=3miA
-----END PGP SIGNATURE-----


#4

Looks like version 0.9.0:

-bash-3.2$ sudo yum list | grep couch
couchdb.x86_64 0.9.0-2.el5
installed
couchdb.x86_64 0.10.0-1.el5 epel

On 12/22/09 7:22 PM, “Adam Jacob” adam@opscode.com wrote:

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

This looks like a couchdb issue - what version are you running?

Adam

kredei@avenue100.com wrote:

Hi all,

for some reason my chef-client runs on all machines on which they’ve worked
for
months have started returning a 500, with the server log showing the
following
after I run ‘sudo -E chef-client’ on the client:

~ Started request handling: Tue Dec 22 18:51:13 -0500 2009
~ Params: {“format”=>nil, “action”=>“show”, “id”=>“qafe01_example_com”,
“controller”=>“chef_server_slice/nodes”}
~ Cannot load node qafe01.example.com -
(Merb::ControllerExceptions::NotFound)
/usr/lib64/ruby/gems/1.8/gems/chef-server-slice-0.7.8/app/controllers/nodes.r
b:39:in
show' /usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/abstr act_controller.rb:315:insend’
/usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/abstr
act_controller.rb:315:in
_call_action' /usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/abstr act_controller.rb:289:indispatch’
/usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/merb

controller.rb:252:in
_dispatch' /usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/dispatc her.rb:100:indispatch_action’
/usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/dispatc
her.rb:100:in
synchronize' /usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/dispatc her.rb:100:indispatch_action’
/usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/dispatc
her.rb:74:in
handle' /usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/dispatc her.rb:36:inhandle’
/usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/rack/application
.rb:17:in
call' /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/requ est_handler.rb:91:inprocess_request’
/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstract_
request_handler.rb:206:in
main_loop' /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/appl ication_spawner.rb:118:inrun’
/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/appl
ication_spawner.rb:69:in
spawn_application' /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/utils.rb: 182:insafe_fork’
/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/appl
ication_spawner.rb:62:in
spawn_application' /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/appl ication_spawner.rb:45:inspawn_application’
/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/spawn_man
ager.rb:158:in
spawn_application' /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/spawn_man ager.rb:286:inhandle_spawn_application’
/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstract_
server.rb:351:in
__send__' /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstract_ server.rb:351:inmain_loop’
/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstract_
server.rb:195:in
`start_synchronously’
/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/bin/passenger-spawn-server:61
~ Params: {“format”=>nil, “action”=>“show”, “id”=>“qafe01.example.com”,
“controller”=>“chef_server_slice/nodes”}
~

The web UI works fine, and registration and validations are also OK (i.e. if
I
delete the node and its registration, and then re-run the client, I get a 401
and can then validate – after that I start getting a 500 again). The server
version is 0.7.8, and I’ve tried every client version from 0.7.4 to 0.7.14
(also switched around ohai versions on both machines). Any ideas on what’s
going wrong here? As far as I know no configurations have been changed.

thanks!
Kristof


Opscode, Inc.
Adam Jacob, CTO
T: (206) 508-7449 E: adam@opscode.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJLMWLGAAoJEK+ksDjf4JoCPRQH+gIU9AcG354pJFhEd+7ClErD
A0xQiVKty0q0psP4f11KYhA3QrIwvs79IXPTOjLsJcjNnH+wOd35branbR/RJlRe
XjrzZnNIb1ZddUaqyTQ5sRjMx5kIs8XgIqVviFKt016IpC33/6cA8XcrMP1ZZ1Y6
Es/DKMkz6szrIxv4k0gpHaAxx9uo7BQm14D4LldBbxXelZKQf6gVSwc0mYro9qEU
bdzdshDaJYkbCZYd877scF7gnvXM5/9n2a9+JH3GO1+TxWqoAcOwdxbPkAxETirI
/oofw60P6bQmjy6ctymsj9MWjgwK1WmSfZ5AnNrUd4KfliglmF8ZQbaT658mMwc=
=3miA
-----END PGP SIGNATURE-----


#5

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

Kristof, how you doing with this?

Adam

Kristof Redei wrote:

Looks like version 0.9.0:

-bash-3.2$ sudo yum list | grep couch
couchdb.x86_64 0.9.0-2.el5
installed
couchdb.x86_64 0.10.0-1.el5 epel

On 12/22/09 7:22 PM, “Adam Jacob” adam@opscode.com wrote:

This looks like a couchdb issue - what version are you running?

Adam

kredei@avenue100.com wrote:

Hi all,

for some reason my chef-client runs on all machines on which they’ve worked
for
months have started returning a 500, with the server log showing the
following
after I run ‘sudo -E chef-client’ on the client:

~ Started request handling: Tue Dec 22 18:51:13 -0500 2009
~ Params: {“format”=>nil, “action”=>“show”, “id”=>“qafe01_example_com”,
“controller”=>“chef_server_slice/nodes”}
~ Cannot load node qafe01.example.com -
(Merb::ControllerExceptions::NotFound)
/usr/lib64/ruby/gems/1.8/gems/chef-server-slice-0.7.8/app/controllers/nodes.r
b:39:in
show' /usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/abstr act_controller.rb:315:insend’
/usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/abstr
act_controller.rb:315:in
_call_action' /usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/abstr act_controller.rb:289:indispatch’
/usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/merb

controller.rb:252:in
_dispatch' /usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/dispatc her.rb:100:indispatch_action’
/usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/dispatc
her.rb:100:in
synchronize' /usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/dispatc her.rb:100:indispatch_action’
/usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/dispatc
her.rb:74:in
handle' /usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/dispatc her.rb:36:inhandle’
/usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/rack/application
.rb:17:in
call' /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/requ est_handler.rb:91:inprocess_request’
/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstract_
request_handler.rb:206:in
main_loop' /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/appl ication_spawner.rb:118:inrun’
/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/appl
ication_spawner.rb:69:in
spawn_application' /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/utils.rb: 182:insafe_fork’
/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/appl
ication_spawner.rb:62:in
spawn_application' /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/appl ication_spawner.rb:45:inspawn_application’
/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/spawn_man
ager.rb:158:in
spawn_application' /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/spawn_man ager.rb:286:inhandle_spawn_application’
/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstract_
server.rb:351:in
__send__' /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstract_ server.rb:351:inmain_loop’
/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstract_
server.rb:195:in
`start_synchronously’
/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/bin/passenger-spawn-server:61
~ Params: {“format”=>nil, “action”=>“show”, “id”=>“qafe01.example.com”,
“controller”=>“chef_server_slice/nodes”}
~

The web UI works fine, and registration and validations are also OK (i.e. if
I
delete the node and its registration, and then re-run the client, I get a 401
and can then validate – after that I start getting a 500 again). The server
version is 0.7.8, and I’ve tried every client version from 0.7.4 to 0.7.14
(also switched around ohai versions on both machines). Any ideas on what’s
going wrong here? As far as I know no configurations have been changed.

thanks!
Kristof


Opscode, Inc.
Adam Jacob, CTO
T: (206) 508-7449 E: adam@opscode.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJLOP3fAAoJEK+ksDjf4JoCrzAIAJp4eotqqCMl45e3ei1ojAzX
BlNK5GZj9Xkg/kQ2q6upvQn7WOGy7M9AvDVq8jIwYC6tx9aXmfCOj2NsxTvb0aIR
n7YMBF15vA4aQ7+irAgZ3x7pPwwsiUXj1secGG66rrefupuoA+L89ygiZwE4iDjC
Kml+3plkrcrBFfAlYyhQ2DA24dqPIENUc96NQNafT86Sp5V80Rl5ndhvP+hqLSL/
MG8OZ3sHkyve7naDl5ySWgxm+7CAL6d4v1obzRNZugaCWsLa+PdfQhOGJMzJxecW
mkoTKVHYr1kqUc/ozvxx6RW2Pv+T9aILFw+BUz/dWI6a9mpc2D/VTgaJLofT660=
=GfD/
-----END PGP SIGNATURE-----


#6

I upgraded couchDB to 0.9.1 and also ended up upgrading the chef server
version to 0.7.16. That made the error disappear. So, in sum, I’m not sure
what was causing it, but everything works now :slight_smile:

Kristof

On 12/28/09 1:50 PM, “Adam Jacob” adam@opscode.com wrote:

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

Kristof, how you doing with this?

Adam

Kristof Redei wrote:

Looks like version 0.9.0:

-bash-3.2$ sudo yum list | grep couch
couchdb.x86_64 0.9.0-2.el5
installed
couchdb.x86_64 0.10.0-1.el5 epel

On 12/22/09 7:22 PM, “Adam Jacob” adam@opscode.com wrote:

This looks like a couchdb issue - what version are you running?

Adam

kredei@avenue100.com wrote:

Hi all,

for some reason my chef-client runs on all machines on which they’ve
worked
for
months have started returning a 500, with the server log showing the
following
after I run ‘sudo -E chef-client’ on the client:

~ Started request handling: Tue Dec 22 18:51:13 -0500 2009
~ Params: {“format”=>nil, “action”=>“show”, “id”=>“qafe01_example_com”,
“controller”=>“chef_server_slice/nodes”}
~ Cannot load node qafe01.example.com -
(Merb::ControllerExceptions::NotFound)
/usr/lib64/ruby/gems/1.8/gems/chef-server-slice-0.7.8/app/controllers/node
s.r
b:39:in
show' /usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/ab str act_controller.rb:315:insend’
/usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/ab
str
act_controller.rb:315:in
_call_action' /usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/ab str act_controller.rb:289:indispatch’
/usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/me
rb

controller.rb:252:in
_dispatch' /usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/disp atc her.rb:100:indispatch_action’
/usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/disp
atc
her.rb:100:in
synchronize' /usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/disp atc her.rb:100:indispatch_action’
/usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/disp
atc
her.rb:74:in
handle' /usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/disp atc her.rb:36:inhandle’
/usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/rack/applicat
ion
.rb:17:in
call' /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/r equ est_handler.rb:91:inprocess_request’
/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstra
ct_
request_handler.rb:206:in
main_loop' /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/a ppl ication_spawner.rb:118:inrun’
/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/a
ppl
ication_spawner.rb:69:in
spawn_application' /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/utils. rb: 182:insafe_fork’
/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/a
ppl
ication_spawner.rb:62:in
spawn_application' /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/a ppl ication_spawner.rb:45:inspawn_application’
/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/spawn_
man
ager.rb:158:in
spawn_application' /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/spawn_ man ager.rb:286:inhandle_spawn_application’
/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstra
ct_
server.rb:351:in
__send__' /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstra ct_ server.rb:351:inmain_loop’
/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstra
ct_
server.rb:195:in
`start_synchronously’

/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/bin/passenger-spawn-server:6>>>>>
1

~ Params: {“format”=>nil, “action”=>“show”, “id”=>“qafe01.example.com”,
“controller”=>“chef_server_slice/nodes”}
~

The web UI works fine, and registration and validations are also OK (i.e.
if
I
delete the node and its registration, and then re-run the client, I get a
401
and can then validate – after that I start getting a 500 again). The
server
version is 0.7.8, and I’ve tried every client version from 0.7.4 to 0.7.14
(also switched around ohai versions on both machines). Any ideas on what’s
going wrong here? As far as I know no configurations have been changed.

thanks!
Kristof


Opscode, Inc.
Adam Jacob, CTO
T: (206) 508-7449 E: adam@opscode.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJLOP3fAAoJEK+ksDjf4JoCrzAIAJp4eotqqCMl45e3ei1ojAzX
BlNK5GZj9Xkg/kQ2q6upvQn7WOGy7M9AvDVq8jIwYC6tx9aXmfCOj2NsxTvb0aIR
n7YMBF15vA4aQ7+irAgZ3x7pPwwsiUXj1secGG66rrefupuoA+L89ygiZwE4iDjC
Kml+3plkrcrBFfAlYyhQ2DA24dqPIENUc96NQNafT86Sp5V80Rl5ndhvP+hqLSL/
MG8OZ3sHkyve7naDl5ySWgxm+7CAL6d4v1obzRNZugaCWsLa+PdfQhOGJMzJxecW
mkoTKVHYr1kqUc/ozvxx6RW2Pv+T9aILFw+BUz/dWI6a9mpc2D/VTgaJLofT660=
=GfD/
-----END PGP SIGNATURE-----


#7

I meant couchDB 0.10.0…

On 12/28/09 3:44 PM, “Kristof Redei” kredei@avenue100.com wrote:

I upgraded couchDB to 0.9.1 and also ended up upgrading the chef server
version to 0.7.16. That made the error disappear. So, in sum, I’m not sure
what was causing it, but everything works now :slight_smile:

Kristof

On 12/28/09 1:50 PM, “Adam Jacob” adam@opscode.com wrote:

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

Kristof, how you doing with this?

Adam

Kristof Redei wrote:

Looks like version 0.9.0:

-bash-3.2$ sudo yum list | grep couch
couchdb.x86_64 0.9.0-2.el5
installed
couchdb.x86_64 0.10.0-1.el5 epel

On 12/22/09 7:22 PM, “Adam Jacob” adam@opscode.com wrote:

This looks like a couchdb issue - what version are you running?

Adam

kredei@avenue100.com wrote:

Hi all,

for some reason my chef-client runs on all machines on which they’ve
worked
for
months have started returning a 500, with the server log showing the
following
after I run ‘sudo -E chef-client’ on the client:

~ Started request handling: Tue Dec 22 18:51:13 -0500 2009
~ Params: {“format”=>nil, “action”=>“show”, “id”=>“qafe01_example_com”,
“controller”=>“chef_server_slice/nodes”}
~ Cannot load node qafe01.example.com -
(Merb::ControllerExceptions::NotFound)

/usr/lib64/ruby/gems/1.8/gems/chef-server-slice-0.7.8/app/controllers/nod>>>>>>
e

s.r
b:39:in
`show’

/usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/a>>>>>>
b

str
act_controller.rb:315:in
`send’

/usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/a>>>>>>
b

str
act_controller.rb:315:in
`_call_action’

/usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/a>>>>>>
b

str
act_controller.rb:289:in
`_dispatch’

/usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/controller/m>>>>>>
e

rb_
controller.rb:252:in
`_dispatch’

/usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/dis>>>>>>
p

atc
her.rb:100:in
`dispatch_action’

/usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/dis>>>>>>
p

atc
her.rb:100:in
`synchronize’

/usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/dis>>>>>>
p

atc
her.rb:100:in
`dispatch_action’

/usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/dis>>>>>>
p

atc
her.rb:74:in
`handle’

/usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/dispatch/dis>>>>>>
p

atc
her.rb:36:in
`handle’

/usr/lib64/ruby/gems/1.8/gems/merb-core-1.0.12/lib/merb-core/rack/applica>>>>>>
t

ion
.rb:17:in
`call’

/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/>>>>>>
r

equ
est_handler.rb:91:in
`process_request’

/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstr>>>>>>
a

ct_
request_handler.rb:206:in
`main_loop’

/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/>>>>>>
a

ppl
ication_spawner.rb:118:in
`run’

/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/>>>>>>
a

ppl
ication_spawner.rb:69:in
`spawn_application’

/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/utils>>>>>>
.

rb:
182:in
`safe_fork’

/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/>>>>>>
a

ppl
ication_spawner.rb:62:in
`spawn_application’

/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/>>>>>>
a

ppl
ication_spawner.rb:45:in
`spawn_application’

/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/spawn>>>>>>
_

man
ager.rb:158:in
`spawn_application’

/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/spawn>>>>>>
_

man
ager.rb:286:in
`handle_spawn_application’

/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstr>>>>>>
a

ct_
server.rb:351:in
`send

/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstr>>>>>>
a

ct_
server.rb:351:in
`main_loop’

/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstr>>>>>>
a

ct_
server.rb:195:in
`start_synchronously’

/usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/bin/passenger-spawn-server:6>>>>>

1

~ Params: {“format”=>nil, “action”=>“show”, “id”=>“qafe01.example.com”,
“controller”=>“chef_server_slice/nodes”}
~

The web UI works fine, and registration and validations are also OK (i.e.
if
I
delete the node and its registration, and then re-run the client, I get a
401
and can then validate – after that I start getting a 500 again). The
server
version is 0.7.8, and I’ve tried every client version from 0.7.4 to
0.7.14
(also switched around ohai versions on both machines). Any ideas on
what’s
going wrong here? As far as I know no configurations have been changed.

thanks!
Kristof


Opscode, Inc.
Adam Jacob, CTO
T: (206) 508-7449 E: adam@opscode.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJLOP3fAAoJEK+ksDjf4JoCrzAIAJp4eotqqCMl45e3ei1ojAzX
BlNK5GZj9Xkg/kQ2q6upvQn7WOGy7M9AvDVq8jIwYC6tx9aXmfCOj2NsxTvb0aIR
n7YMBF15vA4aQ7+irAgZ3x7pPwwsiUXj1secGG66rrefupuoA+L89ygiZwE4iDjC
Kml+3plkrcrBFfAlYyhQ2DA24dqPIENUc96NQNafT86Sp5V80Rl5ndhvP+hqLSL/
MG8OZ3sHkyve7naDl5ySWgxm+7CAL6d4v1obzRNZugaCWsLa+PdfQhOGJMzJxecW
mkoTKVHYr1kqUc/ozvxx6RW2Pv+T9aILFw+BUz/dWI6a9mpc2D/VTgaJLofT660=
=GfD/
-----END PGP SIGNATURE-----