Here's the error:

An AJAX HTTP error occurred. HTTP Result Code: 200 Debugging information follows. Path: /batch?render=overlay&id=7&op=do StatusText: OK ResponseText: Fatal error: Maximum execution time of 240 seconds exceeded in web_root\includes\database\database.inc on line 2136.

Here's line 2136: $return = parent::execute($args);

I set the maximum execution time (maximum_execution_time) to 3000 seconds in php.ini. Actually, maximum execution time may have been set elsewhere (for example, in the script that's being executed.

What about using load_data_infile (http://dev.mysql.com/doc/refman/5.0/en/load-data.html)? What about real ETL tool or even just gettext...? Anyway, it seems pretty cool to the webservers to have php doing something for 240 seconds....

I get this error consistently, every time I try to add the Japanese language. The line number changes, though, I believe. I'll update and let you know.

Comments

Fohsap’s picture

Title: Script timing out » Lang import script timing out
Fohsap’s picture

Usually we get up to 7%...

Completed 1 of 15. ... 7%
Importing: drupal-7.14.es.po.

An AJAX HTTP error occurred. HTTP Result Code: 200 Debugging information follows. Path: /batch?render=overlay&id=8&op=do StatusText: OK ResponseText: Fatal error: Maximum execution time of 240 seconds exceeded in web_root\includes\database\database.inc on line 2136.

Same error, different language. Same line....

Fohsap’s picture

"240", the maximum execution time, also doesn't appear anywhere in the file throwing the error. I'm wondering if .htaccess may be setting it or something. I'm looking around because something other than php.ini is setting the maximum execution time.

Fohsap’s picture

Status: Active » Closed (duplicate)

This is a known issue. Changing php.ini's max_execution_time from 30 to 4000 and |10n_update.locale.inc's drupal_set_time_limit() from 240 to 4000 is a workaround.