Search results

  1. M

    Server load same after switch to litespeed

    You cannot use xcache together with suEXEC, it is not efficient as each PHP process creates its own cache memory. You can try eAccelerator with cache storage in /dev/shm/, but some user experiencing some PHP compatibility issue. Should turn off the optimizer in eAcc. You can search related...
  2. M

    Can't login LS 4.0.3

    That happened before, run of out of disk space will cause that.
  3. M

    High CPU load with Litespeed 4.0.3

    You can "strace" the lsphp process keep using a lot of CPU cycles. strace -tt -T -p <pid_of_lsphp>
  4. M

    Remove LSWS from Autostart

    lsws/admin/misc/rc-uninst.sh
  5. M

    bak_core folder

    you can try a symbolic link.
  6. M

    Easy switch from apache to litespeed and opposite

    If you use cPanel, we have a WHM plugin can do that easily. Otherwise, you can have do it from ssh shell.
  7. M

    Server Load!

    Looks like PHP processes are going into a infinite loop or some thing very CPU intensive. CPU idle is 0 percent try strace the PHP processes on top of the "top" output do to find out what is the PHP process doing.
  8. M

    Server Signature

    add your own 403 page.
  9. M

    Having issues after upgrade to LSWS 4.0.3 and Rails 2.3.2.1

    Looks like your application does not run well with RailsRunner.rb. Please try a blank Rails application with Rails 2.3.3 see if it works.
  10. M

    Turn off buffering!?

    It is not possible now. You need to slow down your PHP script if you want to.
  11. M

    cPanel/WHM build matching PHP binary issue

    Yes, the plugin will upgrade if there is.
  12. M

    how to use suexec with apache conf. and cPanel?

    No need, just set "PHP suEXEC" to yes. http://www.litespeedtech.com/docs/webserver/config/general/#phpSuExec
  13. M

    Server Load!

    Please post your "top" output when load is high.
  14. M

    Problem with sort_by{rand}

    if you upgrade to ruby-lsapi 3.5, you do not need to call srand()
  15. M

    Having issues after upgrade to LSWS 4.0.3 and Rails 2.3.2.1

    just select "staging".
  16. M

    Turn off buffering!?

    It is not possible, LiteSpeed is designed to buffer the response body and make PHP process available for next request as fast as it can. Please read more about "External Application Firewall" on page http://www.litespeedtech.com/litespeed-web-server-features.html
  17. M

    cPanel/WHM build matching PHP binary issue

    It should read like "or different in (current) lsphp". Yes, go ahead, lsphp will be updated to match exactly the options used for Apache php.
  18. M

    symbolic link does not work in 4.0.3

    Use "chown -h <user> <path>" to make the symbolic link the same ownership of the link target.
  19. M

    Failure to compile ruby-lsapi on LS4.03/Ruby 1.9

    For Rails, Ruby 1.8.7 is recommended. We will test it on ruby 1.9.1 .
  20. M

    Having issues after upgrade to LSWS 4.0.3 and Rails 2.3.2.1

    If you use "Rails" Context, it will be using lsws/fcgi-bin/RailsRunner.rb , The dispatch.lsapi wont work with Rails 2.3.x .
Top