On 07/18/2015 03:20 AM, Tim Dunphy wrote: > Hey Felix, > > thanks, but those aren't the important ones I'm afraid. There > should be > a vhost to bind port 8140. If there is not, please check carefully > which > process is actually listening on that port. (If it's Ruby, I have bad > news and good news :-) > > > Whoops! OK I get you now. Here's the vhost that binds to 8140:
Yep, that's the one. OK, so you manage that via puppetlabs-apache. Guess you will have to ultimately fix this in your manifest/data then. The default template for the passenger vhost includes settings PassengerHighPerformance on and PassengerPoolSize X Make sure that both are present in your Apache config, and that the latter is set to a sufficiently high value. Allow Apache to fork off enough Ruby workers to handle your load. I suppose your hardware can run a few dozen processes. HTH, Felix -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/55A9B2DC.7070102%40Alumni.TU-Berlin.de. For more options, visit https://groups.google.com/d/optout.
