Search results

You use LSWS with Apache httpd.conf, you should remove the listener and the vhost from web console. everything is configured through httpd.conf.

Please search the forum first. ia32-libs may be the solution.

You can add "concurrent_php" to Ignored Apache modules in server->general tab. php4_admin_value, php5_admin_value directives are not supported as it is not PHP standard

And the PHP script can modify the limit from PHP code, if it does not work after raising the limit, still only get around 18M, you need to look into possible memory limit configuration of the PHP application.

You should ask this question to PHP developers. bug.php.net

You have to raise memory_limit in php.ini even though the error message showing the limit has not been met. It is PHP internal thing.

You have memory_limit set to 64M in php.ini .

That's because of 2-CPU license, each litespeed list the IP one time.

there is likely another index file in that directory, move index.php to the first see if it help. make sure you locate the correct doc_root directory for that vhost.

set_time_limit(0) only change PHP internal limit, has nothing to do with any web server, including apache and LSWS. Apache is likely to have a very long connection timeout, so it works if you change set_time_limit(), it does not mean that the function really did anything to Apache. If you want...

Also try to build matching PHP to make sure that the latest LSAPI is used.

The memory limit was set to 100MB some where. check php.ini memory_limit, and lsphp5 memory limit configuration.

Are you configure everything in LSWS native configuration? using vhost templates? I think "default" was added somewhere, grep the whole "conf" directory see if you can find it. If you are sure it is not a configuration issue, please let our staff know how to exactly replicate your setup in our...

Run command "ulimit -a" from a PHP script, the memory limit might be lowered in php.ini .

I doubt that LSWS version will affect this, it is a problem between PHP and xcache. You can use a cron job to kill those PHP process with ppid being "1".

if you only need to upgrade PHP, just do it from command line with /script/phpup You can ignore the failure about Apache, then build matching PHP. This way you do not need to switch between Apache and LiteSpeed.

$HOSTNAME will only work for <serverName> config, not anywhere else. :p

$HOSTNAME will works as well.

Next release, LSWS will use server's home name if you leave serverName blank.

The log message shows that the PHP process crashed when processing the request. give our staff a temp root login to check the 503 errors, there must be subtle difference between LiteSpeed PHP and Apache PHP which cause the error. either memory limit, opcode cache or something, if it can be...