Search results

this is an issue for apc, not litespeed. try set apc.filters to reduce number of cached php scripts. or run multiple PHPs(http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:multiple_phps_in_control_panel_lsws), apply apc for some busy sites only.

there are 2 kinds of rewrite rules: per directory and per server. the one you post is per server rule. in .htaccess, should use per directory. in this case, please try following: RewriteEngine On RewriteCond %{ORG_REQ_URI} ^/data/ RewriteRule ^data/(.*) - [R=403,F]

my local tests shows <?php header("X-LiteSpeed-Location: /HOT_GAME.jar"); ?> works. will prompt you to down t.php accessing domain.com/t.php is same to access domain.com/HOT_GAME.jar directly. my tests also shows header("Content-type: application/java-archive"); will be ignored...

according to http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed:wiki:feature:internal_redirect, should be <?php header("X-LiteSpeed-Location: /HOT_GAME.jar"); ?>

looks like having been improved by looking at the graph. one busy site still have the problem(WaitQ=498). try to enable anti-ddos feature, see if can resolve the issue. especially Server --> Security --> Per Client Throttling --> Dynamic Requests/second, tune it to 5,10,... to see if any...

I noticed "Http Out: 103,030KB", this already reach or over the 1G bps NIC's capability. maybe a good example though: the bottle neck is at NIC, not litespeed or others.

then how do you know the IP is from which country ?

per the link you provided, CF-IPCountry is a request header. RewriteCond %{HTTP:CP-IPCountry} ^(CN|RU|IN)$ RewriteRule .* - [F,L]

try:modify /usr/local/lsws/admin/html/utility/build_php/buildconf.inc.php define ('LSAPI_VERSION', '6.0'); to define ('LSAPI_VERSION', '5.5');

no. you can upgrade at command line: /usr/local/lsws/admin/misc/lsup.sh -v 4.2

so when slow down, capture the screen shot of real-time stats and paste here. it provides many useful info there. most likely can identify where the bottle-neck is.

you have 28 (32 ?) CPU and normal load is 28, now only 25% - 50% load, so not high, there is still room for higher traffic, for example, 2M visits.

if only a few busy vhosts need separate php.ini, you can define multiple PHPs, (refer http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:multiple_phps_in_control_panel_lsws)echo with fixed php.ini, to work around it.

so: 1.the output of which is correct. since $PATH is empty 2.the output of "env", no PATH, this also show that $PATH is empty 3.why $PATH is empty, need further investigate. 4. in exterl app lsphp5's definition, add PATH=/usr/local/bin:/bin:/usr/bin to Environment, the output is what...

not sure why yet, but following tests may inspire others: <?php echo "<pre>"; out("echo \$PATH"); out("echo $PATH"); out("PATH=/usr/local/bin:/bin:/usr/bin /usr/bin/which ls"); out("/usr/bin/which ls"); out("id"); out("alias"); out("env"); echo "</pre>"; function out($cmd) { $out...

yes. if you cache 2 minutes, then guest user may not read updated page in recent 2 minutes. usually it's acceptable.

it may still relate to lve. see if you can disable lve for a while and see if PHP_INI_SCAN_DIR works

are you using cagefs at the same time?

tested with root, also tested with nobody access it through browser, it runs under lsphp5 user -- nobody. you can add out("id"); to confirm it.

OK. please PM. can monitor it for 1 or 2 days.