Search results

please give the output of the above command on your server: #grep chrootPath /usr/local/lsws/conf/httpd_config.xml

it looks you enabled chroot when install lsws ? to confirm, take a check: #grep chrootPath /usr/local/lsws/conf/httpd_config.xml

any message in /usr/local/lsws/logs/stderr.log ?

does lsws web admin( :7080) and command line lsphp5 ok ? /usr/local/lsws/fcgi-bin/lsphp5 -i |head have you changed any default settings via web admin ?

>Or it is for setting Memory limit for each child php process of the external application which are forked? yes, this one.

looks weird ... have you stopped apache ? do you read apache's httpd.conf ? have you built lsphp5 ? (#ls -l /usr/local/lsws/fcgi-bin/) ... please provide more info about your setup.

yes, just a simple force install to compare: ls -l /usr/local/lsws/bin/lshttpd.4.2.19 to know when they installed lsws 4.2.19 last time. then simply do a force re-install /usr/local/lsws/admin/misc/lsup.sh -f -v 4.2.19 or through lsws web admin Actions->Version Manager->4.2.19:Force Reinstal...

OPcache is better than APC

what's your php version ? latest version eAccelerator not support php 5.5 and above. and APC is replaced by OPcache. for php 5.4 and above, only OPcache and XCache are recommended

please ask them to do a force-reinstall to ensure the latest 4.2.19 on command line: /usr/local/lsws/admin/misc/lsup.sh -f -v 4.2.19

Cache is disabled by default. then you can enable cache for selected sites. please refer https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:cache:lscache for how to enable cache for website.

lsphp55 error message can be ignored. to have it disappear in error log: #ln -s /usr/local/lsws/fcgi-bin/lsphp5 /usr/local/lsws/fcgi-bin/lsphp55 >11/28/2014 19: 30: 49,824 ERROR [ModSecurity] Variable unknown server while parsing: MULTIPART_STRICT_ERROR can ignore it. it's because litespeed's...

you mean apache logs filled with "Failed to start one instance. Resouce limit reached!" ? per discussion above, it's likely a configuration issue : LVE limit too low. if the issue happened only once, it's hard to find out the root cause. maybe just a restart fix it. if it happens repeatedly...

if your current apache + mod_ruid2 works fine, no need re-build apache. just run litespeed cPanel/WHM Plugin (http://www.litespeedtech.com/products/control-panel-plugins/cpanel-whm-plugin) will do. it'll build matching lsphp according to current apache php's settings.

how did you build lsphp5 ? maybe the problem is here. now the site is running nginx

update: already resolved. "It was due to broken systemd setup in this server, the rc script was not installed properly. fixed now."

REQ/SEC -- requests/second REQ IN PROCESSING -- requests in processing these value are for display only, you can't set it.

>Why do you say it is for all users, not per user? I think you're right. should be per user. here's an accurate answer to your question: >And fork is possible with no limits? >I really need to limit them in terms of the number of processes. /etc/security/limits.conf does not work, neither...

Thanks. So should enable fileprotect when using litespeed. if not, manually enable it by # touch /var/cpanel/fileprotect here's official document for FileProtect https://documentation.cpanel.net/display/EA/Apache+Module:+FileProtect

can you force-reinstall 4.2.19 and test again, there is a new build 3 hours ago. #/usr/local/lsws/admin/misc/lsup.sh -f 4.2.19