Search results

It might be a bug in APC, let PHP dump a core file, and check the core file with GDB, if need, submit a bug report to PHP. To let lsphp dump a core file, you also need to set environment variable LSAPI_ALLOW_CORE_DUMP in the lsphp5 external application configuration.

It is something impossible to me. :) Maybe you put phpinfo() at both place, see if it changes in the middle of the script.

Please try a manual upgrade, see if it the problem went away for later releases. Which OS are you using? 32bit? 64bit?

I thought you have found the cause of the high load is the high I/O wait caused by a cron job. You can try set "Max Idle time" to "5" to "10" seconds. http://www.litespeedtech.com/docs/webserver/config/extapps/#extMaxIdleTime It should help release unused PHP processes, give more memory for...

remove "-b ..." option from command line, the socket will be created by LSWS.

The rewrite rule looks fine, you may have to "grep" for it. You should upgrade Apache's PHP with easyapache before upgrade LiteSpeed PHP. You need to switch back to Apache before running easyapache.

Please PM the IP of your server. we will check if the trial has been blocked because it has been over 30 days since the first try.

408 error is because a request take too long to process, you may want to increase http://www.litespeedtech.com/docs/webserver/config/tuning/#connTimeout

How long have you been using the trial key? If you have used the trial key 30 days again on the same server, it wont allow you to use it even you get a new trial key.

check your cron job, if it happen every day around the same time, it must be some batch job use too much system resources, causes high memory usage or high I/O load.

A PHP script executes "file" commands with wrong parameters.

With suEXEC PHP, each PHP process has its own cache memory, it wastes a lot of memory if many PHP process running. It is true for all opcode caches. eAcc store cache on disk, we thought it is a good idea to put the disk cache under /dev/shm, make it effectively an in memory cache shared by all...

You should upgrade to 4.0.2 or try the 4.0.3 manually.

It should work fine with standard edition.

If you configure vhost natively via web console, you can create a static context pointing to the directory that the symbolic link points to. That's the only way to allow accessing file outside vhost root when "Restrained" is set to yes.

Yes, it is available in Standard edition.

Max Obj Size of 1024 is too small I think. If a page larger than 1K, LSWS will not cache it. Cache Expire time should be shorter, start from 1-5 minutes, just in case that some page should not be cached was cached. If you use cPanel, you should rebuild Apache with mod_cache support, then go to...

We will change that log entry to INFO level, so it will not show up when log level set to NOTICE.

Answers to your questions: a) better put the cache directory to a dedicate disk, you can create the cache directory any where you want. b) It really up to you, and adjust based on your site, maybe start from 500KB. c) If you configure vhost natively, you can set that option at different level...

Please try the latest 4.0.3 build by changing the version number in the download link.