Well Cherokee is really throwing 503's today... I updated us to the latest trunk from Saturday and it seems worse - unsure if related to fixes or just traffic use on our end.
Noticing one thing about Cherokee when the 503s happen and eventually Cherokee stays stuck serving the 503's - that is actual memory use is around 71MB. I am going to turn IOCACHE off and reduce some of the high memory use stuff for static elements and see that helps. I suspect it won't, but that's all we do that is not typical of Cherokee install. Would like to get this 503 issue resolved or work on a temporary fix to stop/reduce it. On Fri, Sep 4, 2009 at 4:00 AM, Alvaro Lopez Ortega<[email protected]> wrote: > On 04-sep-09, at 01:04, Stefan de Konink wrote: > >>> NOTICE: Sources exhausted: re-enabling one. >>> NOTICE: Taking source='172.24.96.243:8500' back on-line >>> NOTICE: Taking source='192.168.13.243:8500' back on-line >> >> So try to find out why all your information sources are exhausted... > > > Cherokee reports that information source poll is exhausted when all of them > are off-line. Most probably they are off-line because it couldn't connect > to them (back-end server overload maybe?). > > Paul, you are the second person who describes a similar issue with the > reverse proxy, so there must be some sort of issue. Just to be sure, it > happens after some time running alright, doesn't it? > > -- > Octality > http://www.octality.com/ > > _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
