Skip to main content

phpMyAdmin import internal 500 error

lblanchardiii

Trying to import a 686 MB SQL file. First, the sql file (compressed) is located on the server itself. I made changes to the phpMyAdmin config to use a directory for this so I didn't have to keep doing this over and over on my slow upload connection.

When I try to import, it starts but after a while it gives the following error:

[2025-04-19 15:15:37 +0000] info [whostmgrd] Internal Server Error: "GET /cpsess4466003910/json-api/loadavg HTTP/1.1" 500 Error ID a969e980aff6
[2025-04-19 15:18:37 +0000] info [whostmgrd] Internal Server Error: "POST /cpsess4466003910/3rdparty/phpMyAdmin/index.php?route=/import HTTP/1.1" 500 The subprocess (php) failed to send content during the allowed timeframe.
[2025-04-19 15:38:23 +0000] info [whostmgrd] PID 3648187: The cPanel Server operation timed out at cpsrvd.pl line 670.: falling back to php-cgi: check /usr/local/cpanel/logs/php-fpm/error.log
[2025-04-19 15:44:23 +0000] info [whostmgrd] Internal Server Error: "POST /cpsess4466003910/3rdparty/phpMyAdmin/index.php?route=/import HTTP/1.1" 500 The subprocess (php) failed to send content during the allowed timeframe.

It does appear to import partially as some of the data does show up on the web site when I visit it, but not all of it.

I thought phpMyAdmin would tell me where it stopped so I could just continue it where it left off, but it does not. It goes straight to a page that just says

Internal Server Error
500

The subprocess (php) failed to send content during the allowed timeframe.

I thought I increased the time for this from the default 30 seconds to 5000 seconds by changing the 'max_execution_time' value for php, but this does not seem to effect how long it runs before popping up the ISE 500.

What setting do I need to change to allow more time for this script to run the import?

Comments

1 comment

Date Votes
  • rbairwell

    Personally, I would not attempt to import (or even export) a large file through PhpMyAdmin: there are so many places it could fail (Apache timeout, PHP timeout, PHP memory limit, WHM timeouts etc etc).

    I would import the file via the shell/terminal:

    mysql -u database_username -p database_name < file.sql

    You'll need to have the file uncompressed file - if you don't, try something like:

    gunzip -c file.sql.gz | mysql -u database_username -p database_name

    In both cases, you will be prompted for the database user's password.

     

    1

Please sign in to leave a comment.

Didn't find what you were looking for?

New post