Search results

We will change log level for those log messages to DEBUG

http://www.php.net/manual/en/filesystem.configuration.php#ini.allow-url-fopen

Pinned thread http://www.litespeedtech.com/support/forum/showthread.php?t=1660

No, LiteSpeed does not support mod_axis2, however, the CGI interface is available, you can use it for low volume application. If Fast CGI interface is available, it can be used for high volume application.

Ask your DC to help on this. Maybe clock on host machine need to be synced.

If it can be reliably reproduce we can login and check the server if you want.

If it does not happen frequently, you can ignore it. LiteSpeed will immediately recover from crash.

check the session storage folder permission. Make sure LiteSpeed setup match Apache's security model, if suphp is used with Apache, enable LiteSpeed PHP suEXEC, otherwise turn it off.

Checked the server, looks like it is a disk quota issue. mailman log complains about disk quota. This error only happen to one mail list, not a system wide problem, Apache does not show this problem, the reason I guess is, litespeed run mailman script in suEXEC mode, while Apache run it as...

please download again.

Please download and update to 4.0.14 release. You can get it by changing version number in the download link.

That's pre-built PHP binary + some other commonly used components, in order to use Litespeed, you need to build your own binary, so you cannot use it directly. However, I think might work fine if you replace the PHP binary with your own custom built one.

Please download and update again, should be addressed.

LVE is detected. Are you using PHP suEXEC? right now, only PHP in suEXEC mode put into LVE.

DataOne has positive feed back on this. Anything in the stderr.log, if LVE detected, it will log something into stderr.log.

throttling is only enabled when serve level configuration is set. You can set server level throttling to a large number, then lower it at vhost level if need.

If it happen repeatedly, please contact bug@litespeedtech.... for instruction on using debug build of LSWS and "strace", "gdb" to help identifying the issue.

You may have to use rewrite rule to check referrals and add exceptions in the rule. The built-in "hotlink protection" wont be able to do what you need.

I believe you have tried to use the NULLed LSWS Enterprise, and got blacklisted.

OK, identified the bug and fixed in 4.0.14 release build. Please download and try 4.0.14 by changing the release number in the download link. i386-freebsd6 and x86_64-freebsd6 packages are available.