Search results

  1. M

    Gzip output script works with Perl-CGI but gives error with Perl-FCGI..

    Not a perl expert here, just a guess. the test code may interfere with the FCGI file handle 0 or 1, so it breaks the FCGI protocol. It is not a problem with CGI though. And it is really a bad idea to start another process for the compression, should use a Perl internal module if available. Or...
  2. M

    500 Errors with older sites after update to 4.0.10 etc.

    Looks like a problem between Gem and older Rails releases, nothing to do with the RailsRunder.rb .
  3. M

    503 Unavailable error

    If the 503 error is not random, it maybe a problem with PHP build and PHP crashed. If switch back to Apache, you will get a blank page instead of 503 error page instead, that's all due to PHP crash. You can try different PHP version, turn off opcode cache, etc.
  4. M

    503 Unavailable error

    Do you get 503 errors constantly?
  5. M

    LSWS 4.1RC1 release

    Thank for the bug report, this will be addressed soon.
  6. M

    DDos and hardware to work well with Litespeed

    I suggest you try LiteSpeed before upgrading the server. If CPU is not 100% utilized during peak hour, upgrade to Quad Xeon may not help. check the 'top' output.
  7. M

    DDos and hardware to work well with Litespeed

    Looks like your server performance is bounded by mysql, try command mysqladmin processlist if a SQL takes too long to process, you need to check the index and optimize the SQL.
  8. M

    DDos and hardware to work well with Litespeed

    Yes, from top output.
  9. M

    .htaccess and mod_proxy

    Currently the rewrite rule does not support changing query string, can only change the request URI part. Next release will support changing query string.
  10. M

    DDos and hardware to work well with Litespeed

    You should post your server memory usage, I/O wait, CPU utilization etc. ShoutCast usually causes high load. And what you experiencing sounds like a DB optimization issue.
  11. M

    CGI Setup with access only to Perl binary.

    I think that you cannot get what you want from any web server. CGI will work like that, you have to limit the access with file system permission if you want. If Perl internal does not limit exec() and system(), nobody can.
  12. M

    Huge lsphp5 problem

    Please downgrade to 4.0.6 for now, you need to run the installer in 4.0.6 package.
  13. M

    Permissions messed up in 4.0.10

    adding lsadm to www-data should fix the permission issue. Next release we will change admin PHP suEXEC to lsadmin:www-data .
  14. M

    4.0.10 --> 4.0.9 downgrade

    Maybe you need to adapt the file permission to allow lsadm to access it. the admin PHP run as lsadm.
  15. M

    4.0.10 --> 4.0.9 downgrade

    You need to run the installer in 4.0.9 to downgrade due to file ownership changes in 4.0.10.
  16. M

    4.0.10 suEXEC

    the admin console run as lsadm:lsadm for 4.0.10, no long as the user that web sever run as for better security. You should change your upload file permission accordingly. For PHP session error, check the permission of lsws/admin/tmp and the session file in it. should be owned by lsadm for 4.0.10.
  17. M

    Directory doesn't exist... :( 404, cannot be found

    there is no index.html, if you access /file/sample.txt, it will work.
  18. M

    4.01 - Symlinks NOT working when outside of the home directory....

    check your error log for the reason of 403 error.
  19. M

    shows logs on high load

    We will have 4.0.11 to address them all.
  20. M

    PHP 5.3 binary size

    that's normal. PHP4 is slimmer and debug symbol has been stripped.
Top