# Stopped Upload kills my Apache/Passenger app

**URL:** <https://www.ruby-forum.com/t/stopped-upload-kills-my-apache-passenger-app/141787>\
**Category:** Rails\
**Created:** [June 30, 2008, 4:26pm UTC](https://www.ruby-forum.com/t/stopped-upload-kills-my-apache-passenger-app/141787 "2008-06-30T16:26:23Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![vulpesfurvus](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/v/c6cbf5/32.png) [@vulpesfurvus](https://www.ruby-forum.com/u/vulpesfurvus)\
**Post date:** [June 30, 2008, 4:26pm UTC](https://www.ruby-forum.com/t/stopped-upload-kills-my-apache-passenger-app/141787/1 "2008-06-30T16:26:23Z")

</div>

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" %\>

 \<%= submit\_tag "Save", :class =\> "button" %\> \<% end %\> \<%= cancel %\>

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:in`loop’  
/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:in`parse\_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:in`request\_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:in`request\_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:in`extract\_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:in`handle\_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:in`dispatch\_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:in`process\_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:in`start\_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:in`fork’  
/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:in`fork’  
…

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

---

<div class="post-metadata">

**Author:** ![vulpesfurvus](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/v/c6cbf5/32.png) [@vulpesfurvus](https://www.ruby-forum.com/u/vulpesfurvus)\
**Post date:** [August 27, 2008, 1:16am UTC](https://www.ruby-forum.com/t/stopped-upload-kills-my-apache-passenger-app/141787/2 "2008-08-27T01:16:28Z")

</div>

On Jun 30, 4:26 pm, Vulpes F. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)  
wrote:

> ```
> /usr/lib/ruby/gems/1.8/gems/passenger-1.0.5/lib/passenger/application_spawner.rb:278:in
> 
> ```
> 
> `fork’

Your backtrace indicates that you’re running on Phusion Passenger  
1.0.5, not 1.9.

Please upgrade to 2.0.3. It fixes many, many problems.