Search results

You need to check /usr/local/lsws/phpbuild/php-5.2.17/config.log compiler does not work properly. or try easyApache, then build matching PHP from WHM.

should be "--with-libdir=lib64".

have you add "--libdir=lib64"? Just use "--with-jpeg-dir=/usr".

http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:php:lsapi:troubleshoot

You may change some permission manually under /usr/local/lsws, the default should work fine. Please do a reinstall. Make sure there are enough disk space available under /usr/local/lsws.

Please check our wiki regarding PHP compilation errors http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:php:lsapi:troubleshoot#configure_compilation

Please download and try 4.1.2 build, just change version number in the download link to get it.

all detected robots are blocked at firewall level, not measured by PPS, it depends on incoming bandwidth usage by robots.

I think it might be due to hash collisions. We will add more code to handle this situation. And we will improve the hash function for the page cache indexes to reduce collisions, will let you know when it is ready.

sure. let us know then domain can be added/removed to reproduce this problem.

Please make sure you do not disable Apache httpd service from WHM. It does look like LSWS restarts to apply the change, does the new account works?

please check /usr/local/cpanel/logs/safeapacherestart_log and /usr/local/lsws/logs/ap_cmd_param.log after adding/removing a domain. safeapacherestart_log shows when cPanel restart Apache. usually, cpanel wait up-to 1 minutes to apply new changes. You can try reverting back to 4.0.20 manually see...

Please check response header with firebug see if the default cPanel page has "LiteSpeed-Cache:hit", if not, it has nothing to do with page cache, just the new configuration has not been applied. Please note that cPanel delay applying new configuration, so new domain wont be take effect...

I think you can update cpanel vhost template, not to do that by default. 4.1 and earlier release does not apply include_path configuration in those files anyway, I think it is safe to remove all of them.

4.1 read configuration in section of <IfModule concurrent_php.c> while 4.1.1 read configuration in section of <IfModule !concurrent_php.c> php4_admin_value and php5_admin_value are ignored, so 4.1 does not set include_path. Yes, I think it is safe to remove those files.

those bad include_path configuration is from /usr/local/apache/conf/userdata/std/2/<domain>/cp_php_magic_include_path Is there any WHM option to get rid of those files? Path configuration in those files are wrong.

Looks like PHP crashed while processing the script. Can it be reliably reproduced, every time accessing that page? if you switch back to Apache, do you get blank page for the same page? You may need to enable PHP core dump to find out why. Please search the forum no how to.

maybe we need to login and take a look.

Can you please check phpinfo() page with 4.1 and 4.1.1, compare "include_path" configuration. Also Please check Apache httpd.conf see if there is any configuration with value "/home/username/php". it has to come from somewhere, LSWS wont add something by itself.

It is likely cached by browser, just clear browser cache and try again.