phpmyadmin export db memory exhausted

[argonius]

Hi,

I am running Plesk 9.3.0. While trying to export a huge database (110MB) over phpmyadmin I received the following error in the error.log:
FastCGI-stderr: PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 152969079 bytes) in Unknown on line 0

I also upgraded phpmyadmin like described on kb.odin.com, but there is no change in behaviour. Still the same error.
If I set the memory_limit from 256MB up to 512MB it takes a long time until my browser freezes (Firefox 3.5) I think there is something wrong, but I can not really imagine what it could be.

OS: Centos 5.4
Plesk: 9.3.0 (direct install, not upgraded from prior versions!)
PhpMyAdmin: 2.11.9.5

hope someone has a clue.

Thanks,
Patrick

 

[IgorG]

http://kb.odin.com/article_50_780_en.html

 

[argonius]

thanks but

this will not solve the problem, cause phpmyadmin in plesk is not using /etc/php.ini

also php parameters like memory_limit, max_execution_time, post_max_size and upload_max_filesize are already increased. There must be another solution.

thanks, patrick

 

[IgorG]

There are two PHP in Plesk - one for Plesk admin interface (lighttpd) and one for client's sites (Apache):

Plesk admin's php:

/usr/local/psa/admin/bin/php
/usr/local/psa/admin/conf/php.ini

Client's php:

/usr/bin/php
/etc/php.ini

Phpmyadmin uses Plesk admin's PHP. Therefore you should tune /usr/local/psa/admin/conf/php.ini

 

[argonius]

thanks but

i already have knowen this. as i wrote in my previous post, i already increased the php parameters for phpmyadmin (so i did it in /usr/local/psa/admin/conf/php.ini. I also build a info.php file in the plesk phpmyadmin directory. this shows me on calling high values for memory_limit, post_max_size, etc...
so as i also wrote, if i increase memory_limit up to 512mb my firefox will wait a long time for a response from phpmyadmin and then freezes! there must be a bug or something. simply tuning php config values will not do the trick.

thanks, patrick

ps:
if you want, you can have a look on the server?

 

[IgorG]

Contact support team if you want to check it on your server. If it is really bug, you will be refunded for ticket.

 

[argonius]

hmm

thanks, but not really helpful ...

 

[ProWebS]

argonius, did you find any solution for this? I have the same problem.