Search results

Thanks for the tutorial, will add it to our wiki.

Please check this post http://www.litespeedtech.com/support/forum/showthread.php?t=861

No, you dont need to create a vhost template when use Apache httpd.conf directly. You can check if port 81 is open with command "netstat -an | grep 81 | grep LISTEN". If it is, try to access a vhost on port 81. The "restart required" status for all IP and vhosts in web admin console might be...

I am not perl expert. You can try "/^(1|2|3|4|5|6|7|8|9|10|11|12)$/"

You need to set port offset to "1", so LSWS will use port 81. As long as it uses standard Apache directives, it should work. Do you mean the /~username/..., it is not supported directly, but can be archived with some rewrite rules. Yes.

Thanks for the praise. Please help us spreading the words, if you dont mind. :)

Just backup your VHOST configuration and reinstall LSWS.:)

lshttpd need to be started by root user, and change to a nonprivilege user. You need to check the user that lscgid run as, should be root. Please double check the user who own the document root directory of that vhost. make sure it is not owned by root. You can remove the server level script...

Can you strace the perl process for lsperd.fpl? I tried it on our 3.0 release, works fine. You can download 3.0 release by changing the version number in the download link.

If you want you can block a subnet instead of a IP.

No, you don't need to change configuration for 3.0RC2. Must be something wrong. Did you upgrade from 2.2.6 to 3.0RC2 on the same server? or try 3.0RC2 on another server? Anything in error.log and stderr.log? Can you try a simple "hello world" perl CGI script?

Thanks for the suggestion. We redefine ENV to a hash array instead of the standard char **environ, which should give better performance. It only happen once during LSAPI initialization. I am not sure what you suggested works or not, will give it a try when I got a chance.

How about use /dispatch.lsapi as a 404 handler, so you can remove the last rewrite rule?

That's as designed, LiteSpeed does not do blocking reverse DNS lookup in our event driven single thread process. We may add non-blocking DNS function in later release. Please use IP for now.

60 is 1 minute, maybe try something like 3000. And set "PHP_LSAPI_MAX_REQUESTS" environment variable to something like 500, so a PHP process will exit after processing 500 requests.

Please check output of "ulimit -t", it should be ulimited. And try to increase "CPU soft Limit" and "CPU hard limit" under "server"->"Security", this limit does not be applied to PHP LSAPI, only apply to plain CGI. But it does not hurt to increase it. Which version of LSWS are you using?

Yes. No clue, you can grep the "no convert in" string in PHP source code see if you can find something.

I don't think it is a bug in our LSAPI module, should be some where inside PHP. Since LSAPI SAPI is used, the entry point of PHP is always from our LSAPI module, you have to check the detail backtrace to figured what exactly causes it.

Does DNS of test.mydomain.com points to the same IP as mydomain.com? You can turn on debug logging by change "Debug Level" to "HIGH", and check the error.log output during restart and serving a request for test.mydomain.com.

<maxConnections> is the limit of client connections, PLAINCONN will not exceed this value. <maxconns> is the limit of number of connections that LSWS will use when talk to a backend external application.