Search results

this is the default setting and almost unlimited connections -- so white list looks unnecessary. is there any valuable error message at web server around the time stamp when lslb have the connection errors?

looks like right. have you white list LSLB's ip in web server ? http://www.litespeedtech.com/docs/webserver/config/security#perClientConnLimit Connection Soft Limit Connection Hard Limit

yes. this is hotlink protection for. or simply use rewrite rule: RewriteEngine On RewriteCond %{HTTP_USER_AGENT} !mydomain.com RewriteRule .*.json$ - [F,L]

the response header "Cache-Control" is ignored by ls cache. (for current version) this is different with how varnish works. the "Cache-Control" header from backend server will pass to end user but not used by ls cache. how long will ls cache a page is determined in lsws configuration, for...

per http://php.net/manual/en/openssl.installation.php you have to re-compile php --with-openssl[=DIR] or --with-openssl=shared

this wiki is for warn up: https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:cache:litemage:troubleshooting:warmup

per the screenshot, 15th -- 18th week, the load dropped to roughly 50% this is good example for ProcessGroup + XCache vs Worker without opcache. load drops about 50% and compared with apache, consumed much less memory. Thanks for the sharing.

update: seems not an issue. in error_log, the last permission issue is found on May 13. all accounts has been running ProcessGroup mode when I logged in on May 15. during about 2 days period I was on the server, always in ProcessGroup mode. how to determine if lsphp running in ProcessGroup mode...

the answer is Yes. you can upgrade to 5.0 to see if it meets your requirement 100%.

yes. regarding xcache configuration: http://xcache.lighttpd.net/wiki/XcacheIni I think the most important one is xcache.size. each account will assign that size memory. if you set it to 256M for example, when there are 100 websites are accessed at a time, 100 x 256M ~ 25G memory are allocated...

as the wiki say, among 3 suEXEC modes, Worker and ProcessGroup mode is able to work with CloudLinux's PHP Selector. but the 3rd mode -- Daemon mode can't work with PHP Selector. default is Worker mode for all users. the end user can't select ProcessGroup mode. since it's in httpd.conf. the only...

load 5-6 is not high if you've 8/16/32 cores. by the "top -c", lsphp (so are you using cloudlinx's php selector ? if not usually it's lsphp5 process) consumed most CPU. no good way to lower the CPU usage unless you enable XCache or Zend OPcache in ProcessGroup mode more info please refer...

this number looks high, surely high traffic. check with "top -c", which processes have the high load, lsphp5 or litespeed process ?

for nf_conntrack / ip_conntrack issue, there is a wiki to address it: https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:config:nf-conntrack-table-full

I'm ok today to login your server to take a look. please PM (Start a Conversation) your server's access.

the real-time stat is a known issue for 5.0, since the format has changed --- /tmp/lshttpd/.rtreport* you can force update to latest build 9. maybe or may not be fixed --- depending on the develop progress -- I haven't tested it yet.

>2015-05-12 02:57:08.134 ERROR HttpListener::start(): Can't listen at address [::]:80: Address already in use! is there any other web server running ? like apache, nginx ? if no, only litespeed is running, then do a full stop and start, instead of gracefull restart...

for the first visit to a page, lsphp is launched. then the result is saved by litespeed as cache AND saved by W3TC as static file (i.e., saved both times) when 2nd visit come, the rewrite rule will rewrite to a static file which W3TC has generated, so litespeed think it's actually a static page...

I re-visited an article page. it returns 304 cache:hit not seen likely because wordpress cache plugin W3TC litespeed only cache dynamic pages. it won't cache static page since it's not necessary at all. if some article pages already generated to static file by W3TC, then static file is...

are you sure no any change made ? there should be no other magic. or you have me to take a look at your server.