Search results

temp solution is simple, mount a RAM disk at /tmp/lshttpd , move swapping directory from /tmp/lshttpd/swap to somewhere else.

Those two warnings can be safely ignored.

add to our to-do list.

It will be fixed in our 4.x release.

Yes, you should use gzip, or disable compression for dynamic content.

It should work, enable rewrite logging with adding "RewriteLogLevel 9" to the vhost configuration section for that vhost.

Are you using cPanel? or other control panel? If use cPanel, just use "Build matching PHP" in LSWS WHM plugin. for building PHP through web console, you need to copy the PHP configuration options from a phpinfo() page produced with Apache. remove Apache specific options.

Does it happen to IE only? or other browsers as well? Do you have an aggressive anti-DDoS setting? Does your web site uses a lot of small images?

Make sure you have add the mapping to the right listener.

The script was contributed by silmak http://www.litespeedtech.com/support/forum/showthread.php?t=801 Maybe he already have a work around. You can try contacting him via PM.

Just change response.headers['X-Accel-Redirect'] = '/downloads/myfile.zip' to response.headers['X-LiteSpeed-Location'] = '/downloads/myfile.zip' http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed:wiki:feature:internal_redirect

Are you using PHP suEXEC? Litespeed does log PHP errors to apache error_log by default, maybe something wrong with php.ini settings. I can take a look at your server if you PM me a temp root login with detail information on how to generate a PHP error to log file.

It is recommended to update Apache with ezapache then build matching PHP binary. However, if you are a experienced sys admin, you can try "build PHP" function in our web console.

It might be overridden by configurations below where you insert it to. Try it in the <virtualHost ...> section for your vhost. or just use .htaccess at your document root.

Under attack, you can try connection soft limit 10, and hard 30. Dynamic Requests/second is 1 and static 20. Under normal condition, use your current limit.

The best way to deal with bot net is combine LiteSpeed with firewall like iptables, when you set connection soft/hard limit properly, litepseed will log those IP that reaches those limits, those IPs are mostly member of the bot net or people trying to abuse your server. LiteSpeed does block them...

http://www.webhostingtalk.com/showthread.php?t=690249

Can you show me your xcache configuration in php.ini? I think the memory limit for lsphp5 may be too low, so it cause 503 errors. For single large web site, it is better disabling PHP suEXEC. Test LiteSpeed on another port with an Apache port offset, make sure xcache is working then switch to...

Maybe the memory limit for lsphp5 external application has been set too low, when xcache is used, people usually set the cache memory size to a large memory block, so, adjust the memory limit for lsphp5 external application, make it higher than the cache memory configuration for xcache in php.ini.

set log level to "INFO".