How to setup Cloud Linux LVE properly and AllowOveride Warning

Member

We've been using LiteSpeed now for a while now with Cloud Linux and MariaDB. Recently we decided to do an SEO scan on one of the sites from an office PC and the CPU shoots right up to 95% or more. We have the account limited but it seems like the LVE is not being used at all. Going through our settings we found Cloud Linux setting but triggering it lost us the use of the PHP Selector and our site went back to PHP 5.5.

We've looked at some of the documentation but we are not sure what the correct settings are to get it functioning correctly. We have new relic and it was showing lsphp consuming the most CPU time.

Could someone let us know what we need to change to get it functioning properly? I'll post screenshots below.

We also have another issue with 'Directive 'AllowOverride' is not allowed in current context.', when we sign in to the LiteSpeed panel we have these warnings show:

Code:

2017-02-04 23:14:22.438 WARN /usr/local/apache/conf/httpd.conf:70: Directive 'AllowOverride' is not allowed in current context.
2017-02-04 23:14:22.438 WARN /usr/local/apache/conf/httpd.conf:70: Directive 'AllowOverride' is not allowed in current context.
2017-02-04 23:14:22.438 WARN /usr/local/apache/conf/httpd.conf:76: Directive 'AllowOverride' is not allowed in current context.
2017-02-04 23:14:22.438 WARN /usr/local/apache/conf/httpd.conf:76: Directive 'AllowOverride' is not allowed in current context.
2017-02-04 23:14:22.438 WARN /usr/local/apache/conf/httpd.conf:110: Directive 'AllowOverride' is not allowed in current context.
2017-02-04 23:14:22.438 WARN /usr/local/apache/conf/httpd.conf:110: Directive 'AllowOverride' is not allowed in current context.

Does anyone know how to resovle this?

Thanks in advance for any help and if you need anymore information please let me know,

Member

I'll give that a go and let you know the results with the AllowOveride issue.

CPU 95% refer web server's CPU(not office PC's CPU) ?

With the CPU percentage I used I should of been more clear and said these values were from New Relic, I should of added the data straight away, here is what says now:

usually a web site's bottle neck is at php/mysql side.
Were looking into this, this site in question has MyISAM tables which we are thinking would be better as InnoDB or xtraDB. We know we might need to change some DB settings, do you have any reccomendations for this?

optimize php code
What exsactly do you mean here? The websites using PHP 7.0.13, we've done all the usual things on the website to optimise it as well. GTMetrix rates most pages A & B with roughly 2 sec load times, even when the CPU is under heavy load.
add php opcode cache
This is switched on and cache rate is 100%, we have been trying to get apcu working with opcache.
add page cage (like lscache plugin for wordpress) is the effective way to reduce web server's CPU usage
We are using LSCache as we have the enterprise version of the software.

All the above however doesn't relate to getting the LVE manager working, if this was working (We would still have performance issues on the site level) it should cap the account to the CPU level we specify?

since this is a cloudlinux feature, I actually haven't much experience on it and don't understand it well.
just took a look at cloudlinux's document, https://docs.cloudlinux.com/index.html?cpu_limits.html , CPU limits is "no longer used, and SPEED is used instead". you may need ask cloudlinx how to test LVE limit (especially CPU or SPEED) for greater details.

Member

We are aware of the change in limits, and before we switched to LiteSpeed it was working.
What I am saying is under general -> server process -> cloud linux, its set to CageFS.
For the LVE to work with LiteSpeed I assume this setting should be LVE?.
When we switch to LVE we loose the Cloud Linux PHP selector.

This must mean we have something wrong with the above configuration?

I guess it might be better to ask on the Cloud Linux forums for this particular issue?

can you be more specific about working or not working ? it looks like I've caught your point until now.
so your question is: under apache, LVE limits works; after switching to litespeed, LVE limits not working ?
can you switch between apache and litespeed to reproduce the issue easily ?

Administrator

regarding database, best you discuss with database expert we're not.
our point is: static page(image, js, css etc) is served by web server(here litespeed) directly. dynamic page is generated by backend php/mysql, usually it's much slower than static page. so we say usually the bottle neck is at php/mysql side. for particular server, bottle neck may vary. some may be php only, some may be mysql only, some may be both. some may be network/disk io etc. identifying the bottle neck first is a general good method for troubleshooting.