Search results

  1. M

    Redirect by rewrite & .htaccess

    please try the 3.0 package http://www.litespeedtech.com/packages/3.0/lsws-3.0-std-i386-linux.tar.gz Frontpage with domain.com may work well with this release as well, please let me know.
  2. M

    Redirect by rewrite & .htaccess

    It works properly with my test case. What is the rewrite rule to redirect /a/info.php to /b/info.php? I wonder if the request got redirected at all. My rewrite rule in /a/.htaccess RewriteEngine on RewriteRule phpinfo.php /2/phpinfo.php It performs an internal redirect which does not change...
  3. M

    FrontPage Extensions & cPanel

    Are you sure it is the default cPanel FP extension installation? I wonder what FP extension feature were you using? the global admin site which can be used to enable/disable FP extension for each vhost? admin page for each site which can be used to manage user accounts? or uploading through FP...
  4. M

    Redirect by rewrite & .htaccess

    OK. I will check this.
  5. M

    setup php in rails template

    You have to use script handler configuration for php, context will not work. :)
  6. M

    max_execution_time did not changed

    I mean removing it from the lsphp external app configuration. Maybe you should remove the current installation and install the package again, make one change at a time and make sure it works. ;)
  7. M

    max_execution_time did not changed

    It looks fine. Will it work if you remove "-c /opt/phpconf" from the command line? Is there any PHP opcode cache enabled?
  8. M

    max_execution_time did not changed

    Maybe it is extension mismatch or missing extension. Please try cd lsws/fcgi-bin ./lsphp -c /opt/phpconf -i You should get some error messages if something is wrong.
  9. M

    errors while using memcache under heavy load

    Nothing to worry about the SIGUSR1, it either send by LSWS or the parent ruby process for various reasons, like LSWS restarts, all ruby processes started by it will be stoped. It should not affect normal Rails services in any way.
  10. M

    max_execution_time did not changed

    the full command should be "$SERVER_ROOT/fcgi-bin/lsphp -c /opt/phpconf"
  11. M

    max_execution_time did not changed

    What you did is correct. Maybe something wrong with the php.ini, you need to check lsws/log/error.log and lsws/log/stderr.log see if any information regarding it. You can remove the php.ini under /opt/phpconf, see if it works again, if yes, it is the php.ini. :)
  12. M

    max_execution_time did not changed

    There is a problem with the conf/php.ini permission when PHP is started in suEXEC mode. For security reason, conf directory is only readable by the user that lshttpd run as, usually "nobody" user. And it is not recommended to change permission mask of conf/ directory. So, it can be fixed by...
  13. M

    gems not found

    Looks like a ruby installation problem. Might be a permission problem. Does plain WEBrick works when started by the user that lsapi ruby process run as?
  14. M

    Zero content length, only affecting one rails app, out of nowhere

    Seems your rewrite rule rewrites everything to /system/maintenance.html .
  15. M

    access.log suddenly stopped logging

    Is there a dedicate access log file for each vhost? The server level access log will only log 404 requests does not belong to any vhost, unless vhosts are configured to log access to server log.
  16. M

    Commercial version and php5/mysql 4

    Forum is the place where to ask this kind generic question. :) Our release package comes with php 4.4.x binary, you need to build your own php binary if you want to use php5 or mysql 4.1+, or need an extra module. You only need to do it once, no need to do it again if you upgrade to our...
  17. M

    customize access log format

    It is compatible with Apache2's log format.
  18. M

    Restrictions on uploading files via POST in LS

    It probably is because the "max request body size" has been reached, you may need to increase it under "server"->"Tuning" tab.
  19. M

    Pressing the +/- in the Order column of Contexts doesn't do anything.

    Should be fixed in the updated RC2 package.
  20. M

    Rails: response 404

    Thank you for the update. That's something what I expected. :)
Top