Search results

What kind of session storage are you using? Maybe there is a permission problem if file based session storage is used. Can you please check the cookie value with Firefox LiveHeader, see if the value changes for every request? Thanks.

Thank you for the update, we will release LSWS 2.2.2 and ruby LSAPI 1.8 soon.

Sorry, made another mistake again. Fixed, please download the package again.

We made a mistake when building admin_php binary, admin_php dynamically linked to libjpeg.so, we updated the binary with static linkage to libjpeg.a, you can download 2.2.1 package again, the problem should be fixed. ~/lsws-2.2.1 is where the installation package expanded, you can remove it...

You are right. I overlooked that it is "HEAD" request. We will change it to follow 404 handler. As HTTP protocol requires that a HEAD request should return the same status code as a GET request. Thanks for the bug report. :)

That's all right. When there is no index file in the public folder, LSWS will forward the request to Rails application for processing, if there is a routing error, rails will output a routing error page. What is output for the same request when WEBrick or Mongrel is used? Is .htaccess support...

There is no error when the TCP socket backlog is not full, user's browser just waiting for next available connection, usually, TCP socket backlog is >100. When backlog is full, user will get connection errors. Very easy, just run the installer and select upgrade.

Are you using the root directory of the Rails app to configure the Rails context? Do not use the path to the public/ folder. Any configuration warning or error in the error log? Is there a index file under public/ folder? Is the name of the index file added to the list of "Index files"...

You need to customize the template to enable awstats support. please make sure the vhost create its own log file. The current web admin console does not allow blank value for "Site Domain", you can try "$VH_NAME" there.

Maybe your rails app uses a lot of memory for those SQL, try increasing the "memory limit" under "Rails" tab, see if it helps or not. You should be able to find some clues for this problem in lsws/logs/stderr.log, lsws/logs/error.log as well as Rails' log files.

No, I did not. You need to download ruby-lsapi-1.8 package and install it again and add an environment variable "LSAPI_PGRP_MAX_IDLE=xxx" under "Rails" tab to tell the ruby process to quit, the value should match "max idle time" value under rails tab.

OK, caught the bug on jp_n9's server, it only happens when ruby processes are started in suEXEC mode, user id is different from that of web server, and "max_idle_time" under "Rails" tab has been set. When there is no request to ruby process for "max_idle_time", LSWS will try to kill this...

The log shows that the request for "/quizzes/12" failed when LSWS is used. Only get "200 OK ..." line, other header lines are missing. You can try this request directly, without redirection, redirection is working fine. Take a look at how this request being handled by rails, and anything...

"Max CGI instances" does not matter. If possible, please PM me temp root access and admin for LSWS web interface to your server, I'd like to take a look.

No, it is not. The resource cost is number of file descriptors, no need to worry about that. "300" is the max value for the current standard edition, which is enough for pretty large website.

They are not related. "Max connections" under "Tuning" tab is the maximum connections that LSWS can handle. All active connections included. "Max connections" under "Rails" tab is the maximum number of connections that LSWS uses to communicate with backend ruby engine.

OK, that's a good idea, we will use the same size limit of the access log file.

[SIZE=1]

To be safe, do "gem uninstall ruby-lsapi" to make sure the gem version is removed.

The problem should be mainly in gem package will be available when we officially announce this release. Yes, packages installed via gem and setup.rb may interfere with each other, remove the other one when switch the package. I think the gem one may has lower priority, not 100% sure. Be...