Search results

That's strange. Can you please try the latest 3.3.4 build, see if it works? Just change the version number in the download link.

We have plan to implement mod_ssi, should has them covered.

What Frank said is true, another thing to consider is the I/O wait, like all other light weight web servers, blocking disk I/O will block lshttpd process, so if your server has high I/O wait, you should consider license for higher CPU count in order to compensate and bring the best out.

No, it is no good solution for that with current LSWS. Can you just override the error page from S3 side?

My guess is that the eaccelerator extension is missing or does not match the PHP version for some reason, please follow our trouble shooting steps in our PHP tutorial in our wiki.

Maybe you need to play with the "PATH env" by set it to the same value as your shell.

Well, you have to install all the libraries/packages that PHP modules depends on. It is not a problem of the LiteSpeed GUI, but your development environment.

Check anywhere you have "public" in your configuration. ;)

Turn on debug logging, see where it looks for the file. Maye need to add directory index file?

check the owner of /usr/local/lsws/somedomain/public/, make sure it is not root or a system user with UID less than 11.

Fix is in our 3.3.4 release. you can give a try by changing the version number in the download link.

A possible solution: http://discussions.apple.com/message.jspa?messageID=5888478

Those errors are between ld and system libraries, so, I guess maybe your compiler environment need some special options, like building universal binary or something like that. It will be very helpful if you can find a gem that builds native ruby extension, and post the compiling parameters used...

Please set "Path Env" to the same value as in your shell terminal, it should fix the gcc problem. Another issue has been fixed: http://www.litespeedtech.com/support/forum/showthread.php?t=1630

Please download 3.3.4 release package and give it a try, just change the version number in the download link.

DirectAdmin create too many useless vhosts for each IP, so, the 5 vhosts limit has been reached. check your httpd.conf and make sure to place the real vhost configuration at the beginning of the configuration file. I don't know what cause the gzip problem, maybe the source code package has...

To help us identify this problem, can you please truss or ktrace command "./lshttpd -d", it should show the crash point.

the total log entries is the number of line in the current 20K log file. You probably have debug logging enabled.

You should check rails logs, those are rails errors.

same as with Apache, if you use LiteSpeed with control panel, just load the configuration file in httpd.conf.