For additional information, some users are randomly just suddenly getting wild with their proccess.
So the CPU load will follows until 40-50 (and that makes LSWS automatically restart with fix 503 error reason)
I found those brutal process on CSF reports.
Here is one for an example :
Code:
Time: Tue Apr 28 15:00:58 2009 +0700
Account: waroacom
Process Count: 21 (Killed)
Process Information:
User:waroacom PID:25158 Run Time:11(secs) Memory:233788(kb) exe:/usr/local/lsws/fcgi-bin/lsphp-5.2.9 cmd:lsphp5
User:waroacom PID:25195 Run Time:9(secs) Memory:233788(kb) exe:/usr/local/lsws/fcgi-bin/lsphp-5.2.9 cmd:lsphp5
User:waroacom PID:25203 Run Time:9(secs) Memory:233788(kb) exe:/usr/local/lsws/fcgi-bin/lsphp-5.2.9 cmd:lsphp5
User:waroacom PID:25204 Run Time:9(secs) Memory:233788(kb) exe:/usr/local/lsws/fcgi-bin/lsphp-5.2.9 cmd:lsphp5
User:waroacom PID:25232 Run Time:6(secs) Memory:233788(kb) exe:/usr/local/lsws/fcgi-bin/lsphp-5.2.9 cmd:lsphp5
User:waroacom PID:25244 Run Time:5(secs) Memory:233788(kb) exe:/usr/local/lsws/fcgi-bin/lsphp-5.2.9 cmd:lsphp5
User:waroacom PID:25245 Run Time:5(secs) Memory:233788(kb) exe:/usr/local/lsws/fcgi-bin/lsphp-5.2.9 cmd:lsphp5
User:waroacom PID:25246 Run Time:5(secs) Memory:233788(kb) exe:/usr/local/lsws/fcgi-bin/lsphp-5.2.9 cmd:lsphp5
User:waroacom PID:25253 Run Time:4(secs) Memory:233788(kb) exe:/usr/local/lsws/fcgi-bin/lsphp-5.2.9 cmd:lsphp5
User:waroacom PID:25262 Run Time:4(secs) Memory:233788(kb) exe:/usr/local/lsws/fcgi-bin/lsphp-5.2.9 cmd:lsphp5
User:waroacom PID:25269 Run Time:3(secs) Memory:233788(kb) exe:/usr/local/lsws/fcgi-bin/lsphp-5.2.9 cmd:lsphp5
User:waroacom PID:25276 Run Time:3(secs) Memory:233788(kb) exe:/usr/local/lsws/fcgi-bin/lsphp-5.2.9 cmd:lsphp5
User:waroacom PID:25282 Run Time:3(secs) Memory:233788(kb) exe:/usr/local/lsws/fcgi-bin/lsphp-5.2.9 cmd:lsphp5
User:waroacom PID:25284 Run Time:3(secs) Memory:233788(kb) exe:/usr/local/lsws/fcgi-bin/lsphp-5.2.9 cmd:lsphp5
User:waroacom PID:25287 Run Time:3(secs) Memory:233788(kb) exe:/usr/local/lsws/fcgi-bin/lsphp-5.2.9 cmd:lsphp5
User:waroacom PID:25288 Run Time:2(secs) Memory:233788(kb) exe:/usr/local/lsws/fcgi-bin/lsphp-5.2.9 cmd:lsphp5
User:waroacom PID:25291 Run Time:2(secs) Memory:233788(kb) exe:/usr/local/lsws/fcgi-bin/lsphp-5.2.9 cmd:lsphp5
User:waroacom PID:25293 Run Time:2(secs) Memory:233788(kb) exe:/usr/local/lsws/fcgi-bin/lsphp-5.2.9 cmd:lsphp5
User:waroacom PID:25312 Run Time:0(secs) Memory:233788(kb) exe:/usr/local/lsws/fcgi-bin/lsphp-5.2.9 cmd:lsphp5
User:waroacom PID:25315 Run Time:0(secs) Memory:233788(kb) exe:/usr/local/lsws/fcgi-bin/lsphp-5.2.9 cmd:lsphp5
User:waroacom PID:25316 Run Time:0(secs) Memory:174220(kb) exe:/usr/local/lsws/fcgi-bin/lsphp-5.2.9 cmd:lsphp5
They are many killing process reports at a time from CSF while my CPU scream.
But that wild process has not happen while using mod_suphp...
It is so confusing...
Btw, my php info page -->
www.dracoola.com/hph.php