Search results

Are you using PHP suExec on that server?

Please do diff lsws/admin/fcgi-bin/admin_php lsws/fcgi-bin/lsphp if they are different, then overwrite lsws/fcgi-bin/lsphp with admin_php, lsphp is a earlier build. If they are identical, you have to try building your own lsphp binary.

No, it is not a problem with APC. Looks like something wrong with the php_html_puts(). Is this a fresh install of LSWS 3.2.4? or upgrade from earlier version? What OS are you using? Can you try building your own lsphp binary?

Looks like there is a infinite loop there. Please try gdb on one of lsphp process. [code]gdb attach <pid_of_lsphp_process> bt q [/gdb] It will show the location where lsphp stuck. You can also try build your own lsphp binary, the pre-built binary does not have anything like adodb builtin.

Does it happen all the time, or once for a while? You can strace the lsphp processes, see what they are doing. If something really is wrong, it will be a PHP bug, maybe in a PHP module. Please show us the strace result of one of the lsphp process.

3.3 release package is available on our server, just change the version number to 3.3 to download it. Please give it a try if you want to.

LSWS check for content changes by checking file size, i-node and modified time, if anything above changed, content should be updated immediately.

Those limits is for anti-DDoS, not for limiting the number of connection, if you want to limit the number of connection per IP to the exact number, you should configure it at firewall level with iptables. Those LiteSpeed configuration should be high enough not to affect normal usage, otherwise...

If you place it under the document root, it will work out of box. ;)

Are you using a trial key? it is a 2-CPU license, so the number shows there is twice of "max connections".

You have make that page accessible via URL like "/error401.html" or whatever, if it is not somewhere under the document root directory, you need to create a "static" context to assign that URL to that file.

It should work, make sure the file for the custom error do not have permission issue, try access that page directly, see what do you get.

If you store the password file somewhere under the document root, you should name it as ".htxxxx" to have it protected from serving as static file by web server. LSWS will not serve any file with a name like that.

Maybe there is permission issue with the password file for your realm. Please double check permission and content of that file.

You can login to our store and pay the monthly fee there. https://store.litespeedtech.com/client/login.php?action=887&sid=

PHP_LSAPI_CHILDREN will be overridden by "PHP suEXEC max conn". So, it has no effect together with PHP suEXEC. You can set "PHP suEXEC Max Conn" to anything less than 500, LiteSpeed can handle it fine, but higher value may not result in higher performance, you can experiment with it to find...

The trial version is a 2-CPU license, for PHP/suEXEC powered web sites, 2-CPU license should work very with on Quad core server. You raise "suEXEC max conn" to 150 see if it helps. There is no good solution now if the DoSer share the same IP with other users. You may have to sacrifices...

Just change the version number in the download link for the 3.3 package.

We do not have a chance to try it on Mac OS 10.5 yet, however, I believe it should work just fine. Would you like to give a try? I can make the latest 3.3 package build available for you.

74.86.x.x:80 is used already. Is there another web server running on the server? or there is another listener on address *:80. Stop the other web server or remove the listener listening on *:80. And chmod 0711 /home/john chmod 0755 /home/john/html will will fix the problem with your document root.