the memory usage is not high: only 1038M used, 6936M free. most memory are used as cache(6667M) by linux
please provide more detail info regarding "Request Timeout" issue. any log in error.log or stderr.log
any log messages in error.log/stderr.log?
does /phpinfo.php also has same problem?
php suExec enabled or not ?
how many virtual hosts on your server?
does phpinfo() under apache and lsws match ?
please provide more detail info. in general, php scripts running under lsws are much...
first, need locate the vB source code where set the cookies.
in example of bbforum_view, it keeps recent-visited-forum history of a user, limit to recent 10 forums, not appending it forever.
there is a setting:
Server->Tuning->Max Request Header Size (bytes)
but usually it's not a problem.
another clue is to check if ip_conntrack tables is full.
check:
#cat /proc/sys/net/ipv4/ip_conntrack_max
#cat /proc/sys/net/ipv4/netfilter/ip_conntrack_count
I suggest you to keep w3total since it's out of box solution.
lsws page cache is a general cache function, to have it work perfectly with wordpress, need some extra work to customize the rewrite rules.
rewrite rules from w3total cache take priority in your .htaccess, so the rewrite rule you added won't reach at all.
both w3total cache and lsws cache are page cache to cache wordpress pages, you only need one at a time, not both.
if working under apache, it should work under litespeed.
to be sure "Build Matching PHP" are done correctly.
to confirm this, compare phpinfo() under apache and litespeed, see if they matches.
can you post the rules here if they're not long?
Include "/usr/local/apache/conf/modsecurity_crs/SQL_injection.conf"
Include "/usr/local/apache/conf/modsecurity_crs/XSS_attack.conf"
are you referring this one installed on your server?
http://www.directadmin.com/features.php?id=894
Integrated awstats into DirectAdmin
what happen when access
www.mysite.com/awstats ?
any messages in error log?
need build matching php for litespeed, need rebuild xcache as well. php and xcache for apache still be there in case you fail back to apache.
in general, you can run both litespeed and apache in parallel for some time. litespeed listen to port 2080(for example) and apache listen to port 80.