Search results

Rails may not behave exactly the same due the differences I mentioned earlier. You can strace WEBrick as well and compare the output. Actually, it is a good way to trouble shoot this kind of problem.

It confirms that Rails is handling the request, LSWS just relay the response from rails. You can try killing all ruby processes, so if a ruby process cache the rhtml, it will be flushed when next request comes in and LSWS start another set of ruby processes. To find out what happened in...

It wont work as the LSWS also limit the size of response header, see the tuning tab of server configuration. So, even this LSAPI limit being lifted, it wont pass the next checkpoint. LiteSpeed is not friendly with script produce large response headers.

Please try the trouble shooting tips at the end of the wiki http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:php:lsapi

Check access log file to see if a request has been received should be easy enough. No, LS does not and could not prevent some one to overwrite a file. The fact is that LSWS does not open those "*.rhtml" files, not even aware the existence of those files. If you want to have this problem...

Answer has been given. LSWS run Rails in different way, including suEXEC, process memory limit, fork children process, limited environment variable passed to ruby process, etc. those difference could make Rails behave differently. We cannot help you if you do not follow our instrcution to...

Anything abnormal, errors, exceptions. I don't have an answer due to insufficient information available. You have to check those log files.

LiteSpeed Load Balancer 1.4 has been released Download LiteSpeed Load Balancer View Version History

It is more likely a permission issue as LS start the backend in suEXEC mode. Or a process memory limit issue, you have to check Rails log and LSWS error logs to find out why.

If LS cache the response for previous request, it will not forward new request to rails, just reply with cached result. If LS forward a request to rails, LS will just relay the response from rails. There is no third possibility. LSWS still serve requests exactly the same way during a graceful...

If a request go though Rails, LSWS is just a messenger, so check the development.log see if the request hit rails.

Whether it is a LS issue or not depends on whether the request being forwarded to rails, or LSWS serve it by itself, or the browser cache it. You should check rails log and LSWS access log.

/opt/lsws/bin/lshttpd -V

you missed PHP mysql module

I am not talking about your language, but your attitude towards using the support service. The previous problem you asked us to fix turned out it was not a LiteSpeed issue, same is this one. We try our best to serve our customers well, but we cannot afford to satisfy all demands despite the...

You have to have your admin to take a look at it. LiteSpeed will not restart hourly by itself, period. Something external request LiteSpeed to restart regularly. Since you are renting a managed server, it is the server admin's responsibility, even though, from past experiences, seems you have...

Maybe it is control panel restart LSWS every hour. You should be able to find out something form log files. LSWS restart is graceful, it is not likely to affect your web site anyway. It is a general server admin issue, not a LiteSpeed bug, we can only take a look if there is support service...

lsws/bin/lshttpd -V

Looks like a permission problem with your "gcc" "ld" executable. check the permission of those files. do chmod 755 /usr/bin/gcc chmod 755 /usr/bin/ld after finish compilation, change it back. If you are using cPanel, you can use the WHM plugin to compile PHP.

Please send your httpd.conf to us for investigation. You can safely ignore this error for now.