Search results

Which log file do you refer to? The real status code has been logged into access log. There might be "File not found" logged in error log, but you can safely ignore that.

Parent lshttpd does not forward file handler to children lshttpd prcess for access.log and error.log when a log file has been rotated. access.log should be owned by lsws:lsws, and user 'lsws' should have permission to open a file for under directory '/srv/www/logs', so "0755" permission mask...

All files can be owned by the rails user or only let a few directories to be owned by rails user to give better security. When LSWS start a Rails app in SuEXEC mode, it uses the owner of public folder, so, you can create a user for each of your rails application if you want, and you need to...

Yes, it is intentional. LSWS does on-the-fly log file rotation, it requires a child lshttpd process to reopen log files for writing, the log file owner will be changed to the user that web server running as. The log file will only be created by the parent web server running as 'root' then...

POST method is not allowed for a static file, if annual_2.html is really a CGI script, you need to change server configuration to make it being handled as a CGI script, either use a CGI context or script handler configuration.

Please follow our step by step Rails configuration http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:ruby_rails In step 5: instead of using "RubyRailsLSAPI" directly, use the load balancer.

Thank you for your praise. :) Anaswers to your questions: 1) Yes, it is a reverse proxy. 2) You can do that, but you cannot use the easy configuration, have to do the step by step manually configuration. 3) "rails context"'s lsapi configuration is added behind the scene, you cannot reference it...

Sorry, my bad. Glad you figured it out. :)

Please uninstall the ruby-lsapi gem then try http://www.litespeedtech.com/packages/lsapi/ruby-lsapi-1.9.tar.gz, It is recommended to install ruby and gem manually from source if 1.9 does not work with your rails installation either.

Sorry about that. :) Sometimes we did that when a non-important bug fix comes up just after a new release was announced, and that bug should not affect most users. We knew it is not a good practise, we will try not do it very often and give it a new release number when possible. ;) If you...

I cannot reproduce the problem you described. :( Are you using LSWS 2.2.2? When MaxIdleTime is not zero, LSWS can start new ruby process and respond correctly in our lab. If you want to bother, you can "truss" those ruby processes and turn on LSWS debug logging, to check exactly what was...

That's because your test script is not right, if run from command line, it outputs nothing. You need to add a response header and output the html generated by markaby. The script should be like this for a simple CGI: # the script require "rubygems" require "markaby" puts "Content-Type...

You probably need to clear your browser cache, index.shtml might be cached when the proxy has not been properly configured. Listening on localhost will not cause 503 error, you need to make sure that localhost:8080 is working properly at Apache side.

That's great! I think it is alright, as long as nobody group has no permission to access all users' directories, one user will not able to peek another user's file.

I think php may not able to locate apc.so. What I would do is to copy apc.so to lsws/lib, then change /opt/lsws/conf/php.ini to extension=../lib/apc.so

Got anything in lsws/logs/stderr.log?

You need to define a "Web Server" external application for the target web server. Then define a "proxy" context with URI "/directory/", select the external application just defined as handler. All requests to http://domain.com/directory/ will be forwarded to the destination server without any...

Finally got markaby installed, have to do "cd vendor/plugins; svn co http://code.whytheluckystiff.net/svn/markaby/trunk" , "script/plugin install ..." does not work. And it works properly inside a controller as well as .mab file in view folder. BTW: ruby-lsapi 1.9 has been updated, please...

Please give http://www.litespeedtech.com/packages/lsapi/ruby-lsapi-1.9.tar.gz a try, your problem might be fixed already. :)

ruby-lsapi 1.9 has been updated to make the request parameters match WEBrick and Mongrel more closely. Give it a try. :)