Search results

You can try increase the memory limit for lsphp5 external app. Maybe your user were trying to process a large file? Also check /usr/local/apache/logs/stderr.log for related errors.

should be under the directory where PHP script located. To get a core dump, you need to check and enable core dump with ulimit -c if it return 0, core dump is disabled. ulimit -c 100000 will enable it. then need to stop then start LSWS.

Once you got the core file, just run gdb <path_to_lsphp5> <core_file> then type command bt to list the call stack.

Which version of PHP is used? Maybe you can try downgrade PHP version. How about Apache mod_php? will APC or Xcache crash it? The problem is between PHP and opcode cache, you can try to let lsphp5 dump core file and exam the core file with GDB. To let lsphp5 dump core file, you need to add...

The latest 4.0rc1 build should be able to take care of the <DirectoryMatch...> configuration.

Since you do not use PHP suEXEC, you can try strace the parent lsphp5 process with command strace -f -p <pid_of_lsphp5> when you get 503 errors. It can give you some hints on why PHP crashed for some reason.

Maybe you have set process limits of lsphp5 too low? check how many lsphp5 processes do you get? I think for some reason, APC crashes PHP, maybe look into other cache solutions like eAccelerator or xcache.

You should use LAN for DB connection. always use the fastest available connection.

Are you using a VPS? What is the cache memory size for APC in php.ini? maybe you need to reduce the cache memory size, especially when you use PHP suEXEC. Maybe you should disable PHP suEXEC if you use VPS to host a few web sites, not for shared hosting.

Please check if it is a permission problem for "curl", "wget" binary. Make sure to give execution permission to the user that LiteSpeed run as.

Should be able to, give it a try.

LiteSpeed pre-compile <location...> <Directory...> directives, this <directoryMatch ...> directive is intended to match document root directory of all web sites, so it will match all requests and causes other "...Match" directives being ignored as LiteSpeed always use the first match. The...

The latest 4.0rc1 build should have addressed the double/triple posts problem.

Do you get anything in stderr.log?

Yes, it is fine.

Just do a upgrade like normal, no reinstall. For lease license, upgrade is always free. Owned license's update has not expired.

LB cannot reach the second server.

Make sure to enable the cache with Apache mod_cache directive CacheEnable ... Some site like vB, does not allow page being cached.

It depends on the LB configuration. LB may not route traffic to second server when all traffic comes from the same IP. You should use "stateless" and "Round Robin" to make LB route traffic to second server.

Thanks! Fixed.