Search results

which OS are you using? Try lsws/admin/misc/admpass.sh to reset your admin password.

You can use the following script to dump the system resource limit for PHP process <?php $limits = posix_getrlimit(); print_r($limits); ?>

We usually put it in /opt/lsws/conf/cert

It is a file/directory permission problem, not related to rewrite rule.

the rewrite rule for Apache should work with Litespeed.

It is limited by the maximum size of each XML configuration value, Right now the limit is about 1MB, so it should be able to hold 58K IPs. How to maintain this list is another story. ;)

That's right, you need to let your admin to clear PHP opcode cache directory after upgrading PHP. And I heard that there are PHP compatibility issues with 5.2.8 .

Easy apache will install all libraries for you if anything missing on your server. For unexperienced people, it is a good idea to run easy apache first, then build matching PHP. May not be necessary for experienced admins.

Sometimes, user need to do "make clean" under /home/cpeasyapache/src/php-5.2.x then build matching PHP. When you build matching PHP from WHM, the PHP will share the same php.ini as Apache mod_php. With LSWS admin console, you have the flexibility to specify the location of php.ini . To use the...

You need to set http://www.litespeedtech.com/docs/webserver/config/vhostgeneral/#docRoot

The latest build of release 3.3.23 has 5.2.8 now. but it wont work unless the suhosin patch become available.

Maybe it is the memory limit for PHP processes, you can try increase the memory soft/hard limit for lsphp5 external application.

I am not that familiar with rack. For the lobster example comes with the rack package, you need to change the handler from WEBrick to LSWS in protectedlobster.rb Rack::Handler::LSWS.run pretty_protected_lobster Then add an external application to LSWS and assign proper script handler and/or...

I think each mongrel instance can only handle one connection and process one request at a time, so, I think you should use "Max connections = 1" for all mongrel external app.

because suhosin patch for 5.2.8 was not available yesterday.

You should check error.log and stderr.log. If used with cPanel, the log file is under /usr/local/apache/logs/, error_log and stderr.log

If each vhost get a its own mongrel instances, one vhost should not affect the others. Have to fix the script, changing timeout may not help as the mongrel may still working on the previous request when LSWS send next request to it. Why not use our dedicate rails support via ruby-lsapi?

LiteSpeed Web Server 3.3.23 has been released Download LiteSpeed Web Server View Version History LiteSpeed Load Balancer 1.5 has been released Download LiteSpeed Load Balancer View Version History

You do not need to use the Rails vhost template for a 'static' website. Just create a vhost and set the document root to the directory directly.

Maybe you can consider to create a external app for each vhost, for PHP, use PHP suEXEC. Your Inital request timeout is too low, keep it at 60 or the longest time that a request would take. LSWS queue the requests when running short on connections to external app. So, "WaitQ" is not 0.