Re: Chef-server with passenger timing out

[Albert Llop <mrsimo@gmail.com>]

We finally upgraded the slice to a bigger one, and now there can be two instances of chef on easily. I still don't know how to solve this "properly" besides having spare resources, since the only thing you can configure in passenger is the amount of total instances that it can have, nothing specific per-app.

Thanks anyway =)

2009/6/9 Adam Jacob <adam@opscode.com>

I imagine there must be a passenger tunable that fixes this?

Sent from my iPhone

On Jun 9, 2009, at 3:34 AM, Albert Llop <mrsimo@gmail.com> wrote:

Hi again (this is the second question),

we have the chef-server installed in a simple slicehost account (typical 256mb), with another rails application.  We're serving both through nginx+passenger, but there's a problem with that. Passenger does some ninja stuff to manage resources and keeps starting and stopping instances at his will. That's usually OK, but for chef-server you need two instances for the openid stuff, and I have no idea how to do that. If I restart nginx so that there's no application on, chef-server seems to work, since passenger allows it to have two instances (but even then, only sometimes), but if the other rails application is on, passenger won't give more than one instance to chef-server, and my client requests just don't work.

Any suggestion on this?

--
Albert Llop

-- 
Albert Llop