Search results

Have Perl work properly on the server? Is there any thing related in error.log and stderr.log? You can try switching to dynamic mode, if it breaks as well, some log messages hould be left in either error.log or stderr.log.

Yes, it is.

Please try 3.1.1 release, this and the ErrorDocument issue should have been addressed. http://www.litespeedtech.com/packages/3.0/lsws-3.1.1-std-i386-linux.tar.gz

using apache specific function is not a good practise in PHP programming. I think wp-cache for wordpress should work well with LiteSpeed, wordpress.com and a few other large blog sites are using it with LiteSpeed without any problem. It is possible to fake a apache_response_headers() in our PHP...

Sorry, forgot to upload them, should be available now.

Maybe text/xml is not in the default MIME list, but added later after the compression has been configured. We will investigate.

Thank you for the suggestion, improving the documentation is ongoing task to us.

cPanel does. What is permission mask and owner of domlogs that cPanel changes it to? We will change the owner of individual log files to nobody:username in next release, hope it will help.

OJ, I think we had identified and fixed your 404 problem in ealier release. It will be great if you can confirm this. aww, Your 404 problem might be different, please let me know the detail.

Maybe something wrong with the solaris update agant. We will check.

We may remove those signatures in the future, you need to add custom error pages for now. :) And there is nothing ashamed of being LiteSpeed. ;)

Yeah, that's one of the minor compatibility issue existing. Actually, LSWS can do that, just need to allow it during Apache configuration parsing phase. Will add that. Thanks for pointing it out. :)

You can do that, just change the cache location in the php.ini .

You probably need to enable the optimizer from lsws/php/php.ini, then do "killall lsphp".

If you are using our pre-built PHP binary or PHP 4.4.6, just run lsws/admin/enable_phpa.sh Then select eAccelerator, it will fetch our pre-built eAccelerator binary. If you use PHP 5, you need to build your own, just follow our wiki and eAccelerator installation instructions.

Looks like that's a permission problem for /tmp/lshttpd directory. Have you reinstall LSWS under another user account? Yes, the service command is available if the rc script has been installed. service lsws start

Please check if the port is in use with command "netstat -an | grep <port>", It lists at least one listening port. And you can turn on debug logging by changing "debugLevel" to 10 in lsws/conf/httpd_config.xml, it will give more detail log in lsws/logs/error.log. You should be able to find some...

Please check the permission/ownership of /usr/local/apache/domlogs directory, maybe that is causing the permission problem. The ownership of the log file probably is not that important as long as it has been set to be world readable. To remove lshttpd rc script, just run...

Glad you figured it out, and thanks for the detail step by step tutorial, I will add that to our wiki. :)

Looks like that a Mongrel instance has gone bad, it closes the connection without sending back anything, and LiteSpeed keep trying the bad Mongrel, so the end results are both lshttpd and mongrel uses a lot of CPU. Please try the latest 3.1 release, it should be as stable as 2.2.6 if not...