[Resolved] Yet another problem with Litespeed.

[VortMax]

eaccelerator.shm_size = 0
eaccelerator.enable = 1
eaccelerator.optimizer = 1

Set enabled to 0 and restart litespeed and test again?

[NiteWave]

that's ok too. have you rebuild lsphp without '--disable-json' ?

[VortMax]

not yet,
I am in and out today on service calls. I may have a chance to try that later tonight though.

[VortMax]

Had no affect, but it appears that eaccelreator is still running?

PHP 5.2.9 (cli) (built: Apr 28 2009 19:31:34)
Copyright (c) 1997-2009 The PHP Group
Zend Engine v2.2.0, Copyright (c) 1998-2009 Zend Technologies
with eAccelerator v0.9.5.3, Copyright (c) 2004-2006 eAccelerator, by eAccelerator

[VortMax]

By the way....Server load jumped significantly (double) when I tried to save that form again. And it appears that it's not the lsws php process but the lsws httpd process that maxes out:

10481 apache 6 -19 61832 44m 492 R 99.8 0.3 2:05.98 lshttpd

[VortMax]

Any more luck with this? I sent a PM to you earlier in the day. I really need to get this fixed ASAP.

Thank you

[mistwang]

I will check it later today.

[mistwang]

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 /etc/httpd/modsecurity.d/modsecurity_crs_10_config.conf, located a few offending rules, comment them out, the site template can be updated now.

[VortMax]

Thank you very much. Can you send me the changes you made to the mod_security stuff via PM. I would like to have a look at it. Curious, what was the purpose of activating the debugging?

[mistwang]

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.