An AJAX HTTP error occurred. HTTP Result Code: 200 Debugging information follows. Path: /drupal-7.0/?q=batch&id=5&op=do StatusText: OK ResponseText: Fatal error: Maximum execution time of 240 seconds exceeded in C:\wamp\www\drupal-7.0\includes\database\database.inc on line 2039 Fatal error: Maximum execution time of 240 seconds exceeded in C:\wamp\www\drupal-7.0\includes\bootstrap.inc on line 3069 Fatal error: Maximum execution time of 240 seconds exceeded in C:\wamp\www\drupal-7.0\includes\session.inc on line 156 Fatal error: Maximum execution time of 240 seconds exceeded in C:\wamp\www\drupal-7.0\includes\session.inc on line 49
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | updating.JPG | 49.48 KB | roseiro |
Comments
Comment #1
gábor hojtsyIt would be good to know which module .po file caused the import to go above 240 seconds (4 minutes!). Do you remember? Separate .po files are imported in separate requests, and importing one .po file should not take 4 minutes, except if the server/database is highly overloaded. Is it old hardware / highly overloaded?
If this is an overloaded/old and slow server, unfortunately the best we can suggest at this point is to increase the execution limit. In that case, there is an issue at #569004: Add support for seek based batch import of .po files dealing with adding support for reading the .po files in smaller chunks, so there is much less likeliness of timeouts.
Marking needs feedback on the first few questions.
Comment #2
gábor hojtsyRetitling
Comment #3
roseiro commentedHello
Thank you for your reply.
I think I may have something to do with the equipment, but let me explain what happens before this error appears.
The bar indicating the download file blocking early on, as I show in fig. attached.
So I think the error is initiated there.
I draw attention to the figure, in this case had installed the Drupal modules 7 and taxonomy management and Localization update the progress bar stopped such as can be seen from 9 to 1 and only after some time the error appeared.
If after stopping the progress I close the error window does not appear that there not only indicates to me that the translation is complete,
but part of the translation made appears later.
Comment #4
gábor hojtsyYes, well, if part of the translations are imported, then the .po parsing times out midway. In this case, this is in fact a duplicate of #569004: Add support for seek based batch import of .po files. I tried to drum up more interest in that issue for the benefit of people with slow/overloaded machines. Will try again. Marking as duplicate of that one.
Comment #5
Infoloko commentedI have exactly the same problem in stalling Spanish. Running on local machine .. this is a show stopper for me as this is for an english/spanish site! Will now have to move to test server and try again from there. File involved:
16 of 105 drupal-7.15-es-po
Comment #6
Infoloko commentedFound a reference on a different site (http://drupal.stackexchange.com/questions/13960/during-updating-translat...) with a simple solution..
Open sites/all/modules/l10n_update/l10n_update.locale.inc; at line 28, change the code to the following one:
drupal_set_time_limit(840);
This seems to have fixed my problem .. now waiting fro the next one!