Search results

  1. M

    new package has some bad installation problems

    Please send your server IP and serial number to support. we will investigate.
  2. M

    shows logs on high load

    I think so, no problem reported with 4.0.11 yet.
  3. M

    lslb split workload

    Just assign different value for "Max connections" to the different backend, like "60" connections to server1, "40" connections to "server2", LSLB will use that as "weight" for different backend.
  4. M

    [AutoUpdate] Failed, updateagent exit code: 3

    should be fixed by now. a glitch when we migrate to a new server.
  5. M

    Possible to have multiple servers to spread the load?

    Not sure you are asking about a cloud solution or just want to spread load among multiple lshttpd processes (n-cpu license) in one server. If you want a cloud solution, you have to use shared storage.
  6. M

    PHP problem

    allow user "lsadmin" to write to "/home/litespeed/dominios/domain.com/conf/"
  7. M

    Building PHP fails on 4.0.9

    Just patch the phpbuild code under utility directory, grep for 4.9, replace to 4.10.
  8. M

    PHP problem

    Maybe do a fresh reinstallation, the admin console should work properly. Try run /path/to/lsws/fcgi-bin/lsphp5 from command line see if you get any error.
  9. M

    litespeed stuck

    If I/O wait is very high, it may affect the lshttpd, please try "strace -tt -T -p <pid_lshttpd>" see what is going on. AIO in 4.1 will solve this issue.
  10. M

    open_basedir error with DirectAdmin

    check phpinfo() page for the open_basedir configuration. adjust the configuration in apache httpd.conf or php.ini. If you used apache with suphp, open_basedir never worked.
  11. M

    408 request time-out

    maybe caused by something else. check max_post_size and file_upload_size, etc in php.ini If it can be reliably reproduced, we will take closer look.
  12. M

    408 request time-out

    upgrade to 4.0.11
  13. M

    408 request time-out

    http://www.litespeedtech.com/docs/webserver/config/tuning/#connTimeout
  14. M

    LSWS Rails App MySQL Connection Errors

    Updated the code, thanks!
  15. M

    Symlink not match?

    You have to allow symbolic link in your LSWS configuration. Only the error message uses a wrong path, the wrong path is due to failed symbolic check, when it passes, there is no problem.
  16. M

    LSWS Rails App MySQL Connection Errors

    if "RAILS_GEM_VERSION" >= 2.3.0, new code with the rack adapter is used, otherwise, the older version of railsrunner is used. new code uses "ActiveRecord::Base.connection_handler.clear_active_connections!"
  17. M

    Trial key

    Thanks for the bug report. Fixed.
  18. M

    control php value in .htaccess

    Which control panel are you using? Have you checked a phpinfo() page?
  19. M

    control php value in .htaccess

    It should work unless you turn off .htaccess. That's one main advantage that litespeed PHP solution over others like suphp or fastcgi PHP.
  20. M

    Using Ruby on Rails with LSWS Enterprise 4.0.11?

    Can it be fixed by restarting LSWS? LSWS resolve symbolic link when read configuration, but does not update the link if changed. Will have it addressed in 4.1 release branch.
Top