After doing some tests, it appears that there is NOT several processes. We have been misguided by the "htop" utility which shows the threads as well as the processes. I just posted a new screenshot showing this : http://thibauld.com/cherokee_processes.png
Proof is that, if I use the traditionnal "ps aux" command, I can only see 1 cherokee-worker process. Thibauld 2010/2/26 Thibauld Favre <[email protected]>: > David, your solution is a good workaround but I'd like to avoid it of > course. I'm not using "god" but "monit" as a watchdog and I will > definitely consider doing something like that if we cannot find > another solution. > > Stefan, you're totally right! I thought it was normal to have several > cherokee-worker running (I remember having around 3 or 4 running in > parallel). Right now my server only has 1 cherokee-worker running and > load is fine. I will now check the correlation between high cpu usage > and the number of cherokee-worker running but I guess it is the root > cause of my problem. > > From what I remember, I never restarted cherokee other than using the > cherokee-admin interface where I performed several "graceful restart" > following a configuration change. > > If you want me to perform some test to try to isolate the issue, just > let me know! > Thanks a lot! > > Thibauld > > 2010/2/26 Alvaro Lopez Ortega <[email protected]>: >> On 26/02/2010, at 06:27, Stefan de Konink wrote: >>> Op 25-02-10 07:59, Thibauld Favre schreef: >>>> And the 100% cpu usage is really due to cherokee without any reasons >>>> (same traffic load) : http://thibauld.com/cherokee_wild3.png >>> >>> That lost photo shows you something you should be interested in in the >>> first place. You see multiple cherokee-workers. Aka that mean that >>> cherokee was multiple times restarted gracefully and still seem to have >>> clients of some sort. >>> >>> This 'restart load goes up problem' is there already for sometime. >> >> That's a really good point. There should be only one cherokee-worker process. >> >> Actually, there were two consecutive PIDs (5901 and 5902) on that screenshot >> which, I bet, is related to the underneath issue. I'm not even sure how that >> happened, it could be either a CGI execution issue, or a SIGHUP boost where >> the workers did not die for an unknown reason. >> >> -- >> Octality >> http://www.octality.com/ >> >> _______________________________________________ >> Cherokee mailing list >> [email protected] >> http://lists.octality.com/listinfo/cherokee >> > > > > -- > CEO Allmyapps - http://allmyapps.com > @thibauld - http://twitter.com/thibauld > cell: +33 (0)6 16 75 27 07 > -- CEO Allmyapps - http://allmyapps.com @thibauld - http://twitter.com/thibauld cell: +33 (0)6 16 75 27 07 _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
