# 500 on client run

**URL:** <https://discourse.chef.io/t/500-on-client-run/1324>\
**Category:** Chef Infra (archive)\
**Created:** [December 23, 2009, 12:19am UTC](https://discourse.chef.io/t/500-on-client-run/1324 "2009-12-23T00:19:38Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kristof\_Redei](https://avatars.discourse-cdn.com/v4/letter/k/b5e925/32.png) [@Kristof\_Redei](https://discourse.chef.io/u/Kristof_Redei)\
**Post date:** [December 23, 2009, 12:19am UTC](https://discourse.chef.io/t/500-on-client-run/1324/1 "2009-12-23T00:19:38Z")

</div>

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](http://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:in`send’  
/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:in`dispatch\_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:in`dispatch\_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:in`handle’  
/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:in`process\_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:in`run’  
/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:in`safe\_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:in`spawn\_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:in`handle\_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:in`main\_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](http://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

---

<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:** [December 23, 2009, 12:22am UTC](https://discourse.chef.io/t/500-on-client-run/1324/2 "2009-12-23T00:22:30Z")

</div>

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

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

Adam

[kredei@avenue100.com](mailto: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](http://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:in `send'  
> /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:in `dispatch\_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:in `dispatch\_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:in `handle'  
> /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:in `process\_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:in `run'  
> /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:in `safe\_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:in `spawn\_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:in `handle\_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:in `main\_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](http://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](mailto:adam@opscode.com)  
-----BEGIN PGP SIGNATURE-----  
Version: GnuPG v1.4.10 (Darwin)  
Comment: Using GnuPG with Mozilla - [http://enigmail.mozdev.org/](http://enigmail.mozdev.org/)

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

---

<div class="post-metadata">

**Author:** ![Nick\_Ohanian](https://avatars.discourse-cdn.com/v4/letter/n/5daacb/32.png) [@Nick\_Ohanian](https://discourse.chef.io/u/Nick_Ohanian)\
**Post date:** [December 23, 2009, 12:59am UTC](https://discourse.chef.io/t/500-on-client-run/1324/3 "2009-12-23T00:59:41Z")

</div>

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](mailto: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](http://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:in `send'  
> > /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:in `dispatch\_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:in `dispatch\_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:in `handle'  
> > /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:in `process\_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:in `run'  
> > /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:in `safe\_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:in `spawn\_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:in `handle\_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:in `main\_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](http://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](mailto:adam@opscode.com)  
> -----BEGIN PGP SIGNATURE-----  
> Version: GnuPG v1.4.10 (Darwin)  
> Comment: Using GnuPG with Mozilla - [http://enigmail.mozdev.org/](http://enigmail.mozdev.org/)
> 
> iQEcBAEBAgAGBQJLMWLGAAoJEK+ksDjf4JoCPRQH+gIU9AcG354pJFhEd+7ClErD  
> A0xQiVKty0q0psP4f11KYhA3QrIwvs79IXPTOjLsJcjNnH+wOd35branbR/RJlRe  
> XjrzZnNIb1ZddUaqyTQ5sRjMx5kIs8XgIqVviFKt016IpC33/6cA8XcrMP1ZZ1Y6  
> Es/DKMkz6szrIxv4k0gpHaAxx9uo7BQm14D4LldBbxXelZKQf6gVSwc0mYro9qEU  
> bdzdshDaJYkbCZYd877scF7gnvXM5/9n2a9+JH3GO1+TxWqoAcOwdxbPkAxETirI  
> /oofw60P6bQmjy6ctymsj9MWjgwK1WmSfZ5AnNrUd4KfliglmF8ZQbaT658mMwc=  
> =3miA  
> -----END PGP SIGNATURE-----

---

<div class="post-metadata">

**Author:** ![Kristof\_Redei](https://avatars.discourse-cdn.com/v4/letter/k/b5e925/32.png) [@Kristof\_Redei](https://discourse.chef.io/u/Kristof_Redei)\
**Post date:** [December 23, 2009, 3:42pm UTC](https://discourse.chef.io/t/500-on-client-run/1324/4 "2009-12-23T15:42:17Z")

</div>

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](mailto: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](mailto: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](http://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:in `send'  
> > /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: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/dispatc her.rb:100:in `dispatch\_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:in `dispatch\_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:in `handle'  
> > /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:in `process\_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:in `run'  
> > /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:in `safe\_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: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/abstract\_  
> > server.rb:351:in  
> > ` __send__' /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstract_ server.rb:351:in `main\_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](http://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](mailto:adam@opscode.com)  
> -----BEGIN PGP SIGNATURE-----  
> Version: GnuPG v1.4.10 (Darwin)  
> Comment: Using GnuPG with Mozilla - [http://enigmail.mozdev.org/](http://enigmail.mozdev.org/)
> 
> iQEcBAEBAgAGBQJLMWLGAAoJEK+ksDjf4JoCPRQH+gIU9AcG354pJFhEd+7ClErD  
> A0xQiVKty0q0psP4f11KYhA3QrIwvs79IXPTOjLsJcjNnH+wOd35branbR/RJlRe  
> XjrzZnNIb1ZddUaqyTQ5sRjMx5kIs8XgIqVviFKt016IpC33/6cA8XcrMP1ZZ1Y6  
> Es/DKMkz6szrIxv4k0gpHaAxx9uo7BQm14D4LldBbxXelZKQf6gVSwc0mYro9qEU  
> bdzdshDaJYkbCZYd877scF7gnvXM5/9n2a9+JH3GO1+TxWqoAcOwdxbPkAxETirI  
> /oofw60P6bQmjy6ctymsj9MWjgwK1WmSfZ5AnNrUd4KfliglmF8ZQbaT658mMwc=  
> =3miA  
> -----END PGP SIGNATURE-----

---

<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:** [December 28, 2009, 6:50pm UTC](https://discourse.chef.io/t/500-on-client-run/1324/5 "2009-12-28T18:50:07Z")

</div>

-----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](mailto:adam@opscode.com) wrote:
> 
> This looks like a couchdb issue - what version are you running?
> 
> Adam
> 
> [kredei@avenue100.com](mailto: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](http://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:in `send'  
> > > > /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: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/dispatc her.rb:100:in `dispatch\_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:in `dispatch\_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:in `handle'  
> > > > /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:in `process\_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:in `run'  
> > > > /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:in `safe\_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: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/abstract\_  
> > > > server.rb:351:in  
> > > > ` __send__' /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstract_ server.rb:351:in `main\_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](http://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](mailto:adam@opscode.com)  
-----BEGIN PGP SIGNATURE-----  
Version: GnuPG v1.4.10 (Darwin)  
Comment: Using GnuPG with Mozilla - [http://enigmail.mozdev.org/](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-----

---

<div class="post-metadata">

**Author:** ![Kristof\_Redei](https://avatars.discourse-cdn.com/v4/letter/k/b5e925/32.png) [@Kristof\_Redei](https://discourse.chef.io/u/Kristof_Redei)\
**Post date:** [December 28, 2009, 8:44pm UTC](https://discourse.chef.io/t/500-on-client-run/1324/6 "2009-12-28T20:44:37Z")

</div>

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 🙂

Kristof

On 12/28/09 1:50 PM, "Adam Jacob" [adam@opscode.com](mailto: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](mailto:adam@opscode.com) wrote:
> > 
> > This looks like a couchdb issue - what version are you running?
> > 
> > Adam
> > 
> > [kredei@avenue100.com](mailto: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](http://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:in `send'  
> > > > > /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:in `_dispatch'  
> > > > > /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:in `dispatch\_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:in `dispatch\_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:in `handle'  
> > > > > /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:in `process\_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: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/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:in `main\_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](http://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](mailto:adam@opscode.com)  
> -----BEGIN PGP SIGNATURE-----  
> Version: GnuPG v1.4.10 (Darwin)  
> Comment: Using GnuPG with Mozilla - [http://enigmail.mozdev.org/](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-----

---

<div class="post-metadata">

**Author:** ![Kristof\_Redei](https://avatars.discourse-cdn.com/v4/letter/k/b5e925/32.png) [@Kristof\_Redei](https://discourse.chef.io/u/Kristof_Redei)\
**Post date:** [December 28, 2009, 8:46pm UTC](https://discourse.chef.io/t/500-on-client-run/1324/7 "2009-12-28T20:46:36Z")

</div>

I meant couchDB 0.10.0...

On 12/28/09 3:44 PM, "Kristof Redei" [kredei@avenue100.com](mailto: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 🙂
> 
> Kristof
> 
> On 12/28/09 1:50 PM, "Adam Jacob" [adam@opscode.com](mailto: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](mailto:adam@opscode.com) wrote:
> > > 
> > > This looks like a couchdb issue - what version are you running?
> > > 
> > > Adam
> > > 
> > > [kredei@avenue100.com](mailto: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](http://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](http://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](mailto:adam@opscode.com)  
> > -----BEGIN PGP SIGNATURE-----  
> > Version: GnuPG v1.4.10 (Darwin)  
> > Comment: Using GnuPG with Mozilla - [http://enigmail.mozdev.org/](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-----