General discussion about Chef

Chef-server with passenger timing out


Chronological Thread 
  • From: Albert Llop <mrsimo@gmail.com>
  • To: chef@lists.opscode.com
  • Subject: Chef-server with passenger timing out
  • Date: Tue, 9 Jun 2009 12:34:16 +0200
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=XNNP6hwpVklHYPayyFnF/2r/iiyfNpGl/KDV2sC5t97vAiWWwuZARIpcL1HOUjTmDz VxZE9xO/RTQR7DOFLSRfhjwjPu4m9syxCEh2qEXj/bBgqDAu88MsAUwuV23mJFmjhovi Mr0CbTkucWr2HgtfC8PKJ0lx7Y4pjRYSfYzOA=
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

Archive powered by MHonArc 2.6.16.

§