Search results

So, nginx cannot populate the memcached, can only get data from it? If it is used as page cache, it won't be any better than web server internal page cache, actually should be not as efficient as the web server need to fetch the page from memcached instead of serving it directly. And memcached...

We will use our internal cache implemented in 4.0. it will be as fast as memcached, especially when used with SSI. What can Nginx do with memcached? as page cache storage? or object/page parts cache?

I think you need to find a way to verify the private key and certificate with other package and make sure they are truly match.

Maybe you should use "mycert" instead of sbiSSL.pem, and set "CA Certificate File" to sbiSSL.pem. I assume the sbiSSL.pem is the CA certificate.

The call stack has been messed up, cannot tell anything. Anyway, if it does not happen frequently, there is nothing to worry about.

It is a PHP problem, if getmxrr() timeout and PHP blocked at that function, it may cause trouble for next request assigned to it. There is not much we can do about. Either allocate enough spear PHP processes by setting "PHP_LSAPI_CHILDREN" larger than "Max connections". Or, let LSWS to kill...

That might be a PHP problem, you should use GDB to check the core file against lsphp5 binary. gdb lsphp5 <core_file> bt

You can try the same command from command line see what happen. then try "sudo /usr/local/lsws/bin/lswsctrl restart" If there is a core file under /tmp/lshttpd, please check it with GDB. gdb lshttpd core_file bt

Have you tried to harden the security under the lsws directory? The default installation should work just fine. Maybe you should remove /opt/lsws directory and reinstall it from scratch. You can manually change the lsws/conf/httpd_config.xml, the worst case.

Just create a listener with the IP for your main site. that's it.

You can try strace dispatch.lsapi process to find out why. dispatch.lsapi should be placed under public/ folder. It probably easier to use the rails context unless you need some extra flexibilities.

Looks like you do have a permission problem. Check the configuration file see if it changed? If you install LSWS to your home directory, you may have this problem, install it to /opt/lsws or /usr/local/lsws.

do make at the root source directory.

Please check the configuration options with the installed CLI php. php -i then check the PHP build directory see if the sapi/litespeed/php get created or not. If not, try "make" from command line see if there is any errors.

We plan to do benchmark again with our 4.0 release. There are many hosting company using cPanel + LiteSpeed hosting thousands of accounts. I am pretty sure everything will work just fine. We will fix any bug discovered. There is no big difference between 64bit and 32bit LSWS, you will not go...

what exactly is the error? I am pretty sure the previous error should have gone.

No problem. thank you for sharing your finding with us.

Maybe just that safari is more picky on cookies, make sure the that domain used in the cookie matches the domain name in the request URL. Only "Set-Cookie" response header is important in this regard.

Phillip, I think maybe Safari is more picky with "Set-Cookie" response header. LiteSpeed will treat the same request exactly the same no matter which browser send the request, unless the browser send something special. To debug and verify this problem, please try something like tcpdump to...

It depends on your web application. If you site is mostly powered by PHP, you will not see big differences. If your site is mainly static content or HTTPS, 4CPU license will work better. Another thread about License and CPU: http://www.litespeedtech.com/support/forum/showthread.php?t=1660 We...