Search results

It is a bug introduced by 2.1.10 when fixing the other one. :oops: Will be fixed in 2.1.11

Your "MyfastCGI" has not been configured properly, <autoStart> set to 1, but the path to the fastcgi application has not been given, you should got some error message during server startup. As the FastCGI has not been configured properly, access to the FCGI context is denied.

Have you created a FCGI context with URI /helloworld.fpl using the helloworld.fpl fcgi application? It will not work if you only add a script handler for .fpl.

Yes.

It should not be redirected if you use a URL like "/error404.html", I think you are using an absolute URL like "http://<your_host>/error404.html"

Eff Max is the maximum connections lsws thinks it can use. "Eff Max" equals configured "Max" at the beginning, sometimes, one fcgi process can stop stop responding for some reason, for example, a runaway process whenever that happened, lsws will reduce the "Eff Max", when "Eff Max" reaches...

Besides maximum sockets and epoll, if the server serves a lot of static file, you can turn on sendfile as well.

You need to manually upgrade PHP binary by copying lsws/admin/fcgi-bin/admin_php to lsws/fcgi-bin/lsphp, don't forget to update PHP opcode cache. We don't want to overwrite a customize built PHP binary with our default.

Please give 2.1.10 a try, http://www.litespeedtech.com/packages/2.1/lsws-2.1.10-ent-i386-linux.tar.gz Hope it has been fixed. To others reading this post: Please note 2.1.10 is beta package to fix above bug report. Until formal testing has been conducted, beta-tested by our beta partners...

We are not working on running apache modules in lsws, that will be very boring and slowing down every thing. :-) We just want to duplicate the most useful features in Apache, possibly using Apache's configuration directly, that's it. :-)

I think there is something wrong with your private key or certificate file. The private key file should start with a line like -----BEGIN RSA PRIVATE KEY----- The certificate file should start with a line like -----BEGIN CERTIFICATE----- Try following our howto to generate your key and...

Yes, it is, but it is hard to say when it will be release right now, as we will freeze on new feature development for a while and focus on stablizing and marketing the existing product. We will inform you about the release date when we start to work this. Thanks!

You have checked LSWS error log, all STDERR output of PHP will be redirected to LSWS error log.

Thanks for the totorial, looks very good. :-) The timeout of the web admin console is configurable. http://www.litespeedtech.com/docs/AdminGeneral_Help.html#sessionTimeout

Great Story! :D Thank you for sharing.

You can check "I/O wait" and "CPU idle", if CPU idle is very low or I/O wait is pretty high, then the server was maxed out. The load is mainly contributed by PHP scripting, not inside LiteSpeed, it will help alot if you can make PHP run faster. :-) If possible you can try other PHP opcode...

It is hard to say what is the root cause of the problem, my guess is the table level lock in MySQL. One request locka a table for too long and blocks other requests, so requests are queued up at the front end server, which causes the high load. You can try some vbulletin hacks that minimize...

Thanks! Fixed. :-)

Sorry, we don't have time to work on that yet.

I tried FreeBSD 6.0 in our lab, looks like there is some problem with the statically linked openssl library, when SSL is used, it will dump a core file. Looks like FreeBSD 6.0 needs a dedicated lshttpd binary.