I am also seeing "Errno::EPIPE in Passenger" with:
Passenger 2.2.4
REE 1.8.6-20090610
Rails 2.3.2
Apache 2.2.11
The errors show up frequently in the apache error_log (as opposed to
the apache-error_log files defined in the VirtualHosts) and look like
this:
*** Exception Errno::EPIPE in Passenger RequestHandler (Broken pipe)
(process 17635):
from /opt/local/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/
1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/request_handler.rb:
108:in `write'
from /opt/local/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/
1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/request_handler.rb:
108:in `process_request'
from /opt/local/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/
1.8/gems/actionpack-2.3.2/lib/action_controller/response.rb:155:in
`each_line'
from /opt/local/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/
1.8/gems/actionpack-2.3.2/lib/action_controller/response.rb:155:in
`each'
from /opt/local/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/
1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/request_handler.rb:
107:in `process_request'
from /opt/local/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/
1.8/gems/passenger-2.2.4/lib/phusion_passenger/
abstract_request_handler.rb:206:in `main_loop'
from /opt/local/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/
1.8/gems/passenger-2.2.4/lib/phusion_passenger/railz/
application_spawner.rb:376:in `start_request_h
andler'
from /opt/local/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/
1.8/gems/passenger-2.2.4/lib/phusion_passenger/railz/
application_spawner.rb:334:in `handle_spawn_ap
plication'
from /opt/local/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/
1.8/gems/passenger-2.2.4/lib/phusion_passenger/utils.rb:182:in
`safe_fork'
from /opt/local/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/
1.8/gems/passenger-2.2.4/lib/phusion_passenger/railz/
application_spawner.rb:332:in `handle_spawn_ap
plication'
from /opt/local/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/
1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstract_server.rb:
351:in `__send__'
from /opt/local/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/
1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstract_server.rb:
351:in `main_loop'
from /opt/local/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/
1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstract_server.rb:
195:in `start_synchronously'
from /opt/local/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/
1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstract_server.rb:
162:in `start'
from /opt/local/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/
1.8/gems/passenger-2.2.4/lib/phusion_passenger/railz/
application_spawner.rb:213:in `start'
from /opt/local/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/
1.8/gems/passenger-2.2.4/lib/phusion_passenger/spawn_manager.rb:261:in
`spawn_rails_application'
from /opt/local/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/
1.8/gems/passenger-2.2.4/lib/phusion_passenger/
abstract_server_collection.rb:126:in `lookup_or_add'
from /opt/local/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/
1.8/gems/passenger-2.2.4/lib/phusion_passenger/spawn_manager.rb:255:in
`spawn_rails_application'
from /opt/local/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/
1.8/gems/passenger-2.2.4/lib/phusion_passenger/
abstract_server_collection.rb:80:in `synchronize'
from /opt/local/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/
1.8/gems/passenger-2.2.4/lib/phusion_passenger/
abstract_server_collection.rb:79:in `synchronize'
from /opt/local/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/
1.8/gems/passenger-2.2.4/lib/phusion_passenger/spawn_manager.rb:254:in
`spawn_rails_application'
from /opt/local/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/
1.8/gems/passenger-2.2.4/lib/phusion_passenger/spawn_manager.rb:153:in
`spawn_application'
from /opt/local/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/
1.8/gems/passenger-2.2.4/lib/phusion_passenger/spawn_manager.rb:286:in
`handle_spawn_application'
from /opt/local/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/
1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstract_server.rb:
351:in `__send__'
from /opt/local/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/
1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstract_server.rb:
351:in `main_loop'
from /opt/local/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/
1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstract_server.rb:
195:in `start_synchronously'
from /opt/local/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/
1.8/gems/passenger-2.2.4/bin/passenger-spawn-server:61
This entry is often, but not always, proceeded or proceeds an entry
that looks like this:
[ pid=8401 file=ext/apache2/Hooks.cpp:621 time=2009-07-15
12:34:57.287 ]:
Apache stopped forwarding the backend's response, even though the
HTTP client did not close the connection. Is this an Apache bug?
And it appears that the latter error always corresponds to a file
being sent to the client by mod_xsendfile after being located within a
rails controller (using the x_sendfile option of the send_file
method).
From what I have seen so far, there is no adverse behavior experienced
by the client corresponding to these error log entries. The files are
always sent as expected, no rails related UX problems have been
reported, and since switching from Apache 2.0.52 to Apache 2.2.11 the
expected http status codes sent by mod_xsendfile are being received by
the clients.
The only real problem noticed so far is really big error_log files
with a low signal to noise ratio.
- Jonn
On Jul 4, 4:58 am, millisami <
millis...@gmail.com> wrote:
> Hi Guys,
> Upgraded to Rails 2.3.2 and Passenger 2.2.4 on Ubuntu hardy slice at
> slicehost with Apache2
>
> I'm getting this same above discussed error in my Apache error.log of
> system /var/logs/apache2/
> ...