Wanting to help track this bug down since we are being impacted. Is spawning Cherokee like this adequate to get debugging and isolate at failure part? cherokee -C /etc/cherokee/cherokee.conf
Thanks! On Thu, Feb 10, 2011 at 7:34 AM, Alvaro Lopez Ortega <[email protected]> wrote: > On 09/02/2011, at 22:38, pub crawler wrote: > >> Running the latest trunk release. >> >> Over the past three or so days we have had at least one incident per >> day where Cherokee stops running. >> >> The Cherokee server process is gone, unloaded. The Admin process >> however is fine and in place and we restart Cherokee via such and are >> back up and running. >> >> Clearly, something is wrong in Cherokee *I think* as the server is >> under no real load and has ample spare resources. >> >> What's the recommended protocol to enable debugging and help to track >> this bug down? > > It might be related to bug #970: > > http://code.google.com/p/cherokee/issues/detail?id=970 > > Let's see what we can do to fix it up ASAP. > > -- > Octality > http://www.octality.com/ > > _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
