Search results

Is that possible to PM me temp root access to that box, I will take a look and have it fixed ASAP.

Yes, it is OK. That statement is based on the assumption that you install cPanel PHP and LiteSpeed PHP to the same location.

Checked the issue, that because the rewrite rule has been executed again when process the custom error page, you need to change the rewrite rule to RewriteCond %{REQUEST_URI} !^/my301.html RewriteCond %{HTTP_HOST} ^mydomain\.com [NC] RewriteRule ^/(.*)$ http://www.mydomain.com/$1 [R=301,L]

You can do that, this two will not interfere with each other. However, you may have compatibility issue as some PHP script written for 4.4.7 which may not work that well under PHP 5, it has nothing to do with LiteSpeed. I think you should at least upgrade cPanel PHP to 4.4.8, and install LSAPI...

The path to the log file should be in the wrapper script. take a look.

The instruction for the GUI is in the wiki of compiling PHP and cPanel+LiteSpeed.

You need to recompile, install it to a different directory, it will not conflict with existing installation. It is recommended to keep cPanel installation and LSAPI installation in sync. So, upgrade your cPanel installation to PHP5, then build Litespeed PHP with similar configuration parameters.

I think you should use PHP or perl script to update the XML configuration instead of using shell script.

Can you please go through the audit log and check how many rules are result in 404, how many rules are not.

lsws/bin/lshttpd -r cp lsws/license.key conf

You can switch to another version with command line tool: /opt/lsws/admin/misc/mgr_ver.sh If you find core file under /opt/lsws/bin or /tmp/lshttpd, please forward to bug @ .... , Are you using 64 bit?

You can set the disk file to location like /dev/shm.

A custom build PHP and opcode cache are included with the installation. You need to find the mod_security ruleset you want to use. If it is configured with Apache, it will work with LSWS without problem.

Please check the parameter log file at /opt/lsws/logs/ap_cmd_param.log. See what command parameter has been used by easyapache to check "httpd".

Attention cPanel users: If you use the "Use Apache Binary wrapper" feature, please make sure to check "httpd" service under "Service Manager" section.

I think eAccelerator is still the most reliable one.

Are you using the new Apache binary wrapper? Or, just a upgrade? from which version?

We will fix it in next release. It should use "nobody:nobody", instead of "apache:apache".

It is not useful at all, but thanks! :) Only backtrace from core produced by the debug build of lshttpd is very useful. debug build is lsws-3.3.x/bin/lshttpd.dbg, you need to manually replace /opt/lsws/bin/lshttpd.3.3.x with it. You should be able find pass installation packages under...

Don't worry about it. it is just what modern bill shows for one time payment.