BackupBuddy: Error Codes - Revision history

Dustin at 04:34, April 3, 2013

2013-04-03T04:34:05Z

485ambiguous: /* 3382 */

2013-03-02T10:09:53Z

3382

485ambiguous: /* 3382 */

2013-03-02T10:00:28Z

3382

Dustin at 10:23, January 6, 2013

2013-01-06T10:23:12Z

Dustin at 23:04, November 12, 2012

2012-11-12T23:04:15Z

Dustin at 23:03, November 12, 2012

2012-11-12T23:03:48Z

Akers: added 3488439, and fixed spacing directly around it

2012-10-19T15:14:31Z

added 3488439, and fixed spacing directly around it

Akers at 15:13, October 19, 2012

2012-10-19T15:13:35Z

Dustout at 09:32, September 26, 2012

2012-09-26T09:32:03Z

Dustin at 06:48, May 9, 2012

2012-05-09T06:48:45Z

← Older revision		Revision as of 04:34, April 3, 2013
Line 233:		Line 233:
	"Error #9033: The pre-backup initialization did not fully complete. Check for any errors above or in logs. Verify permissions & that there is enough server memory. See the BackupBuddy "Server Information" page to help assess your server."		"Error #9033: The pre-backup initialization did not fully complete. Check for any errors above or in logs. Verify permissions & that there is enough server memory. See the BackupBuddy "Server Information" page to help assess your server."
	* One known cause: Server ran out of memory at some point during the pre_backup() initialization procedure, possibly during importbuddy generation. Check PHP error log for memory errors. Increase server memory for probably fix.		* One known cause: Server ran out of memory at some point during the pre_backup() initialization procedure, possibly during importbuddy generation. Check PHP error log for memory errors. Increase server memory for probably fix.
		+
		+	==9034==
		+	* Check file permissions on the reported file and its directory. If still experiencing problems verify ownership and/or that suphp is installed and properly configured on the server. Contact host for details.

@@ Line 21: / Line 21: @@
 *** If you cannot make the file readable and you cannot exclude the folder (because it contains other files that you need) then you will need to consult your host support to try and resolve what is the issue with the file.
 *** If you are having trouble interpreting the diagnostic information in the Advanced Details then please create a topic in the BackupBuddy Forum and we can help explain it to you - however, this doesn't mean to say that we can resolve the issue as it relates to your files and server.
-** Verify permissions are set correctly for /wp-content/uploads/ recursively to 755.
+** Verify permissions are set correctly for /wp-content/uploads/ and all subdirectories/files therein - the server process running the backup needs to be able to access the directories and read/write files/directories - commonly this may mean 755 permissions for directories and 644 permissions for files.
 ** Verify allowed disk usage isn't close or exceeded. (ie Your hosting account is limited to 5GB and you've used 4.95GB.)
 ** Reducing backup size often helps. (directory exclusion, etc)

@@ Line 4: / Line 4: @@
 * The 3382 error literally means that both command line zip AND pclzip were unable to create a .zip file and failed for some reason.
 * Possible causes:
 ** Command line zip is being actively killed. (Cheapest packages at Godaddy kill off exec() within about 10 seconds, throwing the user into compatibility mode which cannot handle larger sites).
 ** Permissions may be blocking backup file creation. Make sure permissions are set to 755 for the /wp-content/uploads/ directory recursively.
@@ Line 9: / Line 10: @@
 ** There may be one or more files/folders being included in the backup which neither the native zip command nor the pclzip function are able to access, e.g., unreadable files or broken symbolic links
 * Possible solutions:
-** If you have BackupBuddy Version 2.2.29 or later then visit the Settings page and enable the Alternative Zip System option and save. Then repeat a Full backup and study the Advanced Details for indications of failure.
+** If you have BackupBuddy Version 3.1.8.3 or later then the Status Log of a manual backup will contain detailed information concerning the problem, which may be just an exit code or an exit code and information on files and may indicate problems such as the file being unreadable - you should check the file(s) noted and determine what the file(s) are so that you can determine how to proceed.
 *** For the native zip command alternatives there will usually be an exit code followed by some general descriptive text concerning the reason for failure (such as being unable to read a file, lack of disk space, etc.).
 *** If the failure is file based then unfortunately at present we are unable to isolate the specific file details from this command. However, the backup will fall back to the Compatibility Mode and the failure indication from that will almost certainly provide a specific indication of the file (including the absolute file path) that is causing the issue. In such a case you must correct the issue by making the file readable if that is appropriate for the file or alternatively use the Exclusions on the Settings page to exclude the folder that contains the bad file.

← Older revision		Revision as of 10:23, January 6, 2013
Line 221:		Line 221:
	==9032==		==9032==
	''BackupBuddy Error #9032: You have not set a password to download this script yet. Please do so on the Settings page. You should have been prompted for a password when you clicked to download this script. If you are seeing this then most likely another plugin is loading its javascript on our plugin page causing it to break. Try disabling all other plugins to see if that fixes it. If so then turn them back on one by one until you find the offending plugin. You may also view your browser javascript error console to check for any script errors to help diagnose the issue.''		''BackupBuddy Error #9032: You have not set a password to download this script yet. Please do so on the Settings page. You should have been prompted for a password when you clicked to download this script. If you are seeing this then most likely another plugin is loading its javascript on our plugin page causing it to break. Try disabling all other plugins to see if that fixes it. If so then turn them back on one by one until you find the offending plugin. You may also view your browser javascript error console to check for any script errors to help diagnose the issue.''
		+
		+
		+	==9033==
		+	"Error #9033: The pre-backup initialization did not fully complete. Check for any errors above or in logs. Verify permissions & that there is enough server memory. See the BackupBuddy "Server Information" page to help assess your server."
		+	* One known cause: Server ran out of memory at some point during the pre_backup() initialization procedure, possibly during importbuddy generation. Check PHP error log for memory errors. Increase server memory for probably fix.

@@ Line 212: / Line 212: @@
 **2 : Make sure you have plenty of free disk space.
 **3 : Upgrade to the latest version of BackupBuddy to make sure you are not encountering any old bugs or we have improved workarounds for your server issue.
 *Related forum threads
 **[http://ithemes.com/forum/index.php?/topic/13796-error-5445589-invalid-backup-serial/ File permissions causing 5445589 error]
 **[http://ithemes.com/forum/index.php?/topic/14834-error-5445589-invalid-backup-serial-0i64w23keq-fatal-error/ Increase the available disk space]

@@ Line 205: / Line 205: @@
 ** One or more tables that was attempted to be imported already existed.
-==5445589==
+==9031==
-'''Error #5445589 – Invalid b/u serial Verify b/u directory writer permission'''
+"Error #9031. Invalid backup serial (xxxxxxxxxx). Please check directory permissions and your PHP error_log as an early backup function (such as pre_backup) may have failed. Fatal error."
-*This basically means there was a mismatch where the unique backup serial that ajax passed was not found server-side. There are 3 known reasons and fixes for this.
+* This is a fatal error which will halt the backup process. You must fix whatever is causing it before BackupBuddy can continue.
-**1 : Fix the file and folder permissions on all your BackupBuddy folders and the wp-content/uploads folder.
+* This basically means that when BackupBuddy tried to load backup information for the unique backup your browser requested information on, no information was found. Please try the following fixes:
-**2 : Increase the available disk space.
+**1 : Fix the file and folder permissions on all your BackupBuddy folders and the wp-content/uploads folder to allow proper writing permissions.
-**3 : Upgrade to the latest version of BackupBuddy. There have been updates to BackupBuddy to address this error more efficiently.
+**2 : Make sure you have plenty of free disk space.
 *Related forum threads
 **[http://ithemes.com/forum/index.php?/topic/13796-error-5445589-invalid-backup-serial/ File permissions causing 5445589 error]
 **[http://ithemes.com/forum/index.php?/topic/14834-error-5445589-invalid-backup-serial-0i64w23keq-fatal-error/ Increase the available disk space]
 ==4543849498==

@@ Line 198: / Line 198: @@
 * This table is not set up properly. All tables should have a PRIMARY key and/or a UNIQUE key. Mysql automatically returns the first fully unique key if available if a primary key does not exist.
 * If a plugin created the reported table contact the author to have this corrected.
 ==5445589==