# /!\\ FAILSAFE /!\\ error with Rails 2.3.4

**URL:** <https://www.ruby-forum.com/t/failsafe-error-with-rails-2-3-4/182783>\
**Category:** Rails\
**Created:** [February 2, 2010, 7:34pm UTC](https://www.ruby-forum.com/t/failsafe-error-with-rails-2-3-4/182783 "2010-02-02T19:34:35Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![casper\_the\_ghost](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/58956e/32.png) [@casper\_the\_ghost](https://www.ruby-forum.com/u/casper_the_ghost)\
**Post date:** [February 2, 2010, 7:34pm UTC](https://www.ruby-forum.com/t/failsafe-error-with-rails-2-3-4/182783/1 "2010-02-02T19:34:35Z")

</div>

Does anyone know what could be causing this error? I am currently  
experiencing it when some browser submit a multipart form witha file  
attached.

Thanks!  
Tom

/!\ FAILSAFE /!\ Tue Feb 02 13:28:35 -0500 2010  
Status: 500 Internal Server Error  
no marshal\_dump is defined for class Proc  
/opt/ruby-enterprise-1.8.6-20090201/lib/ruby/gems/1.8/gems/  
activesupport-2.3.4/lib/active\_support/message\_verifier.rb:36:in  
`dump' /opt/ruby-enterprise-1.8.6-20090201/lib/ruby/gems/1.8/gems/ activesupport-2.3.4/lib/active_support/message_verifier.rb:36:in`generate’  
/opt/ruby-enterprise-1.8.6-20090201/lib/ruby/gems/1.8/gems/  
actionpack-2.3.4/lib/action\_controller/session/cookie\_store.rb:151:in  
`marshal' /opt/ruby-enterprise-1.8.6-20090201/lib/ruby/gems/1.8/gems/ actionpack-2.3.4/lib/action_controller/session/cookie_store.rb:100:in`call’  
/opt/ruby-enterprise-1.8.6-20090201/lib/ruby/gems/1.8/gems/  
actionpack-2.3.4/lib/action\_controller/failsafe.rb:26:in `call' /opt/ruby-enterprise-1.8.6-20090201/lib/ruby/gems/1.8/gems/ passenger-2.2.4/vendor/rack-1.0.0-git/lib/rack/lock.rb:11:in`call’  
/opt/ruby-enterprise-1.8.6-20090201/lib/ruby/gems/1.8/gems/  
passenger-2.2.4/vendor/rack-1.0.0-git/lib/rack/lock.rb:11:in  
`synchronize' /opt/ruby-enterprise-1.8.6-20090201/lib/ruby/gems/1.8/gems/ passenger-2.2.4/vendor/rack-1.0.0-git/lib/rack/lock.rb:11:in`call’  
/opt/ruby-enterprise-1.8.6-20090201/lib/ruby/gems/1.8/gems/  
actionpack-2.3.4/lib/action\_controller/dispatcher.rb:106:in `call' /opt/ruby-enterprise-1.8.6-20090201/lib/ruby/gems/1.8/gems/ passenger-2.2.4/lib/phusion_passenger/rack/request_handler.rb:91:in`process\_request’  
/opt/ruby-enterprise-1.8.6-20090201/lib/ruby/gems/1.8/gems/  
passenger-2.2.4/lib/phusion\_passenger/abstract\_request\_handler.rb:  
206:in `main_loop' /opt/ruby-enterprise-1.8.6-20090201/lib/ruby/gems/1.8/gems/ passenger-2.2.4/lib/phusion_passenger/railz/application_spawner.rb: 376:in`start\_request\_handler’  
/opt/ruby-enterprise-1.8.6-20090201/lib/ruby/gems/1.8/gems/  
passenger-2.2.4/lib/phusion\_passenger/railz/application\_spawner.rb:  
334:in `handle_spawn_application' /opt/ruby-enterprise-1.8.6-20090201/lib/ruby/gems/1.8/gems/ passenger-2.2.4/lib/phusion_passenger/utils.rb:182:in`safe\_fork’  
/opt/ruby-enterprise-1.8.6-20090201/lib/ruby/gems/1.8/gems/  
passenger-2.2.4/lib/phusion\_passenger/railz/application\_spawner.rb:  
332:in `handle_spawn_application' /opt/ruby-enterprise-1.8.6-20090201/lib/ruby/gems/1.8/gems/ passenger-2.2.4/lib/phusion_passenger/abstract_server.rb:351:in` **send** ’  
/opt/ruby-enterprise-1.8.6-20090201/lib/ruby/gems/1.8/gems/  
passenger-2.2.4/lib/phusion\_passenger/abstract\_server.rb:351:in  
`main_loop' /opt/ruby-enterprise-1.8.6-20090201/lib/ruby/gems/1.8/gems/ passenger-2.2.4/lib/phusion_passenger/abstract_server.rb:195:in`start\_synchronously’  
/opt/ruby-enterprise-1.8.6-20090201/lib/ruby/gems/1.8/gems/  
passenger-2.2.4/lib/phusion\_passenger/abstract\_server.rb:162:in  
`start' /opt/ruby-enterprise-1.8.6-20090201/lib/ruby/gems/1.8/gems/ passenger-2.2.4/lib/phusion_passenger/railz/application_spawner.rb: 213:in`start’  
/opt/ruby-enterprise-1.8.6-20090201/lib/ruby/gems/1.8/gems/  
passenger-2.2.4/lib/phusion\_passenger/spawn\_manager.rb:261:in  
`spawn_rails_application' /opt/ruby-enterprise-1.8.6-20090201/lib/ruby/gems/1.8/gems/ passenger-2.2.4/lib/phusion_passenger/abstract_server_collection.rb: 126:in`lookup\_or\_add’  
/opt/ruby-enterprise-1.8.6-20090201/lib/ruby/gems/1.8/gems/  
passenger-2.2.4/lib/phusion\_passenger/spawn\_manager.rb:255:in  
`spawn_rails_application' /opt/ruby-enterprise-1.8.6-20090201/lib/ruby/gems/1.8/gems/ passenger-2.2.4/lib/phusion_passenger/abstract_server_collection.rb: 80:in`synchronize’  
/opt/ruby-enterprise-1.8.6-20090201/lib/ruby/gems/1.8/gems/  
passenger-2.2.4/lib/phusion\_passenger/abstract\_server\_collection.rb:  
79:in `synchronize' /opt/ruby-enterprise-1.8.6-20090201/lib/ruby/gems/1.8/gems/ passenger-2.2.4/lib/phusion_passenger/spawn_manager.rb:254:in`spawn\_rails\_application’  
/opt/ruby-enterprise-1.8.6-20090201/lib/ruby/gems/1.8/gems/  
passenger-2.2.4/lib/phusion\_passenger/spawn\_manager.rb:153:in  
`spawn_application' /opt/ruby-enterprise-1.8.6-20090201/lib/ruby/gems/1.8/gems/ passenger-2.2.4/lib/phusion_passenger/spawn_manager.rb:286:in`handle\_spawn\_application’  
/opt/ruby-enterprise-1.8.6-20090201/lib/ruby/gems/1.8/gems/  
passenger-2.2.4/lib/phusion\_passenger/abstract\_server.rb:351:in  
` __send__' /opt/ruby-enterprise-1.8.6-20090201/lib/ruby/gems/1.8/gems/ passenger-2.2.4/lib/phusion_passenger/abstract_server.rb:351:in`main\_loop’  
/opt/ruby-enterprise-1.8.6-20090201/lib/ruby/gems/1.8/gems/  
passenger-2.2.4/lib/phusion\_passenger/abstract\_server.rb:195:in  
`start\_synchronously’  
/opt/ruby-enterprise-1.8.6-20090201/lib/ruby/gems/1.8/gems/  
passenger-2.2.4/bin/passenger-spawn-server:61

---

<div class="post-metadata">

**Author:** ![casper\_the\_ghost](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/58956e/32.png) [@casper\_the\_ghost](https://www.ruby-forum.com/u/casper_the_ghost)\
**Post date:** [February 2, 2010, 7:37pm UTC](https://www.ruby-forum.com/t/failsafe-error-with-rails-2-3-4/182783/2 "2010-02-02T19:37:31Z")

</div>

On Feb 2, 6:33 pm, TomRossi7 [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> Does anyone know what could be causing this error? I am currently  
> experiencing it when some browser submit a multipart form witha file  
> attached.

Somewhere you are trying to serialize a Proc object (looks like you’re  
trying to put one in the session).

Fred

---

<div class="post-metadata">

**Author:** ![casper\_the\_ghost](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/58956e/32.png) [@casper\_the\_ghost](https://www.ruby-forum.com/u/casper_the_ghost)\
**Post date:** [February 2, 2010, 8:37pm UTC](https://www.ruby-forum.com/t/failsafe-error-with-rails-2-3-4/182783/3 "2010-02-02T20:37:14Z")

</div>

Interesting! I’ve found the problem, but not the fix. I was store my  
ActiveRecord errors in the flash as shown below:

flash.now[:errors]= @object.errors

This apparently causes problems when you are using PaperClip and there  
is a  
validation issue. It may be trying to put the file in the ActiveRecord  
Errors object.

I’m just going to have to change how I do my flash error messages…

Thanks!  
Tom

On Tue, Feb 2, 2010 at 1:36 PM, Frederick C.  
\<removed\_email\_address@domain.invalid
