Good day everyone! Still wrestling with ulimit values causing Cherokee to 503 error crash.
Our solution has been to set ulimit for open files higher - to 9000 to be exact. That has worked for a few weeks. However, we were smacked by the 503 error again today. What happened is simple, I turned Keep Alive back on and ulimit for open files was 1024. Unsure why ulimit was set to 1024 again. So open file resources were eventually exhausted, never released and Cherokee kept sending a 503. We long term need to build intelligence into Cherokee to prune open kept alive connections when such a resource contention exists. For now, I need input on a workaround so we never get 503'd by this again. Here's what I propose: We use cherokee-admin to run and restart Cherokee fairly often. We try to avoid manually running Cherokee unless we really have to for some reason like testing a specific release. Is there a way to append to logic to the LAUNCH handler on the main admin screen? When I click launch I want Cherokee to go ahead and step up the ulimit as insurance that the environment it is running in has same limits every time. Anyone have any ideas about this or better way to accomplish this? Thanks! -Paul _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
