Database Backup failing with mysqldump error 3

  • Resolved Jeffrey Schutzman

    (@jeffpyebrookcom)


    7 years, 2 months ago

    Database backup is failing with mysqldump error 3, can’t seem to get it to run. mysqldump from the command line will work.

    This is the log

    0000.000 (0) Opened log file at time: Fri, 21 Jul 2017 18:00:12 +0000 on https://learntodigitize.net
    0000.002 (0) UpdraftPlus WordPress backup plugin (https://updraftplus.com): 1.13.4 WP: 4.8 PHP: 7.0.18-0ubuntu0.16.04.1 (apache2handler, Linux balboa-nyc1 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64) MySQL: 5.7.19 WPLANG: en_US Server: Apache/2.4.18 (Ubuntu) safe_mode: 0 max_execution_time: 900 memory_limit: 192M (used: 11.5M | 2M) multisite: N openssl: OpenSSL 1.0.2g 1 Mar 2016 mcrypt: Y LANG: C ZipArchive::addFile: Y
    0000.003 (0) Free space on disk containing Updraft’s temporary directory: 33664.1 MB
    0000.006 (0) Tasks: Backup files: 0 (schedule: daily) Backup DB: 1 (schedule: daily)
    0000.010 (0) Requesting semaphore lock (d) (apparently not via scheduler)
    0000.015 (0) Semaphore (d, wp_options) was stuck, set lock time to 2017-07-21 18:00:12
    0000.017 (0) Semaphore (d, wp_options) reset to 1
    0000.019 (0) Set semaphore last lock (d) time to 2017-07-21 18:00:12
    0000.020 (0) Semaphore lock (d) complete
    0000.025 (0) Backup run: resumption=0, nonce=190c03515f03, begun at=1500660012 (0s ago), job type=backup
    0000.028 (0) Scheduling a resumption (1) after 300 seconds (1500660312) in case this run gets aborted
    0000.032 (0) This backup run is not intended for files – skipping
    0000.033 (0) Beginning creation of database dump (WordPress DB)
    0000.036 (0) Testing: /usr/bin/mysqldump
    0000.070 (0) Output: /*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */;\n/*!40103 SET TIME_ZONE=’+00:00′ */;\n/*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */;\n/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;\n/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE=’NO_AUTO_VALUE_ON_ZERO’ */;\n/*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */;\nDROP TABLE IF EXISTS wp_options;\n/*!40101 SET @saved_cs_client = @@character_set_client */;\n/*!40101 SET character_set_client = utf8 */;\nCRE (truncated – 1213 bytes total)
    0000.073 (0) Working binary mysqldump found: /usr/bin/mysqldump
    0000.083 (0) Table wp_options: Total expected rows (approximate): 13360
    0000.269 (0) Table wp_options: binary mysqldump finished (writes: 33) in 0.18 seconds
    0000.272 (0) Table wp_options: finishing file (backup_2017-07-21-1100_Balboa_Threadworks_190c03515f03-db-table-wp_options.table.gz – 403 KB)
    0000.278 (0) Table wp_users: Total expected rows (approximate): 2408
    0000.360 (0) Table wp_users: binary mysqldump finished (writes: 39) in 0.08 seconds
    0000.363 (0) Table wp_users: finishing file (backup_2017-07-21-1100_Balboa_Threadworks_190c03515f03-db-table-wp_users.table.gz – 148.1 KB)
    0000.369 (0) Table wp_usermeta: Total expected rows (approximate): 57994
    0000.611 (0) Table wp_usermeta: binary mysqldump finished (writes: 34) in 0.24 seconds
    0000.614 (0) Table wp_usermeta: finishing file (backup_2017-07-21-1100_Balboa_Threadworks_190c03515f03-db-table-wp_usermeta.table.gz – 418.9 KB)
    0000.619 (0) Table wp_commentmeta: Total expected rows (approximate): 0
    0000.638 (0) Table wp_commentmeta: binary mysqldump finished (writes: 31) in 0.02 seconds
    0000.640 (0) Table wp_commentmeta: finishing file (backup_2017-07-21-1100_Balboa_Threadworks_190c03515f03-db-table-wp_commentmeta.table.gz – 0.6 KB)
    0000.645 (0) Table wp_comments: Total expected rows (approximate): 32
    0000.668 (0) Table wp_comments: binary mysqldump finished (writes: 47) in 0.02 seconds
    0000.671 (0) Table wp_comments: finishing file (backup_2017-07-21-1100_Balboa_Threadworks_190c03515f03-db-table-wp_comments.table.gz – 1.7 KB)
    0000.683 (0) Table wp_links: Total expected rows (approximate): 0
    0000.704 (0) Table wp_links: binary mysqldump finished (writes: 39) in 0.02 seconds
    0000.706 (0) Table wp_links: finishing file (backup_2017-07-21-1100_Balboa_Threadworks_190c03515f03-db-table-wp_links.table.gz – 0.6 KB)
    0000.712 (0) Table wp_postmeta: Total expected rows (approximate): 87635
    0000.761 (0) Binary mysqldump: error (code: 3)
    0348.799 (1) Opened log file at time: Fri, 21 Jul 2017 18:06:01 +0000 on https://learntodigitize.net
    0348.800 (1) UpdraftPlus WordPress backup plugin (https://updraftplus.com): 1.13.4 WP: 4.8 PHP: 7.0.18-0ubuntu0.16.04.1 (apache2handler, Linux balboa-nyc1 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64) MySQL: 5.7.19 WPLANG: en_US Server: Apache/2.4.18 (Ubuntu) safe_mode: 0 max_execution_time: 900 memory_limit: 192M (used: 9.9M | 2M) multisite: N openssl: OpenSSL 1.0.2g 1 Mar 2016 mcrypt: Y LANG: C ZipArchive::addFile: Y
    0348.802 (1) Free space on disk containing Updraft’s temporary directory: 33656.5 MB
    0348.805 (1) Backup run: resumption=1, nonce=190c03515f03, begun at=1500660012 (349s ago), job type=backup, previous check-in=0.7s
    0348.808 (1) Scheduling a resumption (2) after 300 seconds (1500660661) in case this run gets aborted
    0348.811 (1) This backup run is not intended for files – skipping
    0348.812 (1) Resuming creation of database dump (WordPress DB)
    0348.818 (1) Table wp_options: corresponding file already exists; moving on
    0348.819 (1) Table wp_users: corresponding file already exists; moving on
    0348.820 (1) Table wp_usermeta: corresponding file already exists; moving on
    0348.822 (1) Table wp_commentmeta: corresponding file already exists; moving on
    0348.823 (1) Table wp_comments: corresponding file already exists; moving on
    0348.824 (1) Table wp_links: corresponding file already exists; moving on
    0348.838 (1) Table wp_postmeta: Total expected rows (approximate): 87635
    0348.909 (1) Binary mysqldump: error (code: 3)
    0680.785 (2) Opened log file at time: Fri, 21 Jul 2017 18:11:33 +0000 on https://learntodigitize.net
    0680.787 (2) UpdraftPlus WordPress backup plugin (https://updraftplus.com): 1.13.4 WP: 4.8 PHP: 7.0.18-0ubuntu0.16.04.1 (apache2handler, Linux balboa-nyc1 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64) MySQL: 5.7.19 WPLANG: en_US Server: Apache/2.4.18 (Ubuntu) safe_mode: 0 max_execution_time: 900 memory_limit: 192M (used: 11.5M | 2M) multisite: N openssl: OpenSSL 1.0.2g 1 Mar 2016 mcrypt: Y LANG: C ZipArchive::addFile: Y
    0680.788 (2) Free space on disk containing Updraft’s temporary directory: 33511.8 MB
    0680.791 (2) Backup run: resumption=2, nonce=190c03515f03, begun at=1500660012 (681s ago), job type=backup
    0680.793 (2) Scheduling a resumption (3) after 300 seconds (1500660993) in case this run gets aborted
    0680.797 (2) This backup run is not intended for files – skipping
    0680.799 (2) Resuming creation of database dump (WordPress DB)
    0680.804 (2) Table wp_options: corresponding file already exists; moving on
    0680.806 (2) Table wp_users: corresponding file already exists; moving on
    0680.807 (2) Table wp_usermeta: corresponding file already exists; moving on
    0680.808 (2) Table wp_commentmeta: corresponding file already exists; moving on
    0680.810 (2) Table wp_comments: corresponding file already exists; moving on
    0680.811 (2) Table wp_links: corresponding file already exists; moving on
    0680.815 (2) Table wp_postmeta: Total expected rows (approximate): 87635
    0680.874 (2) Binary mysqldump: error (code: 3)

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Contributor DNutbourne

    (@dnutbourne)

    7 years, 2 months ago

    Hi,

    Please could you ask your hosts if there is any further information on this error in the MySQL logs?

    Thread Starter Jeffrey Schutzman

    (@jeffpyebrookcom)

    7 years, 2 months ago

    I had saved the mysql log files, there isn’t anything of interest that I can see.

    Plugin Contributor DNutbourne

    (@dnutbourne)

    7 years, 2 months ago

    Hi,

    Apologies for the delay.

    The error that you are receiving idicates that the wp_postmeta table is corrupt in some way.
    This table will need to be repaired. You can use a plugin such as the following to do so:
    https://wordpress.org/plugins/wp-dbmanager/

    Thread Starter Jeffrey Schutzman

    (@jeffpyebrookcom)

    7 years, 2 months ago

    Sorry, that’s not the case.

    Executing mysqldump from the shell command line completes without error.

    Also, the result from “Analyze Table”, “Check Table”, and “Checksum Table” status as shown in PHPMyAdmin is without error.

    Plugin Author David Anderson

    (@davidanderson)

    7 years, 2 months ago

    Hi,

    The log shows that UpdraftPlus is running mysqldump from the shell, and that mysqldump is returning return code 3. The source code of mysqldump defines the return codes as:

    #define EX_USAGE 1
    #define EX_MYSQLERR 2
    #define EX_CONSCHECK 3
    #define EX_EOM 4
    #define EX_EOF 5 /* ferror for output file was got */
    #define EX_ILLEGAL_TABLE 6

    i.e. 3 is “CONSCHECK”, consistency check. Some sort of data integrity error.

    So, presumably you’re running mysqldump from the shell with a different set of parameters than UD uses, which doesn’t trigger whatever consistency check fails (which, unfortunately, no info gets returned about). You can get UD’s parameters by looking in the method backup_table_bindump() in wp-content/plugins/updraftplus/backup.php.

    David

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Database Backup failing with mysqldump error 3’ is closed to new replies.