By rick hood on

Only /admin/* pages are not loading. All other pages seem to be loading fine - perhaps somewhat slower than on the devel server - but all loading.

Here are differences:

1. PHP - both are 5.2x - fine, no difference
2. MySQL - devel was 4.1 production is 5.x The database seemed to move OK via phpMyAdmin export then import.

But mysqli is not installed on production server so I had to change database connection string from:

$db_url = 'mysqli://username:password@localhost/databasename';
to:
$db_url = 'mysql://username:password@localhost/databasename';

---- I am thinking the MySQL thing is the problem, though possibly stuff below is -----

3. I am running the production site in a folder to test before putting it in server root.

$base_url = 'http://123.123.23.24/folder';

4. I am using the domain access module and have posted about this there:

http://drupal.org/node/332977

Thanks for any advice.

⋅ Categories: Drupal 5.x

Comments

rick hood’s picture

rick hood commented

To be clear, I can log in fine to the production site and it does not appear to be any kind of access control problem to get to the admin pages. There is no error or access denied message - the /admin/* pages just try to load but never load.

rick hood’s picture

rick hood commented

I just wanted to update that the problem I encountered when moving to the production server had something to do with Update Status module. When I disabled it (via phpMyAdmin - go to system table and set status of module to 0) I could then get to my production sites admin pages. Perhaps Update Status was hanging trying to phone home or whatever it does.

Rob T’s picture

Rob T commented

Thanks for the tip.

I just encountered the same scenario. It seemed as if all of a sudden, I could not access any administration page without timing out. Your solution worked for me.

Garry Egan’s picture

Garry Egan commented

After battling for 4 days on this, blaming everyone from my hosting provider (they just moved all of our folders to another box), all the way to COMCAST (they had issues, too), your fix totally saved me. I am under trememdous pressure to fix this particular site as the request came last week and i have been DOWN HARD since.

THANK YOU!!!!

Changing the update field in the system table TOTALLY fixed it.

jaxond’s picture

jaxond commented

In my case, there was an issue moving a site from our live server to a dev server. To be more specific about the fix, look in the system table in the database for a row where the filename field refers to modules/update/update.module. Edit the row, changing the value in the status field from 1 to 0. When you reload the admin page and visit admin/reports/status, you'll notice that Update Notifications are now disabled. The problem you were having could quite possibly relate to http://drupal.org/node/245990.

jenniferism’s picture

jenniferism commented

This worked to get my admin pages back up and functional... but how do I get the update status module working again?

ipswitch’s picture

ipswitch commented

what causes this and how do I re-enable the update module?

Anonymous’s picture

Anonymous (not verified) commented

This fixed the problem (at least temporarily) for my local dev site. A bit of an annoying problem, but no major issue whilst i test out various items.

rfabbri’s picture

rfabbri commented

Apparently when moving drupal 5 sites with update_status module activated, admin section is getting stuck.

So login to your database and run this query :
# if mysql
use %DRUPAL_DATABASE_NAME%;
update system SET status=0 where name='update_status';
# fi mysql

Thanks a lot for this piece of advice !!!

drusillap’s picture

drusillap commented

I increased PHP Memory allowance by adding the following to the settings.php file
ini_set('memory_limit', '32M'); // increased memory size to 32M

pendashteh’s picture

pendashteh commented

Rick's answer saved me! thanks a lot.

kalanh’s picture

kalanh
Primary language English
commented

I came across this issue when my office updated from 32bit XP to Windows 7 64bit, requiring an updated WAMP Server. My data dump worked fine, all of the content pages loaded but the admin pages just timed out.

The only difference to note for Rick's Fix in Drupal 6 is that the field name is now simply called 'update,' rather than 'update_status'.

mysql> UPDATE system SET status=0 WHERE name='update';
Query OK, 1 row affected (0.00sec)
Rows matched: 1 Changed 1 Warnings: 0