By DirtyBirdNJ on

Hello, I started having a problem recently where when either trying to view, or make changes to the module list, I get a PHP timeout error.

Previously, I had ticked 5-7 modules to re-enable them after upgrading to 6.9, and I got the timeout error. After reloading the page once, it loaded find the second time and all the modules I tried to enable actually HAD been enabled.

Today I went to the same page, and got the timeout error again. The issue does not (appear) to be causing any other problems... but it just seems like something that is going to bite me in the rear sooner or later.

⋅ Categories: Drupal 6.x

Comments

DirtyBirdNJ’s picture

DirtyBirdNJ commented

Here is the error that is being generated:

PHP Fatal error: Maximum execution time of 30 seconds exceeded in D:\Websites\drupal\includes\theme.inc on line 752

sethwilpan’s picture

sethwilpan commented

Full error when trying to administer modules:

*
... (Array, 1 element)
o
region (String, 4 characters ) left
*
Krumo version 0.2a
| http://krumo.sourceforge.net

Fatal error: Maximum execution time of 30 seconds exceeded in /var/www/drupal/sites/all/modules/contrib/devel/krumo/class.krumo.php on line 604

pluess’s picture

pluess commented

I have the same problem. I cannot enable or disable any modules anymore. Every time I hit the save button the error shows up after 60 seconds.

Any ideas are welcome.

www.pluess.li

abowers’s picture

abowers commented

I have had a similar problem with Drupal 6 on my local environment for some time (I'm using XAMPP). I was able to ignore it for a while since it isn't my production site, and have had to change a few things to get around it. Some things that might help:

  1. Increase your max_execution_time in your php.ini file. I think this is what this error is really complaining about - the scripts are taking longer than the time allowed in your php.ini file. Now, this doesn't fix any issues causing your script to run for longer than the allowed time, but it might at least let you get in to disable some modules or try to figure out what is going on. I'm not sure what is a normal, acceptable number - usually it is 60, I think. I use 300 on my local dev environment, but 60 on my production site since my dev environment has alot of the performance settings turned off. You may want to check with your hosting provider to see if there are any constraints and to make sure that you are still being a good shared hosting citizen.
  2. Increase your memory_limit, upload_max_filesize, and post_max_size if you can, again in your php.ini. Here's a resource for performance tuning of Drupal: http://drupal.org/node/326504. Again, you might want to check with your hosting provider about available limits.
  3. Disable and uninstall the Update status module on your production site (I like to enable in my local test environment in the settings file so that I know when updates are ready). I've seen around that there can be issues with this module since it is going out to the Drupal site to find updates with running crons and stuff. It may be that the modules list page is doing something with that.

I think that there are several modules out there for troubleshooting. The Devel module can provide statistics for how long queries and stuff is taking. Sometimes, it seems to be related to a specific module that you have enabled, but it might be something else. I am by far no expert, so I always like to check if I have any queries that are taking a long time. I'm not sure what the modules list page is doing that could be the issue. You might try the Arooga module to see if there are problems on any other pages. If not, I can't think of any reason why you couldn't leave your php.ini settings higher, if it works and your hosting provider doesn't mind.