How to solve time out in phpmyadmin?

Question

I want import huge (at least 300 mb) sql scripts via phpMyAdmin.

I've tried:

post_max_size = 750M
upload_max_filesize = 750M
max_execution_time = 300
max_input_time = 540
memory_limit = 1000M

in my php.ini file, but I'm still getting timeout errors during importing.

your script is taking more than 300 sec to execute so time out..try to increase it more...FYI u should look at your code first why script is taking too much time to run — swapnesh, May 23 '13 at 07:02
I got errors are "Script timeout passed, if you want to finish import, please resubmit same file and import will resume." — user1811486, May 23 '13 at 07:05
Then why not resubmit the same file? phpMyAdmin seems smart enough to handle the problem? — Pekka, May 23 '13 at 07:06
why don't you use hedisql instead of phpmysql. save bandwithd and time. — Erdem Ece, Dec 04 '14 at 15:01

jahajee.com · Answer 1 · 2015-01-04T20:35:02.413

155

If even after repeated upload you still get timeout error, pleasechange your settings in

\phpmyadmin\libraries\config.default.php

from $cfg['ExecTimeLimit'] = 300; to $cfg['ExecTimeLimit'] = 0; and restart. Now there is no execution time limit (trust we are talking about local server).

Source : Change Script time out in phpmyadmin

edited Jan 04 '15 at 20:35

answered Feb 08 '14 at 02:54

jahajee.com

3,683
4
21
26

37

Or better still, put that setting in your `phpmyadmin/config.inc.php`. – bodo Mar 06 '15 at 20:32
I tried your suggestion, @canaaerus, but it messed my system even after I changed its place and finally undone it and restarted apache2 server. Now it says Error SQL query: DocumentationEdit Edit SELECT `comment` FROM `phpmyadmin`.`pma__column_info` WHERE db_name = 'bot4a' AND table_name = '' AND column_name = '(db_comment)' MySQL said: Documentation #1100 - Table 'pma__column_info' was not locked with LOCK TABLES – Rodrigo Jul 24 '15 at 13:18
1

@Rodrigo: I'm pretty sure this has nothing to do with the above setting. Also you should ask this a new question and not as a comment. – bodo Jul 27 '15 at 10:40
2

`config.inc.php` is at `/Library/Application Support/appsolute/MAMP PRO/phpMyAdmin` with MAMP on Mac OS X – Shaun Dychko Jul 30 '15 at 17:12
As @chuchunaku says - YOU SHOULD EDIT config.inc.php INSTEAD or it won't work. This is the settings it reverts to not active configuration. – Bysander Sep 23 '16 at 13:05
Thanks, this also solved mine I stuck in this for about 4 hours. – Muhammad Tarique Apr 10 '17 at 10:13
Another source : https://www.devside.net/wamp-server/apache-and-php-limits-and-timeouts – w3spi May 03 '17 at 10:06
If your visiting from 2018 on, I found this file in, /Applications/MAMP/bin/phpMyAdmin/ on my Mac. Just edit config.inc.php and thats it. – Dan Zuzevich Mar 07 '18 at 20:16
I am using AWS server, How can I solved this issue on AWS? – user9437856 Jul 12 '20 at 16:57

score 18 · Answer 2 · answered Sep 13 '16 at 18:26

18

I'm using version 4.0.3 of MAMP along with phpmyadmin. The top of /Applications/MAMP/bin/phpMyAdmin/libraries/config.default.php reads:

DO NOT EDIT THIS FILE, EDIT config.inc.php INSTEAD !!!

Changing the following line in /Applications/MAMP/bin/phpMyAdmin/config.inc.php and restarting MAMP worked for me.

$cfg['ExecTimeLimit'] = 0;

answered Sep 13 '16 at 18:26

chuchunaku

181
1
3

Some of the other answers are saying to edit a file that says "DO NOT EDIT THIS FILE" why are people ignoring the notice? This answer gives solid advice and doesn't ignore the notice at the top of the file. – Spencer Shattuck Jul 18 '19 at 16:44

score 17 · Answer 3 · answered Apr 05 '16 at 08:15

I had the same issue and I used command line in order to import the SQL file. This method has 3 advantages:

It is a very easy way by running only 1 command line
It runs way faster
It does not have limitation

If you want to do this just follow this 3 steps:

Navigate to this path (i use wamp):

C:\wamp\bin\mysql\mysql5.6.17\bin>
Copy your sql file inside this path (ex file.sql)
Run this command:

mysql -u username -p database_name < file.sql

^{Note: if you already have your msql enviroment variable path set, you don't need to move your file.sql in the bin directory and you should only navigate to the path of the file.}

For others on osx; you might have to use `./mysql` (instead of just `mysql`) — Nicolai Krüger, Jul 29 '16 at 08:07

score 12 · Answer 4 · answered Dec 01 '14 at 11:26

But if you are using Plesk, change your settings in :

/usr/local/psa/admin/htdocs/domains/databases/phpMyAdmin/libraries/config.default.php

Change $cfg['ExecTimeLimit'] = 300; to $cfg['ExecTimeLimit'] = 0;

And restart with Plesk UI or use:

/etc/init.d/psa restart and /etc/init.d/httpd restart

score 9 · Answer 5 · edited Jun 22 '17 at 18:21

9

If using Cpanel/WHM the location of file config.default.php is under

/usr/local/cpanel/base/3rdparty/phpMyAdmin/libraries

and you should change the $cfg['ExecTimeLimit'] = 300; to $cfg['ExecTimeLimit'] = 0;

edited Jun 22 '17 at 18:21

Thibault

1,566
15
22

answered Jun 22 '17 at 15:20

user3057553

91
1
2

score 5 · Answer 6 · answered Dec 05 '16 at 14:23

5

If any of you happen to use WAMP then at least in the current version (3.0.6 x64) there's a file located in <your-wamp-dir>\alias\phpmyadmin.conf which overrides some of your php.ini options.

Edit this part:

# To import big file you can increase values php_admin_value upload_max_filesize 512M php_admin_value post_max_size 512M php_admin_value max_execution_time 600 php_admin_value max_input_time 600

answered Dec 05 '16 at 14:23

Artur K.

3,263
3
38
54

THANK YOU for posting this -- really helped me out! – Greg Burkett Mar 28 '17 at 22:58
This really works. file \alias\phpmyadmin.conf overrides conf.inc.php file, which is located in app\phpmyadmin directory – gogagubi Sep 06 '17 at 09:05

score 4 · Answer 7 · edited Aug 24 '15 at 06:43

4

I was having the issue previously in XAMPP localhost with phpmyadmin version 4.2.11.

Increasing the timeout in php.ini didn't helped either.

Then I edited xampp\phpMyAdmin\libraries\config.default.php to change the value of $cfg['ExecTimeLimit'], which was 300 by default.

That solved my issue.

edited Aug 24 '15 at 06:43

MarmiK

5,639
6
40
49

answered Feb 14 '15 at 07:01

Supratim Roy

842
11
16

score 2 · Answer 8 · answered Nov 19 '19 at 12:04

2

None of the above answers solved it for me.

I cant even find the 'libraries' folder in my xampp - ubuntu also.

So, I simply restarted using the following commands:

sudo service apache2 restart

and

sudo service mysql restart

Just restarted apache and mysql. Logged in phpmyadmin again and it worked as usual.

Thanks me..!!

answered Nov 19 '19 at 12:04

Deepak Keynes

311
2
16

1

I guess restart or reload the service are just a normal step when editing configuration file. If phpmyadmin was in timeout, there was cleary another problem that should be troobleshoot before restart all web server directly – Jérémie Leclercq Mar 29 '22 at 14:52

score 0 · Answer 9 · answered Oct 20 '15 at 03:40

I had this issue too and tried different memory expansion techniques I found on the web but had more troubles with it. I resolved to using the MySQL console source command, and of course you don't have to worry about phpMyAdmin or PHP maximum execution time and limits.

Syntax: source c:\path\to\dump_file.sql

Note: It's better to specify an absolute path to the dump file since the mysql working directory might not be known.

score 0 · Answer 10 · edited May 04 '22 at 18:53

0

go to /phpMyAdmin/libraries/config.default.php

Line Number 719

Change

$cfg['ExecTimeLimit'] = 300;

to

$cfg['ExecTimeLimit'] = 0;

edited May 04 '22 at 18:53

Dharman

30,962
25
85
135

answered Apr 28 '22 at 08:44

Waqar Sabir

21
3

1

This is not a good idea to set it to zero, better to increase the limit as needed without removing the limit – Lk77 Apr 28 '22 at 14:48

score -2 · Answer 11 · edited May 23 '17 at 10:31

-2

To increase the phpMyAdmin Session Timeout, open config.inc.php in the root phpMyAdmin directory and add this setting (anywhere).

$cfg['LoginCookieValidity'] = <your_new_timeout>;

Where is some number larger than 1800.

Note:

Always keep on mind that a short cookie lifetime is all well and good for the development server. So do not do this on your production server.

Reference

edited May 23 '17 at 10:31

Community

1
1

answered Jun 12 '16 at 10:17

josef

872
9
8

How to solve time out in phpmyadmin?

11 Answers11

Linked