Search results

  1. M

    Failed to generate the realtime reports!

    PHP_LSAPI_CHILDREN is ignored when PHP suEXEC is used. http://www.litespeedtech.com/docs/webserver/config/general/#phpSuExec
  2. M

    Failed to generate the realtime reports!

    your PHP processes is constantly allocate more than 200MB memory, you need to find out what causes it doing that. Maybe other opcode cache or loader, should reduce the memory usage.
  3. M

    Failed to generate the realtime reports!

    16mb should be fine. you need to find out which process responsible for the swap usage. monitor the usage of /dev/shm with command "df", I think it should be cleaned more frequently.
  4. M

    Disable log rotation

    It should not be a problem any more with the latest 4.0.3 build.
  5. M

    Pre Sale Confusion

    You will be rewarded for your help. :)
  6. M

    Failed to generate the realtime reports!

    Your server start to use swap, that's why you get high load. your PHP opcode cache size is a bit high to me, since eaccelerator uses /dev/shm, there is no need to set opcode cache too high. Also, make sure the /dev/shm got cleaned regularly.
  7. M

    FollowSymLinks and SymLinksIfOwnerMatch

    There is no way to prevent a user running a perl script to create a symbolic link pointing to another user's file, unless you want to disable perl completely. However, does not like Apache, 4.0.3 enforces "SymLinksIfOwnerMatch", nobody can override it via .htaccess with "Options +FollowSymLinks"...
  8. M

    Pre Sale Confusion

    Thanks. fixed.
  9. M

    Pre Sale Confusion

    It is 500 for VPS license.
  10. M

    Pre Sale Confusion

    Yes, the lshttpd in VPS edition uses 1 CPU. should be fine for a VPS, give it a try.
  11. M

    htaccess & php[45]-script

    Make sure it does exist. You can try that command from command line.
  12. M

    Failed to generate the realtime reports!

    If /tmp/lshttpd/swap use too much disk space, consider moving "Static GZIP Cache Directory" http://www.litespeedtech.com/docs/webserver/config/tuning/#gzipCacheDir
  13. M

    Failed to generate the realtime reports!

    Just do killall -9 lshttpd then try restart LSWS see if it fix itself.
  14. M

    Failed to generate the realtime reports!

    I think it is safe to remove PHP session files, and /tmp/lshttpd/swap
  15. M

    Failed to generate the realtime reports!

    /tmp is full I think. clean it up.
  16. M

    4.0.2: web server with pid=xxxx received unexpected signal=11

    Yes, you should download the enterprise version, however, the bug may not be fixed, please follow up with our staff to investigate your issue.
  17. M

    503 error with Rails 2.3.2

    Is there any Ruby processes get started? Anything in Rails logs file? LSWS error.log and stderr.log? 4.x comes with a new RailsRunner.rb to support Rack, if you revert back to 3.3.24, you should copy over the old RailsRunner.rb, but 3.3.24 wont work with Rails 2.3.2 , only earlier Rails releases.
  18. M

    htaccess & php[45]-script

    I am talking about the script handler configuration in LSWS console, not whether .php4 scripts are processed by PHP4 or PHP5. It is controlled by the "AddType" directives you mentioned. You have to have a script handler defined for "php4", so LSWS will know that MIME type...
  19. M

    Command Line Restart of Individual Virtual Host

    LiteSpeed can start individual Rails application configured this way. http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:rails_hosting Or, just kill those ruby process belong to one user if Rails start in suEXEC mode.
  20. M

    htaccess & php[45]-script

    You have to have a "Script Handler" for "php4" defined at server level from LSWS web console.
Top