BackupBuddy: Advanced Debugging
Backups Time Out / Marked as Bad
- Backup file size is too large so it takes too long to finish & server kills it. Try reducing backup size, excluding directories, disabling compression to speed up zip file generation, or getting host to enable native zip compression if not already enabled.
- Backup file location permissions do not allow writing. Give write permissions to the directory /wp-content/uploads/.
Fallback to Compatibility Mode (not necessarily a 'problem')
- The command line command 'zip' is unavailable. Ask host to allow access to it. Not available on Windows without using the zip package we provide (Ask Dustin about this until he documents it!)
- exec() function is disabled in PHP. Ask host to remove this block or remove it from the block list in cPanel if available. (Ask Dustin about this until he documents it!)
- They are using Windows. -- ask Dustin.
FTP Transfers Fail
- Login credentials are wrong. Test them to be sure. This is surprisingly common. View the HTML source to obtain the hidden password.
- The path entered is incorrect or the directory has not been created. BackupBuddy requires the path to already exist.
- Some hosts block outgoing FTP connections, port 21 (standard FTP port), and/or do not have the FTP extension available for their PHP installation. This can easily be tested by entering settings for a known working FTP or by taking the FTP settings the user entered and trying them in an FTP client.
Scheduled Events Fail to Trigger
- The scheduled date is wrong and has not passed.
- Not enough visitors are visiting to trigger the schedule. Someone must visit any page on the WordPress site on or after the scheduled time for the event to occur. If no one visits during the time-frame then the event may be missed or occur at an unscheduled time.
- The backup is failing. Test manual backups.
Warning: mysql_query() [function.mysql-query]: Unable to save result set in /www/wp-content/plugins/backupbuddy/backupbuddy.php on line 1673
- This is usually caused by a corrupt database or corrupt table(s) within said database. Citation of problem. Potential fixes:
- Repair the database/table using a tool such as phpMyAdmin.
- Add this line to wp-config.php to allow WordPress to repair tables: define('WP_ALLOW_REPAIR', true);
- Use the free plugin WP-dbManager to select the database to repair.
Warning: exec() has been disabled for security reasons in /www/wp-content/plugins/backupbuddy/lib/zip/zip.php on line 124
- exec() is disabled somewhere in PHP configuration. Ask the host to correct this or use cPanel to edit PHP settings to enable it if possible. See 'Fallback to Compatibility Mode' above.
Importing / Migrating with importbuddy.php
The source site is now redirecting to the destination site (or vice versa):
- This occurs if the new database settings were not entered during Step 4 of importbuddy.php. Because of this, both sites are now sharing the same database so one of them (usually source) is redirecting to the other (usually destination). importbuddy.php needs to be re-run inputting the source URL on Step 4 and using the source database settings. This will reconfigure the source database to use its proper URL. Next importbuddy.php needs to be run again inputting the destination URL on Step 4 with the NEW database settings for the new database. This way both sites will have their own database for their respective URLs.
ERROR #59233894: NOTE: Did you refresh after finishing the import? If so, [...]
- This error indicates that BackupBuddy was unable to detect the file 'backupbuddy_dat.php' in the current directory nor wp-content/uploads/temp_XXXXXX/backupbuddy_dat.php where XXXXXX are the random characters found in the ZIP file name. Verify the directory has write permissions. You can try editing importbuddy.php and changing the false in the following to true: $force_compatibility = false; You may also manually extract the ZIP file in the same directory using cPanel or your own software to continue to the next step.
500 Server Errors:
- .htaccess file is causing URLs to be redirected improperly or is malformed.
- PHP is not functioning or enabled for the site. Check with basic phpinfo().
- A 404 error is occurring but the server is not set up correctly to return a 404. Do sanity check with .htm file.
The backup zip file is not found:
- The zip file has been renamed to a non-BackupBuddy format.
- The zip file permissions are wrong. Ex: Not readable.
- The zip file is not in the same directory as importbuddy.php.
- The zip file has not finished uploading or was interrupted in transit. If BackupBuddy was used to send it try manually uploading.