Search results

It is the dump of request info when something happened. That message itself does no harm, the root cause of that message may need some attention.

No problem. this type of issue usually used up all available idle CPU cycles on one core, by spinning in the event loop, maybe a little bit sluggish, but should not block a request.

503 error means the backend cannot complete the request, is usually caused by PHP crash. The log section you posted is not a 503 error, but a 500 request timeout. You can search for "oops" string to locate log entries related to 503.

It is like a problem with your PHP setup. Your cookie length is fine. You can try turning off all type of cache, then enable one by one.

Can also do "lsof -p <pid_of_100%_cpu>", then kill -USR2 -p <pid_of_100%_cpu> to turn on debug logging dynamically, Log Level must be set to "DEBUG", and "Debug Level" "NONE". If it is too big, please send the log file to bug@litespeedtech...

there is a bug in mod_security implementation may cause high CPU usage after lshttpd run for a while. Please download and upgrade to the latest 4.1.2 build. If it happen again, please try "strace -tt -T -p <pid_of_lshttpd_using_100%_cpu>"

This feature has been added to 4.1.2 release.

that message is produced by lscgid binary, you should not get a message like that if you run "irc.cgi" from command line, unless you overwrite irc.cgi with lscgid binary. Switch back to Apache, if it does not work with Apache, it wont work with LiteSpeed. You have to fix irc.cgi instead.

what type of CGI is involved? Can you run the script from command line? Does it work if you switch back to Apache?

get the latest build of 4.1.2 by changing the version number in the download link. should be addressed.

We will add that feature in later release. I think the best solution is to get a session aware LB, like our LSLB product.

You can try page cache. http://www.litespeedtech.com/support/forum/forumdisplay.php?f=30

sure. no problem.

can you please reproduce the bug with debug logging enabled? You can search related log entries by your IP address, please send the log to bug@litespeedtech...

Are you using a FastCGI script to handle the upload?

Have you set "Inbound Bandwidth" limit? http://www.litespeedtech.com/docs/webserver/config/security/#inBandwidth Looks like a bug in bandwidth limit implementation.

download 4.1.2 again, this version may work well with symlink off.

Maybe you can use "If Owner match" instead of disable symlink completely.

Please check error.log and stderr.log. no change has been made related to directory listing in 4.1.2 .

You have to locate the gcc error, the part you posted does not help. you can try to compile those code manually, see what you get.