Search results

We will investigate this issue and have it fixed in the 3.2.1 final release.

Have you tried a reinstallation? Maybe the httpd_config.xml is corrupted for some reason.

A sample perld configuration: <extProcessor> <type>fcgi</type> <name>lsperld</name> <address>uds://tmp/lsperld.sock</address> <note></note> <maxConns>20</maxConns> <env>FCGI_PERL_MAX_REQ=1000</env> <initTimeout>60</initTimeout>...

We are working on it.

under server->external app for the FCGI Application, then server->script handler section for the script handler of "pl".

You can run perl script either as plain CGI script in suEXEC mode, or run it within the our Perl FCGI container as the user/group of the web server run as, "nobody/nobody". To run perl CGI script as plain CGI, just add a server level script handler for "pl", using CGI as the handler. To use the...

It probably is a bug in the web admin console code. What changes you have made in the web admin console? Please check if there is any related error message in lsws/logs/error.log or stderr.log.

Anything special for this vhost? can you send us the vhost configuration for this one?

OK, "none" is a special value need to be treated differently. Will fix that.

We will have this issue addressed in final 3.2.1 release.

The first .htaccess error probably is because the comment at the end. start it at another line, it should be fine. For the other site, there might be some issues with the .htaccess configuration for that site. please send us the .htaccess file.

When you do a "ab" benchmark, you may need to turn off LSWS request rate throttling in order to get meaningful results.

If PHP send back compressed content, LiteSpeed will send it as is without trying to compress it again. So, it does not hurt to leave it on. Yes, use compression level 1 if you want to save some CPU cycles.

It works for files already cached, For new file or updated file, the uncompressed version will be used. unless you are running short of disk space, this option should be enabled.

http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:apache:plesk

Please download and try the latest 3.2.1 build, a simple plesk wiki is added, it may not be complete. If you need to do any extra step during the installation, please let us know. http://www.litespeedtech.com/packages/3.0/lsws-3.2.1-ent-i386-linux.tar.gz

LiteSpeed can use manually created gz files, it is optional to create compressed version of the static file. LiteSpeed is designed not to repeat the same task again and again, so the compressed version will be cached for sure. Yes, LiteSpeed will update the compressed cache if the original...

The limit is higher because we want to make sure that the limit will not break any thing. During a graceful restart, the number of processes running on the same user ID might be higher than you expected. The way we calculate the limit is: ( 3 * MaxConn + 50 ) * Number of CPU license

I just checked another production server which has similar configuration, and userdir works well? Have you tried it with other accounts? Please double check that the IP and account name matches in the vhost configuration section of httpd.conf.

Please download and try the updated 3.2.1 package. you may see uncompressed version being served during the construction of the compressed cache for that file, once the compressed version was built, compressed version will always be served.