Search results

We will consider adding customizable log format. Right now, if you can settle with a signle log file, let all virtual host use server's access log, then virtual host name will be logged.

It is caused by mmcache + gzip compression in PHP, try turning off compression in PHP and clearing mmcache disk cache. Consider using eAccelerator instead.

If you are using "epoll" event dispatcher, you should switch to "poll".

You are welcome. :-) "Connection limits" are helpful with server load, but I think it is not the cause of the site slow down & hanging problem. The problem should be caused by the persistent connection from PHP to MySQL, deadlock happens, and eventually all PHP processes hang there doing...

I think it is not configured properly, and I need more information to identify the problem, output of "top", "netstat -an | grep ESTABLISHED", and content of lsws/logs/error.log lsws/logs/stderr.log, Real time report page in admin interface. If you can make the admin interface available to...

In addition to the limits in PHP, you should check the request, response body size limit of lsws, they are under "server"->"tuning" tab. Please error.log and stderr.log, and restart lsws.

The problem is identified. It is due to the 2.2.x kernel used on that server. 2.4.x kernel is the minimum requirement of LSWS. :-)

Do not install lsws under /etc, it is not allowed to serve anything under /etc for security reason. If you don't mind and your server is available over internet, I'd like to logon your server and take look. It is the best way I can help right now. PM me. Up to you. :-)

Did you start it as root or as the normal user? have to be a normal user. Which version of debian are you using?

I think it is a binary/library compatibility issue. Try starting lsws as the normal user specified during the installation, just run lsws/bin/lshttpd directly. Also, you need to change a configuration file manully, lsws/admin/conf/admin_config.xml , search for some thing like...

Any thing in lsws/logs/error.log?

Those activities are logged in the error log. just check the log file once for a while. Most time you don't need to any thing, as those are taken care of by server itself unless the attacker is not frustrated and keep doing that, then you can block them at firewall level. We will add a option...

Yes, it looks cool. If you are using scripts to detect possible attack based those information, it is not a good choice at all. We have built-in anti-attack features to fend off attacks. Just relax. :-) Have you read this and adjust your configuration according...

Did you take a look at the real statistic page in the web admin interface? What data did you monitor in mod_status?

Looks like the /checkout_process.php take more than 5 minutes to process and request is timed out, is it normal? There might be MySQL dead lock. you should turn off MySQL persistent connection. check your php.ini , default one is in lsws/conf/php.ini

That's remote address, where the request comes from. don't worry.

It because one script send a redirect to itself.

New benchmarks will be released with 2.0 release.

It will be in 2.x soon after we finish some more important features. It probably will available for all editions.

A session-aware load-balancing module is planed. Best Regards, George