Search results

not quite understand your question... but I think apc_clear_cache('user') caused 503 error. to avoid this 503, may need modify the code? for example, before call apc_clear_cache('user'), first check if it exists?

in your example, there are 8 groups of lsphp5, lsphp5 in one group share 1 APC cache. for example, lsphp5 pid=31153,776,1944,31744 are in one group. the parent process is 31153, the rest are child processes and share APC cache created by 31153. but share cache between groups of lsphp5 is not...

please give output pstree -p|egrep "ls|lite"

disable suExec should have better performance. But in shared hosting suExec have to be enabled.

not working because of PHP suExec enabled. disable suExec if you can, then php processes share once copy of APC cache.

echo umask() while echo get_current_user()

try yum install perl-Digest-SHA1.i386 not sure it'll help or not

if it's directAdmin or cPanel, then apache httpd.conf is read and parsed. please check httpd.conf, vhost, <directory ...> if AllowOverride All or AllowOverride Limit is there. can refer apache document http://httpd.apache.org/docs/2.0/mod/core.html#allowoverride

are both server level and vhost level "limit" of "Allow Override" checked?

there may be other place to block 7080. for example, the server's gateway firewall. you can also try change 7080 to a bigger number, for example 15000, see if it can be reached.

ssh to the box, how about "wget 127.0.0.1:7080"

check if there is other application already listen to port 7080

yes. this is normal. for some reason lsws restarted during your download. but wget has download resuming feature, it can continue downloading at the failure point.

in most time, should run apache or lsws only, not both. when installing lsws at first time, running lsws at an offset port say 2080 is a safest way. firstly to ensure not to break current web service. while you can check if your web sites also works well at 2080 port. once you're sure all are...

Thanks cwh. just what I want to say.

use them in parallel. now lslb is front end and lsws is backend. please refer our wiki page for some instructions: http://www.litespeedtech.com/support/wiki/doku.php#load_balancer refer "Litespeed Load Balancer With ClusterHTTP"

something must be wrong at this server. in general, eAccelerator should work. Please check the WP configuration, if any inefficient plugin(s) installed. disable one by one if you can and see if any difference.

you can install a trial version to watch 15 days before deciding purchase. apache will still be there, and you can switch between apache and litespeed by one click. You can run apache and litespeed at the same time too --- with an port offset. for example, apache listen to port 80 while...

Thanks. This may be a good reference for google search.

you may run "strace -tt -T -p <lsphp5_pid>" directly? replace <lsphp5_pid> with number, which is process id of lsphp5. "ps -ef|grep lsphp5" can get the pid.