Search results

You have to use command "sudo -u <user_name> <path_to_lsphp> -i" to check. User name should match the user that lsphp process run as. I think it is a permission issue.

Does $logger work for rails 2.x when WEBrick or mongrel is used? Another main difference of Ruby LSAPI is that it forks children processes off a process with initialized Rails framework, I am not sure it is the cause or not.

The only difference is that LiteSpeed only set a few Environment variable, not everyone in the shell, if you the route depends on some special environment variable, it must be set under "ruby rails" tab. For example, "HOME" must be set when use RESTful route.

That's correct. everything is still managed by cPanel.

There is a memory limit configuration in php.ini as well.

You can try it from command line with sudo sudo -u <user_name> lsws/fcgi-bin/lsphp -i

All those operations are performance by LSWS watchdog process, so "Auto Restart" must be set to on. Since we have a lot of feature depends on the watchdog process, 3.3.4 has been changed to always on, can not be disabled.

LiteSpeed does not block requests result in 404 not found.

You have to trace a PHP process that proces the request that has problem, those are idle processes. You can apply another trial, we allow trial for maximum 30-days for each server, and we offer 30-days money back as well.

For linux, you need to install jpeg-devel RPM.

It is a PHP core function, should be available to all PHP SAPI, it might be a permission issue or something.

Are you streaming the flv through PHP? the MIME type probably is set by PHP not by LSWS. If you do so, you should look into our "Internal redirect" feature, do a search on the forum.

LiteSpeed Web Server 3.3.4 has been released Download LiteSpeed Web Server View Version History

There should be any problem with the configuration, maybe your browser cached the file, clear browser cache and try again.

Feature like proxy detection probably will not make into the lshttpd core, we'd like to keep it light and make API available for third party external processors.

Some complex logic can be done with external processor like PHP, RoR or other web programming language, like proxy detection etc. after authenticated, issue a internal redirect to let lshttpd serve the file directly. We will update our wanted feature list as well.

Maybe the page was cached by your browser, clear browser cache first.

http://en.wikipedia.org/wiki/Bus_error

gzipped version should be served, the query string part should be ignored it is a static file. Please double check if the "Static gzip cache directory" is not full, by default is under /tmp/lshttpd/swap.

OK, this issue has been identified and fix has been committed to the 3.3.4 release. Sorry for the delay, we do need a little bit more detail in the bug report to get it fixed. :)