Search results

That looks great! Do you mind we keep a copy and link it in our wiki?

Don't worry, we have tested it in our lab extensively. Should be best release for cPanel users.

Looks like it does not build PHP with LiteSpeed SAPI at all. I think you should check your configuration parameters, and make sure to remove those related to other SAPI modules, like Apache (--with-axps), or fcgi (--enable-fastcgi), etc. A set of files will be created each time you build PHP...

We will not able to fix a php internal bug, which we believe it is the root cause of the core dump. However, if you do not want to have lsphp stop producing core dump files any more, the solution is easy. Just add the following code to LSAPI_Init_Env_Parameters() function in...

For the ruby process, you should give enough memory, otherwise the application will break. For Memory I/O buffer, you don't have to change it as LSWS will allocate memory on demand. When the limit is hit, LSWS will start to swap to disk.

Please try command cd /opt/lsws/bin ./lshttpd -t

The build failed, you can check the build log under lsws/phpbuild directory.

That's normal, lshttpd cannot kill a child process started in suEXEC mode.

You can find the default value in the installation package under conf/ directory.

LiteSpeed Web Server 3.3.14 has been released This release is mainly to address a few minor bugs and improved cPanel compatibilities. Attention cPanel users: This release should fix the cPanel compatibility problem for real. :) "Use Apache Binary wrapper" option is recommended for people...

It is more likely a ruby internal problem, so, you may get more helpful tips if you write to the ruby email lists about this. If you want to, you can try debug a live Ruby process with http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:ruby_debug

Please try reset Static Requests/Second, Dynamic Requests/Second and Outbound Bandwidth to "0", then restart LSWS.

I have upgrade our rails test environment to 2.1.0, created a test rails application, it works fine with LiteSpeed, maybe the rails 2.0.2 is buggy.

No. you won't get email notification regarding this. Only when something happen to lshttpd itself you will get notified.

No, it will be added when the SSI support is ready.

Those are normal. need more information about your installation.

Maybe need to add something like "require rails" before "require config/environment"? Just a wild guess.

Do you have any idea why you get this ./config/environment.rb:13: uninitialized constant Rails (NameError) from /opt/lsws/fcgi-bin/RailsRunner.rb:5:in `require' from /opt/lsws/fcgi-bin/RailsRunner.rb:5 line 5 is require 'config/environment'

Does /opt/lsws/phpbuild/php-5.2.6/sapi/littespeed/php get created? Any error in the build log?

Please send a temp server root login to support@litespeedtech... we will take a look.