This is an extremely common issue with Fantastico fresh WordPress installs. It is very frequent and I need a resolution. This issue does not exist...
No APC here. I am about to just scratch LiteSpeed on all of our servers if this persists.
2010-11-11 16:16:24.165 [INFO]...
We have the latest build as of Thursday and we are still seeing constant issues with WordPress and 503 errors. When are these going to get resolved?...
There is a PHP4 and a PHP5 section set by cPanel for Apache. LiteSpeed should be picking up the PHP5 section.
And why would it be using PHP4 when it is disabled in LiteSpeed?
Very true. Why is it using the php4 variables anyhow?
No Include path is defined @ /usr/local/lsws/lsphp5/lib/php.ini which IS the php.ini file used.
Where else would it be pulling from?
include_path .:/usr/local/lsws/lsphp5/lib/php .:/usr/local/lsws/lsphp5/lib/php
That is not the proper path though as explained clearly. The proper path is :
PHP4 is deprecated. In order to remove it from our LiteSpeed installs, is all that is necessary to run a delete on... LSAPI App lsphp4...
Having an issue with RVSitebuilder. It appears the script wants to pull from the path which LiteSpeed does not have configured.
.net support will be in our 4.0 release.
When in the 4.0 release is it planned?
Recompiling to 5.2.14 several times did the trick.
We are having an issue with mod_mono 2.0 not loading .asp pages with LiteSpeed.
LoadModule mono_module modules/mod_mono.so...
I just rebuilt and the problem is far worse now affecting all scripts:
2010-08-08 12:12:43.978 [INFO]...
Two weeks ago. 5.2.13.
We have quite a few clients that are having 503 issues with LiteSpeed servers.
This occurs even with fresh installs. Some work and some don't....
What would be causing this in a phpsuexec environment?
nobody 38.01 2.42 0.0
Top Process %CPU 24.4 lshttpd
Top Process %CPU 24.2 lshttpd
Separate names with a comma.