Search results

that's correct, not need to bring down LSWS.

You can copy ixed.5.2.lin from /usr/local/lib/php/extensions/.... It is another loader like ioncube, I believe.

per user limit can be set in /etc/security/limits.conf, LiteSpeed cannot set unlimited, it has to be a number, or system default.

It will be served via a special URL when required, like mod_status in Apache.

there is a memory limit being set in php.ini as well.

Please contact sales on this, yearly software update is a product add-on for owned license, maybe product type of your license need to be updated if it was set as "Yearly software update for LSWS 4-CPU owned".

put ionCube load modules in /usr/local/lib/php/extensions/no-debug-non-zts-..../ directory.

Looks like a MySQL performance issue, as it using 99% CPU, it is not something related to LSWS at all. A few tips to trouble shot this is to check mysqladmin processlist mysqladmin extend-status find out the SQL takes long time, add proper table index if need. Our advanced anti-DDoS setup...

It wont work well, as LSWS does not know which vhost a connection goes to without accepting the connection and receiving the request headers, there is no way to tell which connection is valid user, which one is from attacker, if close connections after accepting connections, valid user will be...

You can ignore those, it does not matter. you can remove those templates, or create a listener with name "Default".

most likely the request crashed PHP, LSWS tried three times, always crash PHP. To trouble shoot this, the easiest way is to switch back to apache, put LSWS on a port offset, so only you can access litespeed. change "max idle" of lsphp5 external app to a longer value like 300 seconds, then send...

Thanks for the detail test case, we successfully identify the bug and fixed it. It was the length of request body not being passed to PHP properly. Fix is in our 4.0.16 build, just change the version number in the download link to get it.

Maybe that IP used trial key before, so it is not allow to use trial key again, please send the IP to sales@... to clear it.

Chunked POST request should be supported. Can you provide a simple example request including request header and chunked body, please send it to bug@litepseed... We will fix it if it is a bug or a situation not handled properly.

change php.ini to allow PHP dump errors to screen or log file, so, you will get an idea what happened with PHP. Try changing index.php, only display phpinfo() to test PHP installation works or not.

ispCP may require a PHP module that does not exist in LiteSpeed PHP, You should rebuild PHP with exact the same configuration option like Apache's PHP. Just display phpinfo() page from both, and compare if all configuration options, runtime configuration, and modules are the same.

That's from PHP internal, have no clue what it is.

activating debugging is to find out the offending rule. LiteSpeed will log the rule to error.log, reproduce the problem, then grep error.log with your IP. it will list the test string and pattern of the rule, then you can comment it out, try again, until the page works.

The 99% cpu is caused by PCRE pattern matching, when processing mod_security rules, rebuild LSWS with reduced PCRE looping limit, the 99% cpu problem is gone. Then there are a few mod_security rules block the POST request, enable debug logging with "SecDebugLogLevel 9" in...

I will check it later today.