Search results

like I stated before, once we can reproduce the issue, should be able to fix it quickly. even we have a copy of XenForo, can't guarantee we can easily reproduce the issue. for the recent example, the issue comes with the open source opencart. but finally, I found that issue only happen when...

hmm... the document is here: http://php.net/manual/en/ssh2.installation.php have you built ssh2.so and put extension=ssh2.so in php.ini ? for how to build ssh2.so for lsphp, please refer http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:php:opcode_cache it's same...

I'd recommend: use disk cache, not use shared memory, or use minimum shared memory -- 1M only. not sure if it's possible to completely disable shared memory in latest eAccelerator. per my past experience with eAccelerator, 1M is the minimum shared memory size and you have to set it. no need...

for lsws gzip, it'll compress static page only. 8G looks too much. in general, you can monitor its size by du -sh /lsgzip after running a few days so you'll know exactly how much it needs. you can create a cron job to clean this cache directory as well. regarding realtime status reports, you...

the user/group which litespeed process run as(though not the root litespeed process), by default it's nobody:nobody on centOS. you can check it by ps -ef|grep litespeed what's the purpose you use the ram disk, cache ? if 4GB is enough for your server, purely depending on the web...

no need re-install. just set it: admin console->Server->External App->lsphp5-> suEXEC User suEXEC Group then restart litespeed

ps -ef |grep lsphp to find which user run lsphp yes, you can configure litespeed to have lsphp run as which user/group.

there is a good news for this issue, but need end user's verification. in recent 2 weeks, we got a similar report which only have issue on chrome. in the end, we're able to reproduce this issue on user's website and have a fix for it quickly. the most time is spent on reproducing the...

that mean they are only 6 lsphp5 process running on the server. the process limit is to limit the number of running processes. you see, your server is quite idle, only 6 processes running, there is no difference you set set limit to 200 or 300.

> Server -> Security -> External Application Resources not exist for "ideal Process Soft Limit, and Hard Limit", default one is good for most cases. for example lsphp5, you can pstree -p|grep lsphp5 |wc to know how many lsphp5 are running on your server. you can set the limit big...

it looks lsapi 6.3 disable -c option. however if run command line, "-c option" still effective. can you confirm ?

the settings looks ok. can you PM the server's access so that I can do more tests on the server directly.

there is no difference between /tmp and /diskcache at all. if /diskcache is on a faster partition, or it points to memory(for example point to /dev/shm), then it'll be faster than /tmp

no cache enable flag like [E=Cacahe-Control:mag-age=60] in reriterules and use W3TC at the same time. how did you enable lsws cache ?

please check if any message left in /usr/local/lsws/admin/logs/error.log when you get the white screen. also switch to latest 4.2.4 to see if it's still problem. and switch to version before 4.2.3 to be more sure 4.2.3 is the root cause.

the cached file don't look helpful --- but great you can dig it out please paste the rewrite rules which lead to cache "/" (can omit rules to cache other URLs)

the best way should be you and every user feel the site faster and no one complaint. there are many automatic monitor tools in the net, but is hard to tell which one is the best. the first and most important thing looks to be the network traffic. then google analytics is an ideal tool to...

do you use /usr/local/lsws/admin/misc/purge_cache_byurl.php to delete the cache?

you can start from 2-CPU license, monitor the traffic and performance, and change the type of license monthly-base. the CPU here not mean physical CPU, core looks better than CPU in the license context, but this term has been there for years and is not likely to change soon since it may confuse...

set limit to soft/hard connections per IP (e.g., 20 / 30) the web server will block the IP for "Banned Period (sec)" automatically