As originally reported in the forums: (http://drupal.org/node/414568)

I discovered that while drupal.org is down, I can't access the Administer section of my two Drupal installs. As soon as drupal.org came back up, access was regained.

I'm running Drupal 6.9 and 6.8 on two different LAMP servers. PHP version is 5.1.6. Drupal is installed in a subdirectory. 6.9 is running behind a corporate firewall, 6.8 is not. Both experienced the same problem.

Comments

vm’s picture

could be due to the update status.module which connects to drupal.org. I only enable the update status module when I need to check the status of modules. It is not something I allow to run at all times.

vako’s picture

I had a similar issue a while back and running update.php fixed it.

z33k3r’s picture

Same here. Running 6.10 on LAMP, I experienced an inability to use the administrative side of things. I do have the status update module turned on.

Luckily for me it was only 20mins later that Drupal.org came back online.

Module should give a time out message rather than actually timing out...

z33k3r’s picture

Any updates on this from anybody?

dave reid’s picture

Component: base system » update.module
vm’s picture

Version: 6.9 » 6.x-dev
dww’s picture

Sounds directly related to (if not actually duplicate with) #319486: Fetched update informations at every cron. update.module shouldn't be attempting to fetch updates on every load of admin/* -- that only happens in cases where the {cache_update} table isn't working correctly (e.g. you have memcache and it's not specially configured, you've set the [sic] "minimum" cache lifetime, etc).

However, this isn't duplicate with #319486 because if d.o is down, it'd be nice if update.module had a nicer way to fail than just hanging when it does need to fetch available update data...

dww’s picture

Oh, but this is directly duplicate with #414820: Unavailable drupal.org leads to crashed cron. ;)

dww’s picture

Status: Active » Closed (duplicate)
dww’s picture