Having similar problem on my servers since WHM/cPanel auto updated my PMA to 4.0.5 - when I try to export any DB over around 25mb (regardless of if I choose "quick" or "gzip" method) I get an error like this:
Code:
Firefox can't find the file at https://my.hostname.net:2083/cpsess294726548209/3rdparty/phpMyAdmin/export.php
So I checked into the link that
cPanelNick provided above to the bug case at
#4046 Exporting huge Tables causes memory-Problems and then also discovered another open bug case at
#4072 Export doesn't work on my server
Even though the problem report symptoms are a bit different, in both reports you can see that phpMyAdmin senior developer
Marc Delisle has proposed the same bug fix in both cases which can be seen by
clicking here and it
looks like he's already implemented the fix in PMA 4.0.6-rc2 at this link - https://sourceforge.net/projects/phpmyadmin/files/phpMyAdmin/4.0.6-rc2/
Question I wonder is - how long will it take for 4.0.6 to make it's way into WHM/cPanel?
Admittedly I've always just let my WHM updates also handle the phpMyAdmin version on my servers, and I've never encountered this issue before, so I'm wondering what happens from here or how long it might be before WHM starts loading the fixed version into cPanel.
And for anyone who needs to only export certain DB's for specific users, you might find this helpful - here's the command I run in ssh to export individual user db backups into a folder in their hosting account where they can access them (make sure you create the folder in their account first):
mysqldump -p -u username database_name > /home/username/public_html/your_db_backups/database_name.sql
In that example:
- The first "username" should be their cPanel account username
- The database_name would obviously be the actual DB name you want to export
- The second "username" in the path would also be their cPanel account username
- The /your_db_backups/ folder in the path is a folder that I create (
folder must exist BEFORE running the command)
- The database_name.sql is the exported / backup file of their DB and I choose to name it the same as the DB I'm exporting
So if I had a user account name "steve" with a Wordpress database called "steve_wp1" that I need to export via shell and provide him a copy of,
the shell command would look like this (on my server configuration):
mysqldump -p -u steve steve_wp1 > /home/steve/public_html/your_db_backups/steve_wp1.sql
NOTE - as soon as you (I) run that command shell will ask for a password , and the password should be the user's cPanel (hosting account) password.
Likewise - if I needed to restore that DB for "steve" the command would look like this:
mysql -p -u steve steve_wp1 < /home/steve/public_html/your_db_backups/steve_wp1.sql
The same would come in handy if "steve" had his own backup .sql file that he wanted me to restore. He could just upload it to a folder in his hosting account and I could use the method above. (BTW - as far as I know the file has to be a .sql file and should not be a compressed format such as gzip).
I know for some folks the information above is easy / basic stuff, but it wasn't something I could have come up with myself without doing some reading first (took hints from posts on forums and even this thread) SO I'm hoping that information will help other users get through until we have a correctly working PMA Export feature again.
ALSO NOTE - As of today (September 1st 2013) PMA has shifted their public support to StackOverflow / StackExchange at
'phpmyadmin' tag wiki - Stack Overflow (they are trying to consolidate support and all their other public venues such as Forum / IRC / etc... are to be considered deprecated).
Hope some of my info was useful.
Also hope that the 4.0.6-rc2 fix that PMA released yesterday will make it to my WHM/cPanel updates soon! A large number of my customers depend on PMA for their DB backups.
