I've some problems with tcpsndbuf on my Virtual Host.
http://i.stack.imgur.com/47lNe.png
While tcpsndbuf is in the yellow Zone, the whole Server is nearly down. I can't acces to ssh or MySQL or anything else.
After a few minutes everything is working normal again.
tcpsndbuf current (in green zone): 887,760
Softlimit: 7,116,560
Hardlimit: 8,536,480
My Page has about 300 users each day so nothing special.
I'm running Passenger and Rails 3.0. and I tried Passenger 3.0.7, 3.0.8 and 2.2.15. I already Updated Apache2 to 2.2.16. I'm using Debian Lenny.
Here are some lines from /apache/error.log
[ pid=30503 file=ext/apache2/Hooks.cpp:676 time=2011-08-16 15:40:27.108 ]:
Either the vistor clicked on the 'Stop' button in the web browser, or the visitor's connection has stalled and couldn't receive the data that Apache is sending to it. As a result, you will probably see a 'Broken Pipe' error in this log file. Please ignore it, this is normal. You might also want to increase Apache's TimeOut configuration option if you experience this problem often.
[ pid=30503 file=ext/apache2/Hooks.cpp:676 time=2011-08-16 15:40:31.127 ]:
Either the vistor clicked on the 'Stop' button in the web browser, or the visitor's connection has stalled and couldn't receive the data that Apache is sending to it. As a result, you will probably see a 'Broken Pipe' error in this log file. Please ignore it, this is normal. You might also want to increase Apache's TimeOut configuration option if you experience this problem often.
[ pid=30503 file=ext/apache2/Hooks.cpp:676 time=2011-08-16 15:40:32.361 ]:
Either the vistor clicked on the 'Stop' button in the web browser, or the visitor's connection has stalled and couldn't receive the data that Apache is sending to it. As a result, you will probably see a 'Broken Pipe' error in this log file. Please ignore it, this is normal. You might also want to increase Apache's TimeOut configuration option if you experience this problem often.
[ pid=30503 file=ext/apache2/Hooks.cpp:676 time=2011-08-16 15:40:34.695 ]:
Either the vistor clicked on the 'Stop' button in the web browser, or the visitor's connection has stalled and couldn't receive the data that Apache is sending to it. As a result, you will probably see a 'Broken Pipe' error in this log file. Please ignore it, this is normal. You might also want to increase Apache's TimeOut configuration option if you experience this problem often.
[ pid=30503 file=ext/apache2/Hooks.cpp:676 time=2011-08-16 15:42:24.305 ]:
Either the vistor clicked on the 'Stop' button in the web browser, or the visitor's connection has stalled and couldn't receive the data that Apache is sending to it. As a result, you will probably see a 'Broken Pipe' error in this log file. Please ignore it, this is normal. You might also want to increase Apache's TimeOut configuration option if you experience this problem often.
[ pid=30623 file=ext/apache2/Hooks.cpp:676 time=2011-08-16 15:42:49.683 ]:
Either the vistor clicked on the 'Stop' button in the web browser, or the visitor's connection has stalled and couldn't receive the data that Apache is sending to it. As a result, you will probably see a 'Broken Pipe' error in this log file. Please ignore it, this is normal. You might also want to increase Apache's TimeOut configuration option if you experience this problem often.
[ pid=30503 file=ext/apache2/Hooks.cpp:676 time=2011-08-16 15:42:50.257 ]:
Either the vistor clicked on the 'Stop' button in the web browser, or the visitor's connection has stalled and couldn't receive the data that Apache is sending to it. As a result, you will probably see a 'Broken Pipe' error in this log file. Please ignore it, this is normal. You might also want to increase Apache's TimeOut configuration option if you experience this problem often.
Tue Aug 16 15:43:34 2011] [warn] child process 30503 still did not exit, sending a SIGTERM
[Tue Aug 16 15:43:34 2011] [warn] child process 30623 still did not exit, sending a SIGTERM
[Tue Aug 16 15:43:36 2011] [warn] child process 30503 still did not exit, sending a SIGTERM
[Tue Aug 16 15:43:36 2011] [warn] child process 30623 still did not exit, sending a SIGTERM
[Tue Aug 16 15:43:38 2011] [warn] child process 30503 still did not exit, sending a SIGTERM
[Tue Aug 16 15:43:38 2011] [warn] child process 30623 still did not exit, sending a SIGTERM
[Tue Aug 16 15:43:40 2011] [error] child process 30503 still did not exit, sending a SIGKILL
[Tue Aug 16 15:43:40 2011] [error] child process 30623 still did not exit, sending a SIGKILL
[Tue Aug 16 15:43:41 2011] [notice] caught SIGTERM, shutting down
And Finaly:
*** Exception Errno::EPIPE in Passenger RequestHandler (Broken pipe) (process 26478):
from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/rack/request_handler.rb:94:in `write'
from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/rack/request_handler.rb:94:in `process_request'
from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/abstract_request_handler.rb:207:in `main_loop'
from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/rack/application_spawner.rb:120:in `run'
from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/rack/application_spawner.rb:65:in `spawn_application'
from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/utils.rb:252:in `safe_fork'
from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/rack/application_spawner.rb:58:in `spawn_application'
from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/rack/application_spawner.rb:41:in `spawn_application'
from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/spawn_manager.rb:150:in `spawn_application'
from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/spawn_manager.rb:278:in `handle_spawn_application'
from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/abstract_server.rb:352:in `__send__'
from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/abstract_server.rb:352:in `main_loop'
from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/abstract_server.rb:196:in `start_synchronously'
from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/bin/passenger-spawn-server:61
*** Exception Errno::EPIPE in Passenger RequestHandler (Broken pipe) (process 24397):
from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/rack/request_handler.rb:94:in `write'
from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/rack/request_handler.rb:94:in `process_request'
from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/abstract_request_handler.rb:207:in `main_loop'
from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/rack/application_spawner.rb:120:in `run'
from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/rack/application_spawner.rb:65:in `spawn_application'
from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/utils.rb:252:in `safe_fork'
from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/rack/application_spawner.rb:58:in `spawn_application'
from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/rack/application_spawner.rb:41:in `spawn_application'
from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/spawn_manager.rb:150:in `spawn_application'
from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/spawn_manager.rb:278:in `handle_spawn_application'
from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/abstract_server.rb:352:in `__send__'
from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/abstract_server.rb:352:in `main_loop'
from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/abstract_server.rb:196:in `start_synchronously'
from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/bin/passenger-spawn-server:61
Is this an Passenger Bug?
Anyone got an idea how to fix this?
Thanks
