Search results

Will follow up your ticket.

APC should work fine with ProcessGroup mode. Please check error_log and stderr.log for APC related errors. If you use cageFS, make sure the user's Cage has been updated to get all changes at server level. It should work with suEXEC Daemon mode as well, just all user shares the same APC cache...

Yes, you can try that.

Can you start sitemap generator manually? How long does it usually takes to finish? You can try https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:php:run-without-timeouts set "noabort" env with rewrite rule.

Please create a ticket with us, we need to do more investigation on this. Does it happen for regular HTTP connections? or HTTP/2 ?

Can you give user with uid 1000 a little more disk space? That's the easiest way to fix it. Otherwise, you need to patch the cPanel plugin code.

What exactly is the problem. Those rewrite rules should work fine.

those orphaned lsphp processes may not be the result of 5.0, but PHP stuck in waiting certain resources. Please check those processes with "lsof-n -p <pid>", and "strace -tt -T -p <pid>" . It could be a bug in opcode cache dealing with SHM lock. then you can kill them all. see if it reappears.

OK, I see. Have you tried 4.2.23?

Which version of IE? does it support SPDY? It works fine with build 4?

Do you have a test account to play with? please PM me the test account, I can take a look.

Sorry for the late response. If "jspa" is not a real script in the file system. you should just define a servlet context to match *.jspa URLs.

Since you have a front-end SSL proxy server, enabling SPDY or HTTP/2 on backend LiteSpeed web server has no effect to end users. Actually, HTTP/2 and SPDY are enabled by default, just the end user cannot reach it. I believe the front-end SSL proxy is not capable of forwarding SPDY and HTTP/2...

Good to know, 5.0 build 5 is available now.

5.0 Build 5 is out, it should fix the stats. Please run lsup.sh again.

The real-time statistics is broken due to some changes in .rtreport file, it will be fixed soon.

build 4 is available now, broke HTTP/2 in build 3. Sorry guys.

Please try build 3, Also, please install gdb, so the bug report can have full stack backtrace.

This issue should be addressed in 5.0 Build 3 as well. it is related to a front-end HTTPS proxy.

Please try Build 3, Safari is affected by a SPDY related bug in Build 2.