Search results

  1. N

    conf/vhconf.xml is not a valid file AFTER upgrade

    if so, your way is ok and not a problem. just searched, a user(here lsadm) belonging to max number of groups is 32 or 16. if only 5 users, I think it's ok. please wait for our development's investigation result.
  2. N

    conf/vhconf.xml is not a valid file AFTER upgrade

    not sure, maybe you can refer Virtual Host Templates -> EasyRailsWithSuEXEC
  3. N

    conf/vhconf.xml is not a valid file AFTER upgrade

    I can reproduce the issue you reported on centOS: #groups lsadm lsadm : lsadm nobody user1 after upgrade: #groups lsadm lsadm : lsadm nobody and it can be fixed by change line 905 of functions.sh from usermod -G $WS_GROUP lsadm to usermod -a -G $WS_GROUP lsadm we'll estimate if...
  4. N

    conf/vhconf.xml is not a valid file AFTER upgrade

    what's the permission of conf/, conf/vhconf.xml ?
  5. N

    Editing php settings seems impossible

    check if it's overridden in .htaccess for example, php_value upload_max_filesize 2M
  6. N

    I'm behind SYN FLOOD with Spoofed IP'S

    can you identify which process has high CPU usage, by "top -c" etc? ddos usually last short time only, is your website DDOS'd continuously?
  7. N

    I'm behind SYN FLOOD with Spoofed IP'S

    maybe you can order "Advanced Anti-DDoS Setup" https://store.litespeedtech.com/store/cart.php?gid=5 we have some experience on anti-ddos and have succeeded on a lot user cases. but not 100% sure if it apply for your case as well.
  8. N

    403 error for save <SCRIPT> into file on the server

    may be not. try to ask your host to disable that rule. if that rule already disabled, then maybe mod_security plugin for cPanel has been installed by your host, that acts same as request filter but more powerful and complex.
  9. N

    403 error for save <SCRIPT> into file on the server

    it may trigger certain "Request Filter" rule. check lsws admin console->Server->Request Filter, disable "XSS attack" rule if it's enabled.
  10. N

    CSS style Problem

    ~>curl -I http://www.clip4u.org/wp-content/themes/clip4u_blue/style.css HTTP/1.1 200 OK Date: Mon, 04 Jun 2012 09:43:54 GMT Server: LiteSpeed Accept-Ranges: bytes Connection: Keep-Alive Keep-Alive: timeout=5, max=100 ETag: "5d2a-4fcc5fed-0" Last-Modified: Mon, 04 Jun 2012 07:12:45 GMT...
  11. N

    VERY BUSY Server Configuration - 800 Req/Sec

    the 2nd virtual host: WaiQ is 5. in this case, try increase Server->General->PHP suEXEC Max Conn current value looks to be 5. increase to 10 and watch real-time stats again.
  12. N

    [solved] Litespeed webserver stops working while cleancache script is runnning

    maybe bad sects under /tmp/lshttpd ? Please PM your server's access info, I'd investigate this strange issue.
  13. N

    [solved] Litespeed webserver stops working while cleancache script is runnning

    I think this is where the main problem is --- please fix it before trouble-shooting other issues. maybe hard disk has hardware problem.
  14. N

    [solved] Litespeed webserver stops working while cleancache script is runnning

    is the size of /tmp/lshttpd/swap big? #du -sh /tmp/lshttpd/swap
  15. N

    503 Error!!!

    please check error.log/stderr.log, grep "oops", there'll more detail about the 503 error.
  16. N

    [solved] Litespeed webserver stops working while cleancache script is runnning

    the default swap is /tmp/lshttpd/swap is your /tmp NFS ? it may be very slow per some of our past experience. if so, better to use local disk as /tmp also, please run iostat to check if some of hard disks have high i/o wait issue.
  17. N

    Web server automatically restarted - shows wrong version

    a full stop and start may resolve it, restart not working --- this is my experience on one or two servers. please try if it works for your case.
  18. N

    Is mod_mono compatible with Litespeed

    no. not support
  19. N

    [Solved] LiteSpeed is not up! Please check log file for errors.

    please note this info: [ERROR] Failed to find your license key under - /usr/local/lsws/ or /usr/local/lsws/conf/! either /usr/local/lsws/trial.key or /usr/local/lsws/conf/trial.key should exist otherwise, the trial version won't run. maybe you deleted the file accidently. try re-apply...
Top