up vote 2 down vote favorite
1
share [g+] share [fb]

I have an Nginx and Passenger setup that is proving problematic.

At relatively low loads the server seems to get backed up and start churning results like this into the error.log:

connect() to unix:/passenger_helper_server failed 
(11: Resource temporarily unavailable) while connecting to upstream

My passenger setup is:

passenger_min_instances 2;
passenger_pool_idle_time 1200;
passenger_max_pool_size 20;

I have done some digging, and it looks like the CPU gets pegged. Memory usage seems fine passenger_memory_stats shows at most about 700MB being used, but CPU approaches 100%.

is this enough to cause this type of error?

Should i bring the pool size down? Are there other configuration settings I should be looking at?

Any help appreciated

Other pertinent information:

  • Amazon EC2 Small Instance
  • Ubuntu 10.10
  • Nginx (latest stable)
  • Passenger (latest stable)
  • Rails 3.0.4
link|improve this question
Hi, I've exactly the same problem, with some traffic I got that error I'm googling around and here there is a guy with that problem, nginx+php: devcomments.com/… My config: nginx/0.6.35 + Phusion Passenger 2.2.10 passenger_max_pool_size 6; passenger_pool_idle_time 3600; Please let me know if you find a solution, I'll do the same. Thank you – user72939 Mar 3 '11 at 13:16
Same problem here. Did you ever find a solution? – Hates_ Aug 9 '11 at 9:57
Never did find the answer, but decreasing the passenger pool helped immensely. – Toby Hede Aug 11 '11 at 10:58
feedback

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
or
required, but never shown
discard

Browse other questions tagged or ask your own question.