>
> 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 conf
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 b
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 vhos
On 07/17/2015 10:37 PM, Tim Dunphy wrote:
>
> Hi Felix,
>
> Thanks for getting back to me! And yes, you are correct.
> Puppet/Foreman is running through apache/passenger.
>
> And here's the vhost configurations. There's two of them, one for ssl
> and one for non ssl. Non ssl is first:
>
Hi Tim,
Hi Felix,
Thanks for getting back to me! And yes, you are correct. Puppet/Foreman is
running through apache/passenger.
And here's the vhost configurations. There's two of them, one for ssl and
one for non ssl. Non ssl is first:
#
Hi,
I'm not very familiar with the puppet/foreman stack, so this might be a
silly question, but how is the master set up? Is it running through
Apache/Passenger?
In that case, can we see the Apache vhost configuration?
Thanks,
Felix
On 07/15/2015 05:12 AM, Tim Dunphy wrote:
> Hey all,
>
> I'm
