Search results

It is cause by a bug in our lscgid, when php started in suEXEC mode. the fix will be in 3.3.5 release.

delete it in a cron job, and you can set log level to ERROR. check the error log, if those are PHP errors, you should fix your php code.

You can remove those log files.

There is one more place need to be changed, so the default rails configuration does not take staging, will be fixed, just override the environment in the specific rails context configuration.

try rpm -ql libjpeg-devel Then specify the path for libjpeg PHP configuration parameter accordingly.

try "ulimit -a", raise the memory then start LSWS. see if it helps.

You can ignore that warning message. has no harm when you use LSWS with Apache httpd.conf

It must be some mismatch libaries, not related to LSAPI. You can try build a CLI version, without lsapi.

I will check suEXEC.

No, VPS license only works in a VPS, not in a physical server.

Yeah, you can verify the limit by run "ulimit" from the PHP process. Try it from command line first. I think it may related to how it was handled by linux kernel. Try a strace lshttpd when it spawn a new PHP process, see if ulimit has been called. Are you using suEXEC?

I think it maybe related to ruby internal bugs, as I remember, there are bug related to popen() or other functions use fork() then exec(), if exec() failed, the forked children process does not shutdown properly.

Mono has FCGI support now, so it should work with LiteSpeed, just not when Apache httpd.conf was used.

If you stop Lshttpd then start it, it may take up to 30 seconds as the old lshttpd process need to finish all the lingering requests. You can either force lshttpd to stop by killing them with "-9", or always use "./lswsctrl restart" instead of "stop" then "start".

It is not possible to transfer httpd port from LiteSpeed to Apache, LiteSpeed does that during a graceful restart. Apache does not know how to take it. ;) LiteSpeed's watch dog process should never die and new instances should be started if a child process crash, the impact should be minimum...

Which OS are you using? The pcntl_fork() should fail when process limit has been reached. the code may still looping and waste CPU time, but it should not bring down the whole server. We will check.

If you upgrade PHP, you must rebuild Xcache, double check the directory for the extension if correct.

Which OS are you using? You may need to install LSWS with root user in order to lift the memory limit imposed by the OS by default.