Have moved my services to the new provider. Never had such a problem before but now my new provider seems to stop/kill/hang processes running for longer then 30s.

The problematic module seems to be:

  • Localization update 7.x-2.0 Provides automatic downloads and updates for translations.

Once I run it, the whole service hanged so had to manualy disable it in the database.

It's a big problem for me as I used to run it periodically to update translations.

The question is if is there any way to configure it to do not exceed the given 30s time limit?

  • Ask your host what methods you have available to increase the execution time (user php.ini and max_execution_time for example). If not, and the module doesn't already provide a batched version of its functionality, you'll need to open a feature request for it to the issue queue, as it'll mean coding that new functionality into the module – Clive Jun 20 '15 at 12:54
  • I can not increase host limit, period. What is a batched version ? – Paul Paku Jun 20 '15 at 12:57
  • Drupal provides a batch API that well-behaved modules use to perform long tasks. It breaks requests up so they have less chance of running into execution timeouts. If the module you're using runs long tasks, but doesn't use the batch API, your problem could solved by someone updating the module to use it. Not a trivial matter though, it'd take a couple of hours of coding and some more for testing. If the module already does use the batch API, and it's still timing out, then quite simply you need to put the site on a host that lets you increase that limit, or has better hardware – Clive Jun 20 '15 at 13:02
  • Ok, got the point. Have found it's known problem ... drupal.org/node/1267652 – Paul Paku Jun 20 '15 at 13:05

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.