WSOD after local restore

nstrassner - July 22, 2009 - 16:41
Project:Backup and Migrate
Version:6.x-1.2
Component:Miscellaneous
Category:bug report
Priority:critical
Assigned:Unassigned
Status:postponed (maintainer needs more info)
Description

After successfully migrating a site from a local installation (with Drupal 6.13) up to an on-line production site (also with 6/13) using Backup and Migrate (6.x-1.2) I made some minor text changes to the production site and wanted to mirror those changes back to my local install. Again using Backup and Migrate, I downloaded the SQL file and did a local restore and got the WHITE SCREEN OF DEATH!

I went back to the production site, disabled all contributed modules, backed up again and tried a local restore and WSOD again. I tested the backups at the production site and found no problems restoring what I saved there, but nothing I do can restore the downloaded SQL files will work (either via Backup and Restore module or PHPMyAdmin.

Using PHPMyAdmin, I deleted all blocks and even turned off Backup and Migrate and tried restoring via PHPMyAdmin, all to the same effect.

I’m not sure what to do next in discovering why a backup that restores remotely will not restore on my local site.

Anyone run into this before or have a suggestion?

#1

nstrassner - July 22, 2009 - 18:19

More information:
I used PHPMyAdmin to dump an SQL backup, downloaded it and attempted a local restore and got this error (and the restore failed):

Error

SQL query:

-- -- Dumping data for table `actions` -- INSERT INTO `actions` (`aid`, `type`, `callback`, `parameters`, `description`) VALUES ('comment_unpublish_action', 'comment', 'comment_unpublish_action', '', 'Unpublish comment'), ('node_publish_action', 'node', 'node_publish_action', '', 'Publish post'), ('node_unpublish_action', 'node', 'node_unpublish_action', '', 'Unpublish post'), ('node_make_sticky_action', 'node', 'node_make_sticky_action', '', 'Make post sticky'), ('node_make_unsticky_action', 'node', 'node_make_unsticky_action', '', 'Make post unsticky'), ('node_promote_action', 'node', 'node_promote_action', '', 'Promote post to front page'), ('node_unpromote_action', 'node', 'node_unpromote_action', '', 'Remove post from front page'), ('node_save_action', 'node', 'node_save_action', '', 'Save post'), ('user_block_user_action', 'user', 'user_block_user_action', '', 'Block current user'), ('user_block_ip_action', 'user', 'user_block_ip_action', '', 'Ban IP address of current user'),[...]

MySQL said: Documentation
#1062 - Duplicate entry 'comment_unpublish_action' for key 'PRIMARY'

#2

ronan - July 25, 2009 - 03:12

...I tested the backups at the production site...

Oh, man, you just about gave me a heart attack with that line :)

Well the second issue you mention is easy enough. When you back up with phpMyAdmin, you need to pick 'Add Drop Tables' and 'Export Tables Structure and Data' (or whatever the actual text is) so that the tables get deleted and then recreated, otherwise you'll get duplicate entry errors.

As for your original issue. The WSOD often (if you're lucky) is accompanied with some useful entries in your apache error logs. You may need to check the docs of your operating system (or XAMP or MAMP or whatever you use) to find out where those are, but take a look and see if any of them give you any clues, or post them here and I may be able to help you figure out what's going on.

#3

ronan - September 26, 2009 - 17:37
Status:active» postponed (maintainer needs more info)

Did you manage to get a look at your error logs for this?

 
 

Drupal is a registered trademark of Dries Buytaert.