Hi,
I’m having a big problem with stoped uploads killing my app.
I simply have a restfull controller and as follows, my view and models
are:
View new.html.erb:
New Image
<%= error_messages_for :image %> <% form_for(:image, :url => collection_url, :html => {:multipart => true}) do |f| %>
<%= label :image, :name, "Name", :class => "aligned" %>
<%= f.text_field :name %>
<%= label :image, :file_data, "Localização" , :class => "aligned"%>
Maximum Size: 2.5MB / Only: GIF or JPG
<%= file_column_field "image", "file_data" %>
Model image.erb:
class Image < ActiveRecord::Base
belongs_to :image, :polymorphic => true
validates_presence_of :file_data
validates_file_format_of :file_data, :in => [“gif”, “jpg”]
validates_filesize_of :file_data, :in => 1.kilobytes…3000.kilobytes
file_column :file_data, :magick => {:geometry => “640x480>”,
:versions => { “thumb” => “80x”, “medium” => “180x” }}
end
I’m using file_column plugin as you can see.
Deploying this on my server in production I get the following error
when some user cancels the upload:
Processing ImagesController#new (for ------ at 2008-06-30 03:19:52)
[GET]
Session ID: ----
Parameters: {“catalog_id”=>“1”, “action”=>“new”,
“catalog_item_id”=>“65”, “controller”=>“superuser/images”}
Rendering template within layouts/application
Rendering images/new
Completed in 0.17773 (5 reqs/sec) | Rendering: 0.17347 (97%) | DB:
0.00000 (0%) | 200 OK [http://my_server/images/new]
/!\ FAILSAFE /!\ Mon Jun 30 04:21:51 -0700 2008
Status: 500 Internal Server Error
bad content body
/usr/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/request.rb:548:in
read_multipart' /usr/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/request.rb:517:inloop’
/usr/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/request.rb:517:in
read_multipart' /usr/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/request.rb:445:inparse_multipart_form_parameters’
/usr/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/request.rb:383:in
parse_formatted_request_parameters' /usr/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/cgi_process.rb:78:inrequest_parameters’
/usr/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/request.rb:287:in
parameters' /usr/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/request.rb:22:inrequest_method’
/usr/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/request.rb:35:in
method' /usr/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/routing.rb:1483:inextract_request_environment’
/usr/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/routing.rb:1424:in
recognize' /usr/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/dispatcher.rb:170:inhandle_request’
/usr/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/dispatcher.rb:115:in
dispatch' /usr/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/dispatcher.rb:126:indispatch_cgi’
/usr/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/dispatcher.rb:9:in
dispatch' /usr/lib/ruby/gems/1.8/gems/passenger-1.0.5/lib/passenger/request_handler.rb:304:inprocess_request’
/usr/lib/ruby/gems/1.8/gems/passenger-1.0.5/lib/passenger/request_handler.rb:180:in
main_loop' /usr/lib/ruby/gems/1.8/gems/passenger-1.0.5/lib/passenger/application_spawner.rb:320:instart_request_handler’
/usr/lib/ruby/gems/1.8/gems/passenger-1.0.5/lib/passenger/application_spawner.rb:282:in
handle_spawn_application' /usr/lib/ruby/gems/1.8/gems/passenger-1.0.5/lib/passenger/application_spawner.rb:280:infork’
/usr/lib/ruby/gems/1.8/gems/passenger-1.0.5/lib/passenger/application_spawner.rb:280:in
handle_spawn_application' /usr/lib/ruby/gems/1.8/gems/passenger-1.0.5/lib/passenger/application_spawner.rb:278:infork’
…
After this apache is flooded by the process and freezes.
Anyone as been trough this or knows if this may be a bug on the
framework?
Perhaps some weird problem between apache and passenger
apache version is: Apache/2.2.3
passenger: 1.9