Search results

LiteSpeed Web Server 4.0.13 has been released Download LiteSpeed Web Server View Version History It is highly recommended to upgrade to this release.

We have not heard any feedback on eAccelerator 0.9.6 yet. Assume it is better than 0.9.6-rc1. Please give it a try and let us know.

That's caused by random crash by PHP, there is no good solution other than trying different PHP version, turn off eAccelerator etc. As I know PHP 5.2.12 + eAccelerator is not that stable. Another thing you can try is to let lsphp5 dump core file, so, you can get an idea what is the problem in...

I did, do not change it.

Adjust the parameter a little bit, see if it helps or not.

Yes, you can do that.

The image is too small.

I think APC have file descriptor leak problem. Should upgrade APC.

Suhosin might be the reason.

ruleRemoveByID is not supported yet, so, the only option with LiteSpeed is to comment out those unwanted rules.

If eAccelerator is configured to use 256MB, the soft limit should be set above 512MB to leave 256MB for normal PHP usages. I think 600M should be enough by giving some head room.

/path/to/lsws/admin/misc/rc-uninst.sh

You can try a complete reinstall of 4.0.12, not sure what messed up the permission. Which control panel you uses? DA?

mod_rewrite is built in. You can use the exact same configuration as if Apache is used. RewriteEngine On is the directive. Turn on rewrite log, you will see what happened in the error log.

In the access log, 503 is the code, 400 is the response body size of 503 error returned. 503 error is caused by PHP crash, please take a closer look at error log and stderr.log for messages related to the 503 error. please post your lsphp5 external app configruation. Have you tried different...

You can turn on rewrite log by adding RewriteLogLevel 9 to the vhost configuration to enable rewrite logging, then you can check error log see what happened.

You can compare the phpinfo() output form apache fcgi PHP setup and LiteSpeed output, see if there is any major difference, you can compare the memory usage of PHP processes from ps or top output.

Maybe you added a opcode cache with LiteSpeed setup, opcode cache memory is counted toward the limit.

Any update? Is it OK now?

It should have something to do with PHP setup. Have you tried turning off eAccelerator? eAccelerator has no effect on Apache suphp, I guess that is the difference between LiteSpeed and Apache PHP setup. Seems eAccelerator is not very stable lately.