Search results

  1. M

    Core file after upgraded to 3.3.5

    PM me is fine.
  2. M

    Core file after upgraded to 3.3.5

    I may need to ssh to the server and take a look. If lshttpd crash, it should create core file under /tmp/lshttpd/bak_cores, not the root folder. Maybe PHP crashed.
  3. M

    Running lsphp standalone

    Yes, it will be your responsibility to start and monitor the lsphp processes though.
  4. M

    Can see web sites in litespeed with Lxadmin

    You can manually move the <VirtualHost ...> section up in front of those catch all vhosts.
  5. M

    503 error, rails not running

    PWD should not matter. You can remove that. It does not looks like those should affect your rails app. Can you confirm that you run rails in the same mode, under LiteSpeed and WEBrick? WEBrick default to "Development".
  6. M

    503 error, rails not running

    That's the only place you can set env for rails.
  7. M

    503 error, rails not running

    You need to check variables set in your current shell environment with command envAdd all of them see if it help, then strip one by one.
  8. M

    503 error, rails not running

    This error has nothing to do with ruby-lsapi. Maybe you need to explicitly add "LD_LIBRARY_PATH" environment variable under "ruby rails" tab in order for rails to find the missing library? LSWS only set "PATH=/bin:/usr/bin" environment variable, all other shell environment variables are...
  9. M

    LiteSpeed Web Server 3.3.5 has been released

    PHP LSAPI has been updated, so, it is recommended to rebuild your PHP binary, either manually or through the web GUI provided.
  10. M

    503 error, rails not running

    http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:rails:troubleshoot
  11. M

    Upgraded to 3.3.5 Issue

    That page loads fine with my firefox on Linux.
  12. M

    Just converted from apache to litespeed

    Please PM me the login to LSWS admin console.
  13. M

    Failed to execute 'vmstat' command?

    never mind, that is just for pulling server status, vmstat has not been installed on your server, this has no harm and not related to Rails.
  14. M

    AutoUpdate not working?

    OK, the autoupdate has been triggered. :)
  15. M

    killed with SIGTERM, 3-4 times a day

    Thanks for the confirmation. :)
  16. M

    Best configuration for DDoS protection?

    Anyway, you should go with Enterprise edition if you host more than 3 websites on it. Standard edition won't work. Just take a trial.
  17. M

    Just converted from apache to litespeed

    Please check LSWS error log, see if anything abnormal.
  18. M

    Just converted from apache to litespeed

    No, just do a upgrade on top of it.
  19. M

    Feature Request : Seperate ModSec Error log File

    No, a dedicate mod_security audit log will be created, and the log entry in it should make CSF happy. Yes, you need to download 3.3.5 again.
Top