I 'maintain' a site for an organization and use drupal as the content engine. I rarely login, except when I am notified that a module or something needs to be upgraded to a newer version.

Unfortunately, I do not know when I last logged in, but I would say sometime over the last 30 to 45 days, to upgrade a module or maybe a theme. I did not encounter any errors, but certainly did not do any regression test, post upgrade.

Today, I logged in to update a more advanced content that I help them with and it worked fine. After finishing, I decided to check the Modules tab for any possible upgrades. When I clicked it, I get the following error:

The website encountered an unexpected error. Please try again later.

I then tried to go to the tab with the logs to find out what was going on and received the same error.

I pulled down the web log errors and found nothing (at least nothing that would cause a problem with PHP) and then checked the php error log and there's nothing in it for the last month. The last error was:

[07-Jun-2012 01:03:03] PHP Fatal error: Maximum execution time of 180 seconds exceeded in .../public_html/includes/locale.inc on line 1781

The site appears to work fine. I can update new content. But, I cannot get to the Modules or People or Configuration or Reports (I always get the error above.)

I found a tip on disabling modules, but when I ran the query, there were around 180 modules and I really have no idea which ones to disable (if there had been 20, I'd have just tried them one at a time, but it seems a bit onerous to try this same approach on 180).

Can someone provide some general steps on how to troubleshoot an issue when you don't know the last change that was done to the site and cannot get to the logs (thru the admin panel, at any rate)?

thanks,

jones

Comments

skein’s picture

try running the update.php. it might clear the cache and the problems might go away.

jajtiii’s picture

Thanks, that helped a lot.

In case anyone else finds this thread, I ran update.php in the root directory and it generated a new error that finally pointed me in the direction of the Google Analytics Report module. There was a 'bug' report here -

http://drupal.org/node/1558190

I have no idea if it is being tracked elsewhere, but that thread pointed me to the fact that the last time this thing was updated it created directories within directories, multiple times.

I resolved it by deleting the entire directory (google_analytics_reports) and uploading the latest version. Ran update again and no errors. I can also access the other parts of my backend that were previously denied to me.

thanks again, skein.

sagehassan’s picture

thanks soo much

duckzland’s picture

my best bet is your watchdog log gotten too big.

the cause can be cron never run for that site. btw what is the php memory limit for that site?

Usually upgrading php memory limit can solve this problem

--------------------------------------------------------------------------------------------------------
if you can use drupal why use others?
VicTheme.com

fejn’s picture

Looks like you got your problem resolved, but remember you can get to the admin pages like this (assuming site is www.example.com)

Content: www.example.com/admin/content
Structure: www.example.com/admin/structure
Appearance www.example.com/admin/appearance
People: www.example.com/admin/people
Modules: www.example.com/admin/modules
Configuration: www.example.com/admin/config
Reports: www.example.com/admin/reports

These should get you to the first level overlay in the section (assuming you are already logged in); you can get further into the menus in the same way by extending the path properly. e.g.,

Blocks menu: www.example.com/admin/structure/block