503 error, phpMyAdmin running sql query
 

I am having problems with running large sql queries with PhpMyAdmin under lsws

The sql query that is being run is around 3MB

I thought at first it may be the upload_max_filesize = 2M So i changed it to 4M No go.

I then checked the logs and found

lsws/log/error.log

FATAL: emalloc(): Unable to allocate 2040073 bytes
FATAL: emalloc(): Unable to allocate 2040073 bytes
FATAL: emalloc(): Unable to allocate 2040073 bytes
FATAL: emalloc(): Unable to allocate 2040073 bytes
FATAL: emalloc(): Unable to allocate 2040073 bytes
FATAL: emalloc(): Unable to allocate 2040073 bytes

Then went to admin and changed

Debug Level = High
Log Level = Debug

Here are the lines from error.log that are being produced from the above settings.

2005-02-28 16:36:54.225 [DEBUG] Failed to execute 'mpstat' command: No such file or directory
2005-02-28 16:36:59.229 [DEBUG] Failed to execute 'mpstat' command: No such file or directory
2005-02-28 16:37:04.233 [DEBUG] Failed to execute 'mpstat' command: No such file or directory
2005-02-28 16:37:09.238 [DEBUG] Failed to execute 'mpstat' command: No such file or directory
2005-02-28 16:37:14.242 [DEBUG] Failed to execute 'mpstat' command: No such file or directory
2005-02-28 16:37:19.246 [DEBUG] Failed to execute 'mpstat' command: No such file or directory
2005-02-28 16:37:24.250 [DEBUG] Failed to execute 'mpstat' command: No such file or directory

I thought mpstat had to do with getting system info such as processor id and the such.

I know the above errors are being created when trying to run my sql queries because the same
thing keeps on growing in the log at the same time i am making the 503 come up


Please help me with this. I am slowly getting the site up again.

I am running now on suse 9.2 professional minimal install Kernel 2.6.x

thanx

In addition to the limits in PHP, you should check the request, response body size limit of lsws, they are under "server"->"tuning" tab.

Please error.log and stderr.log, and restart lsws.

AHH YES

Sure enough it was the max dynamic request body size

was set to 1M

Changed to 4M and worked like a charm.

Thanx