Search results

the error message is about LVE limit. >we need opcache. just enable opcache while disable LVE

probably a permission issue introduced from Magento. can you try #chmod -R 777 /tmp/cache/ for a quick action. after the change, restart lsws. see if these errors still there.

I can reproduce this issue on latest lsws 4.2.20, and ok for 4.2.19 it's because of change of /usr/local/lsws/admin>diff html.4.2.19/utility/build_php/build_install.template html.4.2.20/utility/build_php/build_install.template 6a7 > # PHP_USRGROUP = {PHP_USRGROUP} 103,104c104,105 <...

CentOS should be ok since it's the major target OS. how did you install lsws on this server ? install.sh ? to ensure to be root user fist before do installation.

which linux distro , redhat / centOS / ubuntu or freebsd / iOS ... etc ?

I think 2nd link is good enough. redmine is a popular application and complicated enough. I know some users has run redmine + litespeed + ruby-lsapi for years smoothly. but might be not latest redmine and latest ruby-lsapi

>It's a brand new fresh installed Debian 7, any clue what's wrong with my exim? run test from linux command line first(before test in php), can it work ? >And if I set LSWS to run as nobody:nogroup then should I set nobody:nogroup too for all of my public_html? or lsadm:lsadm or I can set to...

can you confirm: switch back to 4,2,19, the issues not exist ? there should be no difference between 4.2.19 and 4.2.20 regarding lsphp. We'd identify and resolve the issue ASAP too. the quickest and best way is: 1) provide us the server's root access 2) among all the issues, find out the most...

please check the logs of web admin(7080), default path is /usr/local/lsws/admin/logs/access.log and error.log to get more information

you can create a simple test.php to ensure if mail works or not e.g., http://php.net/manual/en/function.mail.php Example #1 Sending mail

just consider xcache is part of php. since xcache can work well with php 5.4 / 5.5 / 5.6 and litespeed works well with php 5.4/5/6 so xcache work well with litespeed.

this is common for php 5.4 and above (no direct relation with litespeed): Zend Opcache or XCache is recommended eAccelerator and APC are not recommended Opcache has no variable cache while XCache has.

>1. What Operating System is the best for LSWS? I'm considering about Debian 7 or FreeBSD. Debian. however Redhat or CentOS may be better than Debian >2. What File System ia the best for hosting PHP File with some static files? I'm considering about EXT4 or XFS. I believe no difference...

I think 3 steps: 1. have access log to show the real IP: https://support.cloudflare.com/hc/en-us/articles/200170676-How-do-I-restore-original-visitor-IP-with-a-LiteSpeed-server- 2.from the access log, find out those IPs with certain algorithm. 3.submit these IPs to cloudflare front end servers...

in your case, please try php "suEXEC Daemon" mode the default is "suEXEC Worker" mode document: http://www.litespeedtech.com/products/litespeed-sapi/php/guide-to-suexec-setups

in phpinfo, check open_basedir and include_path, see if they're same between apache and litespeed.

I couldn't find any useful message in the debug.txt other than >[STDERR] PHP Warning: Unknown: failed to open stream: No such file or directory in Unknown on line 0 maybe fail to load a php extension .so ? to debug in this direction, put a phpinfo.php on the problem site's document root, 1)...

the master config file: /usr/local/lsws/conf/httpd_config.xml

virtual host level rewrite has higher priority, it can be used to resolve context conflicts issue. here's one safe and easy to understand solution: remove those 2 contexts, implement them all in rewriterule in Rewrite Tab, add RewriteCond %{REQUEST_URI} !^/upload RewriteRule /(.*)$...

it looks the issue has gone. Can you let us know what's the problem ? I suspect configuration issue, maybe the change of default ext app settings for lsphp5