LiteSpeed 4.2 + SuExec Daemon + CloudLinux + APC = 503 errors

[meli]

Having some serious troubles with the new updates. I wanted to switch over to APC & get everything squared away with the new version of LiteSpeed so we could see what kind of performance gains are in store. Unfortunately, we can't get 503 errors to stop running rampant after enabling APC.

We have tried all sorts of APC settings, LiteSpeed settings, disabling other PHP modules, etc. Nothing has worked. If APC is enabled, clients see 503 errors. This happens on heavily loaded systems as well as lightly loaded systems. After 1-2 page requests on a site, 90% of the page requests from that point forth are 503 errors.

I've tried -huge- memory settings for APC and for LSPHP. I simply can't get it to work, no matter the configuration I use. I've had to disable all opcode caching for now because of the 503 errors. Is there something I'm missing?

Here is a link to our LiteSpeed configuration (this is for PHP 5.2.17, but this same error occurs with 5.3.18 on all three of the systems we've tried it on):
https://dl.dropbox.com/u/158959/litespeed1.png

PHPInfo is at the link below, but APC is disabled for now for obvious reasons.
http://atlasmail.theservercompany.co...as/phpinfo.php

The 503 errors show "Connection reset by peer!" when attempting to connect to uds://...lsphp52 , nothing of any substance.

There is plenty of available RAM on the system when the 503 errors occur (>10GB), and I've tried huge settings (~16GB) for max RAM usage by LSPHP with no luck.

Any tips?

[webizen]

https://store.litespeedtech.com/stor...yarticle&id=31

[meli]

So the solution is basically "turn off APC" I guess? I've done everything else on that list prior to making my post, even so far as to turn off APC until I can get some input elsewhere. I upgraded LiteSpeed & the LSAPI module for improved performance with opcode caching and the first recommendation is to disable opcode caching?

[webizen]

You should have mentioned you tried that post already (to save everyone's time).

You can run it(with APC enabled) from command line (like /usr/local/lsws/fcgi-bin/lsphp52 -v) and see any error messages. Also, in lsphp52 ext app config, lower mem limit to 1-1.5gb, increase proc limit to 200.

[meli]

I did basically explain everything in that post in my original post in the second paragraph. Command line PHP works just fine during the same time the 503 errors are popping up. The short of it is APC makes PHP 503 (and not 100% of the time, but -most- of the time), and without APC it works. I've tried up & down on the memory settings & connection settings with no luck (in LiteSpeed), and I've tried all sorts of APC settings, as well. This is across all of my systems, of which most are set far lower than the RAM settings you see in that screen shot. I suppose I'll try to figure this out on my own since I don't want to waste anyone's time.

[webizen]

pls pm one server temp root access for further look if you like.