Search results

  1. M

    litespeed doing "extra" compared to apache

    It could be redirect. You can check what happened with Firebug.
  2. M

    Mystery of processing photos?

    If you have a 32 bit vps, you have to use the 32bit LSWS. Please PM me a temp root login to your VPS and detail on how to reproduce the problem. I will check.
  3. M

    Error when build PHP

    better use different cache directory for lsphp4 and lsphp5. allowed_admin_path does not matter I think.
  4. M

    Mystery of processing photos?

    Is the VPS 64bit? If yes, you should try the 64bit enterprise with the trial key, if it works, then get a VPS license. If not work, I can take a look at it.
  5. M

    Mystery of processing photos?

    Looks like the ruby process crashed during processing a JPEG image. You can try increase the Memory Soft/Hard Limit and Process Soft/Hard limit under "Ruby" tab. Or, maybe rmagick require a special Environment variable, you can try adding environment variables in the "Environment" option. Can...
  6. M

    Catch timeout exception for Ruby LSAPI

    It depends on your web site and traffic volume. It should be good start point with Max connections 10 Initial Request Timeout 60 (If some request takes longer, increase it). LSAPI Ruby can be fine tuned via environment variables http://www.litespeedtech.com/ruby-lsapi-module.html
  7. M

    Error when build PHP

    Try again and make sure 4.4.9 is selected.
  8. M

    Catch timeout exception for Ruby LSAPI

    That's correct behavior. LSWS will try three times on a failed requests. The initial request timeout should be set high enough to allow Rails finish serving a request normally. It is intended for catching a runaway request. So, you cannot implement what you want via initial request timeout...
  9. M

    Clustering LiteSpeed Balancer

    Yes, two load balancers will work in a HA manner. We don't have tutorial on CARP + LSLB together. CARP is completely independent, you can google examples related to CARP setup. There is a third party tutorial about LSLB in our wiki.
  10. M

    Error when build PHP

    chmod 0755 /usr/bin/ld
  11. M

    litespeed control panel: domain stopped?

    If you messed up the server configuration and have no idea what is wrong, you should reinstall LSWS.
  12. M

    Setting $SERVER_ROOT

    You have to replace "~" with the real user home directory.
  13. M

    Random 404 pages

    For some reason, the first request was aborted. [LSAPI] send abort packet! Maybe something wrong with HTTP request from "Media Center PC 5.0" browser. The second request is successfully completed, just the status code has not been change from 404 to 200, the rails app does not set it. So, it...
  14. M

    Setting $SERVER_ROOT

    You can put your web site anywhere you want. you don't have to use $SERVER_ROOT for the vhost root. http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed:wiki:template
  15. M

    Setting $SERVER_ROOT

    $SERVER_ROOT is the directory where LSWS was installed to. usually it is /opt/lsws or /usr/local/lsws, it is fixed and cannot be changed via configuration. If you install LSWS to other directory, its value will change accordingly.
  16. M

    Clustering LiteSpeed Balancer

    Yes, you can setup a HA cluster with Common Address Redundancy Protocol (CARP) http://en.wikipedia.org/wiki/Common_Address_Redundancy_Protocol We have user doing this with FreeBSD + LSLB for HA solutions.
  17. M

    php

    Maybe it is a good idea to hire an admin to help you with the PHP setup if you have difficulty to follow our wiki.
  18. M

    SNMP + Cacti Install = initscripts problem

    you can try explicitly install those missing rpm yum install ethtool mingetty module-init-tools
  19. M

    Litespeed is not logging

    When used with a hosting control panel using Apache httpd.conf, LiteSpeed will not compress or rotate the log file, usually the control panel will do that while updating the statistics.
  20. M

    $SERVER_ROOT variable in error document

    OK, I know what is wrong, it is a misunderstanding, when you configure A "Custom Error Page", the path is a URL, not a file path. You have to set the error URL to "/404.html", then add a static context, equivalent to "Alias" in Apache, mapping "/404.html" to "/opt/lsws/404.html".
Top