Search results

Which OS are you using? Looks like the PHP code has not been properly patched when you build matching binary from WHM, it should grab the latest PHP LSAPI patch and create /home/cpeasyapache/ls.src/php-5.2.6/sapi/litespeed/ directory. Is the directory created? Please try it again see if there...

This error means that the script generate an extremely large response header. larger than 64K. Maybe store too much data in the cookies? It is not efficient.

probably will not, just build your own from the web console.

Maybe it has been set somewhere else as well. You can try changing the "Header" value see if it changes.

It is not likely. we need you to confirm this before we can start investigate, it might be something else. Try something like #deny from all which can be easily told working or not and not affected by something else.

I guess so.

We tried similar configuration at vhost template level, still works. I think the problem is that, for some reason the "open_basedir" configuration has not been applied at all, not that $VH_ROOT does not get expanded. How about the $VH_ROOT in "error_log" configuration?

Where do you use the variable for? server level, vhost level, vhost template. We tested vhost template, seems work well.

You should try increase the memory limits and process limits for the lsphp external app. And it is a good idea to keep PHP, APC and LSAPI updated.

The expires header is only effective for static file, not for dynamically generated content, you need to add those headers in your PHP script.

You can set expires configuration from LSWS web console. http://www.litespeedtech.com/docs/webserver/config/general/#expiresByType The expires setting is associated with MIME type configuration, just like "GZIP" settings, so the MIME type must exist globally.

It should work. Just that you may need to define the MIME type in the server level MIME configuratin.

Does it mean $VH_ROOT never worked? We need to know which version works if there is so we can track the code changes.

Maybe a bug in PHP opcode cache?

It should not be. Which version you upgrade from? Tried switch back?

I believe PHP crashed during processing this request. Maybe due to missing PHP module, or a PHP bug. changing LSWS is not likely be able to fix this problem unless this request use a lot of memory and the memory limit for PHP process is relatively low. You may need to find a way to strace the...

No, you need to count connections in "ESTABLISHED" state only.

Those are normal. "borken pipe" is the result of error code EPIPE, just another way to say that peer has closed the connection.

http://www.litespeedtech.com/support/forum/showthread.php?t=1883

That's the part I cannot agree with the point I mentioned earlier, suPHP should be 200% or better scalable than suHTTPD, it debatable with different workload, I will skip that, just for typical shared hosting situation, many web sites are just static.