Search results

  1. M

    license update delay?

    Usually update in one day, but you can make it update immediately with /usr/local/lsws/bin/lshttpd -V or /usr/local/lsws/bin/lshttpd -r
  2. M

    [Solved] pipelog problem

    It is a permission problem with /usr/local/psa/admin/sbin/pipelog try "chmod 0755 /usr/local/psa/admin/sbin/pipelog"
  3. M

    OS X Lion

    thanks for the update. :)
  4. M

    htpasswd auth

    We tested it against 4.1.3 release, it works fine in our lab. Have you tested 4.1.3? If it still does not work properly with 4.1.3, the best way to address it is to login to your server and take a look.
  5. M

    Error No input file specified.

    If you have fine tuned any configuration, I recommend you to revert back to default. Or, reinstall LSWS by following the tutorial in our wiki, it should work, if still have problem, please contact bug@litespeed for assistance.
  6. M

    Virtual Host not accessible with correct password for security

    Likely a file permission issue with .htpasswd file.
  7. M

    htpasswd auth

    OK, looks a bug in 4.1.x release. We are at the hostingcon now, will address this issue next week. Yes, change "Debug Level" to "HIGH" will give full debug log, by default, debug logging is disabled at "NONE" level.
  8. M

    htpasswd auth

    You can try enabling debug logging, also try an older release like 4.0.20 see if it is a bug introduced in 4.1.x.
  9. M

    [solved] LVE not working with LSWS 4.1.3

    We tried in our lab, looks fine. Is PHP running in suEXEC mode? "PHP suEXEC" must be turned on. Please check /usr/local/apache/logs/stderr.log for LVE related errors.
  10. M

    [Solved] APC Running but not working more than 0 minutes

    increase http://www.litespeedtech.com/docs/webserver/config/extapps/#extMaxIdleTime to make PHP process stay alive longer.
  11. M

    [Solved] APC Running but not working more than 0 minutes

    You may need to disable PHP suexec as APC is fresh for each new PHP process started. Please search on the forum, have been discussed for too many times.
  12. M

    How do I change the write name and group after install?

    You can give it a try, permissions of some files under lsws/ directory need to be changed as well, after changing it, you need to do a manual upgrade from command line, it should fix those permissions. If you messed up, just do a reinstall.
  13. M

    [Solved] shell php

    You should only change permission of public_html, files and directories under it should be world readable.
  14. M

    [Solved] shell php

    maybe you were not running LiteSpeed as nobody user, you may need to reinstall litespeed if that is the case. The permission mask has to be 0750, you need to figure out what else causes the 404 error.
  15. M

    [Solved] shell php

    you need to check the permission of public_html folder then. It should be owned by "user:nobody" with permission mask of "0750", only user and nobody group can access anything under public_html.
  16. M

    [Solved] shell php

    Can you check which user ID that shell PHP run as ? add "id" output. It should run as user ID of a account that the PHP script belongs to when PHP suEXEC is enabled. However, if it is "nobody", then just like web server process, it could read files from all accounts.
  17. M

    Sudden Slow Performance

    You really need to look into what is the bottle neck of your server when it is slow. could be CPU, memory, disk I/O, network I/O. check top, iostat and dmesg.
  18. M

    [solved] SSI Problems Yet Again...

    Please do a force reinstall of 4.1.3, should be addressed now.
  19. M

    LiteSpeed Cache + Magento

    Right now use Magento with Litespeed page cache is easy, just turn on the private cache. Then add "/checkout/", "/wishlist/", "/customer/" URLs to "Do not cache URL". http://www.litespeedtech.com/docs/webserver/config/cache/#noCacheUrl
  20. M

    100% CPU after 4.1.1 upgrade from 4.0.20

    Please do "lsof -n -p <pid_of_100%_CPU_process>", we need to find out what is file handle 7. Please also do "kill -USR2 <pid_of_100%_CPU_process>", it turns on debug logging to help us identify the problem. Server level configuration, "Log Level" should be "DEBUG", "Debug Level" is "NONE".
Top