[Mongrel] 503 Errors While Cluster Is Still Active

Joey Geiger jgeiger at gmail.com
Fri Jul 6 18:39:14 EDT 2007

I get that when I start up apache and there isn't a mongrel available to answer.

I think in your case it may be that all your mongrels are busy, and
it's letting you know that.  You might need to add more mongrel
processes to see if it helps, but that may be an issue if you're only
running on a VPS with 64MB.... Mongrel w/rails starts at 32mb and
grows for me, so it seems you could have 2 running before you get into
performance issues...

On 7/6/07, Justin Williams <carpeaqua at gmail.com> wrote:
> I've setup a new mongrel cluster on my VPS, and am noticing a lot if
> 503 errors if I try to hit the server too many times in succession in
> a few seconds.  I've read that this is usually caused by the cluster
> crashing, but I haven't been seen the cluster crash when I do this.
> Does anyone have any other ideas what might cause this?  I have my
> server configured how MediaTemple suggested
> (http://kb.mediatemple.net/article.php?id=279).  It just seems like
> Apache isn't able to always see the cluster.
> Thanks for your help.
> -
> Justin Williams
> Owner, Second Gear
> http://www.secondgearllc.com/
> _______________________________________________
> Mongrel-users mailing list
> Mongrel-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users

More information about the Mongrel-users mailing list