Search results

Please do a force reinstall of 4.1.4 to make sure getting the latest build. We fixed a bug in realtime statistics report that may cause 100% problem. Not sure it is the one you experiencing or not. If it happens again, please try "strace -tt -T -p <pid_of_100_CPU_process>", for a little while...

Please upgrade to the latest release, it should have been taken care of. Or, you can add "concurrent_php" to http://www.litespeedtech.com/docs/webserver/config/general/#apacheIgnoredModules

Not likely is a disk space issue. Should be something else. google results indicates that is an issue with libjpeg. If you can reproduce this error, you just strace the PHP process producing the error to find out why.

IP should work, domain does not.

http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:license:transfer_release_license

I think 8000 accounts should be fine. maybe hit a bug in LSWS, please contact bug@litespeed... our staff can take a look if you do not mind.

sendfile should be enabled along with AIO. Maybe you are using PHP script to streaming files, it is low efficient, if so, you should consider using internal redirect feature. http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed:wiki:feature:internal_redirect

You have to reinstall LSWS and specify the user/group during installation. If you use LiteSpeed along with hosting control panel like cPanel, you should not do that, running as another user will break control panel integration.

checked the implementation, looks like vhost level external app is not allowed to set suEXEC user/group, please move the external app definition to server level.

you may forget to create script handler for ".php" using vhost level lsphp5 external app. And the vhost level lsphp5 external app should have unique name, adding username or vhost name as part of the name is recommended.

Use LSWS with 2-CPU license, it will give your basic load balancing and cache, I am not sure varnish can do load balancing or not.

Please switch back to Apache to verify if apache mod_security does the same. Changing release number for each build is a big overhead. We will release a new release package after we confirmed that all known bugs have been successfully fixed.

The fix is to comment out <LocationMatch "^/_vti_bin/.*.exe> </LocationMatch> section in /etc/httpd/conf.d/mod_frontpage.conf Later build of LSWS will do that automatically, no further actions is required.

if use vhost template, should not set UID/GID in external app, only use Doc root uid.

Please do force reinstall of 4.1.4, it should be addressed now. Scan request body is enabled by default in 4.1.4, while it was disable in Apache and earlier release of LSWS.

Please do force reinstall of 4.1.4, it should be addressed now. Scan request body is enabled by default in 4.1.4, while it was disable in Apache and earlier release of LSWS.

You need to define vhost level lsphp5 external app and script handler, use "Doc root UID", or set UID/GID explicitly in external app configuration.

Using LiteSpeed alone is your best choice.

Any one can reliably reproduce this problem with 4.1.4, please contact bug@litespeed..., we need to figure out what exactly causing this problem.

setenv is not supported, please use RewriteRule .* - [E=SHOP_PATH:/home/www/public_html/] instead.