Search results

That's because PHP process exit after serving previous request. LSWS will try another PHP process. As long as there is no "oops, 503", it is fine.

If you use LiteSpeed with Apache httpd.conf, you just use the "ErrorDocument" directive to set your error page.

You need to open port 7080 with your firewall.

I think the vhost was configured not to allow symbolic link, since the owner matches, it should not be a problem if symbolic links are allowed. I can login to the server to take a look at this issue if you want.

Your app works fine in our lab. So, it must be your local environment. Please double check the RailsRunner.rb against the one in our installation package 4.0.2 Check if there are multiple version of Ruby installed and the correct one has been used.

I think an App generated by Rails 2.3.2 is likely to break with 2.2.2. I only care about the result with 2.3.2. If the app can be easily packed, please send it to bug@... , we can try it in our lab.

It does not looks right. Better trace individual calls with strace -tt -T -p <pid> You can get a clue about what is going on as well.

The parent process of lshttpd running as root is responsible for log rotation, so, if it happen next time, please "strace" that lshttpd process, it should do "stat()" regularly on all log files, and try to do a "rename()" if file size is over the limit. Might be something wrong with that process.

If it complain about missing some libraries, just try installing the <libxxx>-devel rpm with yum.

try yum install curl-devel or install libcurl or libcurl4 for your linux distribution.

There is a solution with using suhosin http://www.webhostingtalk.com/showthread.php?t=600238

First of all "enable_functions" does not exist, http://us2.php.net/manual/en/ini.list.php Second of all, if it was available, it wont be able allowed in .htaccess, just like disable_functions If PHP can have that function with Apache, there is no function had ever been disabled with Apache.

It is OK to have it at "4". Check the number of PHP processes running. You can try disabling ea cache temporarily see if the high CPU usage PHP process goes away.

Maybe there are too many running PHP processes cause high memory usage. Set "Max Idle Time" to 10. http://www.litespeedtech.com/docs/webserver/config/extapps/#extMaxIdleTime better not using /home1 , it will cause high I/O load.

You can strace the PHP processes that uses a lot of CPU, if it is from one user, maybe you should check the script from that user or just ban that user see if it helps. It might be a bug in eaccelerator, so, clean /dev/shm before it is full.

You can find out how much memory reserved by those loaders from phpinfo() page and reduce it with php.ini .

Does your app run properly under 2.3.2 with mongrel or webrick? We tried the default rails app generated with 2.3.2, works fine.

Latest 4.0.3 build allow you to configure a audit log via Apache Style configuration at server level. Just change the version number in the download link to get it.

should have take care of the missing .htaccess under docroot scenario in the latest 4.0.3 build. You can give it a try.

We will have it ready sometime in May.