Search results

We recommend using fail2ban in this regard.

It is up to tomcat how to access those "attributes" in the AJPv13 request. http://tomcat.apache.org/connectors-doc/ajp/ajpv13a.html

I think you did not configure it properly for the regular expression. can you post a screen shot of that page? Another solution is to use proxy context, instead of servlet context. But, you still need to get the regular expression right.

Which version did you upgrade from? Are you using a VPS? "find: /proc/irq/ ..." is normal, it does not hurt. the error regarding "read()" is abnormal, Is there anything in error log? Can do "strace /usr/local/bin/lsws/lshttpd -d" and send us the output?

Yes, CSF need to be configured to parse error log file for detected IP attacking the server. We will leave it for CSF developer or someone familiar with their regex setup.

Please download and do a manual upgrade to 4.0.12 again. the latest build is more aggressive in closing files, it may solve your problem. Since the web server load is pretty high, I think it is better to have a dedicate DB server. If DB server is not that busy, you can use it as secondary web...

You can try our latest 4.0.12 if you have not, it might be fixed.

What do you mean "compatibility to CSF Firewall"? Exclude from LFD?

The problem is the URI configuration, it does not work like that, you need to use regular expression like

Maybe something wrong with the encryption key, Run /path/to/lsws/admin/misc/create_admin_keypair.sh fixed it.

chown -R lsadm:lsadm /usr/local/lsws/phpbuild

Where LSWS has been installed to? Possible for our staff to login and take a look?

It is likely a PHP/APC internal problem. Try turning off APC, or try eAccelerator, or upgrade APC. Also, if it does not solve the problem, do "strace -tt -T -p <pid_of_lsphp5>" and "strace -tt -T -p <pid_of_lshttpd>" and send us the output.

Upgrade to the latest 4.0.12 see how it goes.

download 4.0.12 and perform a upgrade again see if the problem fixed.

You have some mismatched PHP modules I think. those modules need to be build manually, it cannot be taken care of by cpeasyapache. try run /usr/local/lsws/fcgi-bin/lsphp-5.2.12 -i from command line, see if you got any error.

For PHP 5.3, LiteSpeed SAPI is included, so, you do not need to run "buildconf" again. Sometimes, at the end of configure output, it will say certain configuration is not known, like "--with-litespeed", but actually,it is successful if scroll back to check the SAPI used. If buildconf failed for...

Please submit a ticket to our billing system, we will investigate.

If you use PHP suEXEC, you need to increase the "PHP suEXEC Max Conn" from 10 to 20. That site may have performance issue as well.

Please follow our trouble shooting guide in our wiki http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:php:lsapi#trouble_shooting If cannot solve it by following those steps, please post more detail information about the issue.