Scheduled Backups Fail on wp_posts
-
Manual backups work fine, but scheduled backups keep failing on wp_posts. I’ve increase memory and not sure what else to do to troubleshoot.
Viewing 6 replies - 1 through 6 (of 6 total)
-
This started after switching servers, in case that helps. The undefined index error is new. I’ve also tried maxing out the max execution time.
WordPress version: 4.9.9 BackWPup version: 3.6.6 PHP version: 7.3.0-2+ubuntu18.04.1+deb.sury.org+1??(64bit) MySQL version: 10.2.21-MariaDB-1:10.2.21+maria~bionic cURL version: 7.58.0 cURL SSL version: OpenSSL/1.1.1a WP-Cron url: https://www.[redacted]/wp/wp-cron.php Server self connect: Response Test O.K. Document root: /srv/www/[redacted]/releases/20190110182729/web Temp folder: /srv/www/[redacted]/releases/20190110182729/web/app/uploads/backwpup-ec6879-temp/ Log folder: /srv/www/[redacted]/releases/20190110182729/web/app/uploads/backwpup-ec6879-logs/ Server: nginx/1.15.6 Operating System: Linux PHP SAPI: fpm-fcgi Current PHP user: web Maximum execution time: 300 seconds BackWPup maximum script execution time: 25 seconds Alternative WP Cron: Off Disabled WP Cron: On CHMOD Dir: 0755 Server Time: 14:18 Blog Time: 09:18 Blog Timezone: America/New_York Blog Time offset: -5 hours Blog language: en-US MySQL Client encoding: utf8mb4 PHP Memory limit: 512M WP memory limit: 512M WP maximum memory limit: 512M Memory in use: 6.00 MB Loaded PHP Extensions:: Core, PDO, Phar, Reflection, SPL, SimpleXML, Zend OPcache, calendar, cgi-fcgi, ctype, curl, date, dom, exif, fileinfo, filter, ftp, gd, gettext, hash, iconv, igbinary, json, libxml, mbstring, memcached, msgpack, mysqli, mysqlnd, openssl, pcre, pdo_mysql, posix, readline, session, shmop, sockets, sodium, standard, sysvmsg, sysvsem, sysvshm, tokenizer, wddx, xml, xmlreader, xmlrpc, xmlwriter, xsl, zip, zlib [INFO] BackWPup 3.6.6; A project of Inpsyde GmbH [INFO] WordPress 4.9.9 on https://www.[redacted]/wp/ [INFO] Log Level: Debug [INFO] BackWPup job: Database Backup 2; DBDUMP [INFO] Runs with user: (0) [INFO] Cron: 10 * * * *; Next: Fri, 11 Jan 2019 @ 09:10 [INFO] BackWPup job started from wp-cron [INFO] PHP ver.: 7.3.0-2+ubuntu18.04.1+deb.sury.org+1 (64bit); cli; Linux [INFO] Maximum PHP script execution time is 0 seconds [INFO] MySQL ver.: 10.2.21-MariaDB-1:10.2.21+maria~bionic [INFO] Web Server: [INFO] curl ver.: 7.58.0; OpenSSL/1.1.1a [INFO] Temp folder is: /srv/www/[redacted]/releases/20190110182729/web/app/uploads/backwpup-ec6879-temp/ [INFO] Logfile is: /srv/www/[redacted]/releases/20190110182729/web/app/uploads/backwpup-ec6879-logs/backwpup_log_ec6879_2019-01-11_08-15-03.html [INFO] Backup file is: /srv/www/[redacted]/releases/20190110182729/web/app/uploads/backwpup-ec6879-temp/Database_2019-01-11_08-15-03-AM_VXWGQ6KE06.tar.gz [11-Jan-2019 08:15:03] 1. Try to backup database … [11-Jan-2019 08:15:03] Connected to database [redacted]_production on localhost [11-Jan-2019 08:15:03] Backup database table "wp_commentmeta" with "0" records [11-Jan-2019 08:15:03] Backup database table "wp_comments" with "0" records [11-Jan-2019 08:15:03] Backup database table "wp_ewwwio_images" with "~52005" records [11-Jan-2019 08:15:03] Backup database table "wp_links" with "0" records [11-Jan-2019 08:15:03] Backup database table "wp_options" with "752" records [11-Jan-2019 08:15:03] Backup database table "wp_pods_[redacted]" with "49" records [11-Jan-2019 08:15:03] Backup database table "wp_pods_[redacted]" with "253" records [11-Jan-2019 08:15:03] Backup database table "wp_pods_[redacted]" with "9" records [11-Jan-2019 08:15:03] Backup database table "wp_pods_[redacted]" with "2" records [11-Jan-2019 08:15:03] Backup database table "wp_pods_[redacted]" with "60" records [11-Jan-2019 08:15:03] Backup database table "wp_pods_[redacted]" with "8" records [11-Jan-2019 08:15:03] Backup database table "wp_pods_[redacted]" with "222" records [11-Jan-2019 08:15:03] Backup database table "wp_pods_[redacted]" with "8" records [11-Jan-2019 08:15:03] Backup database table "wp_pods_[redacted]" with "239" records [11-Jan-2019 08:15:03] Backup database table "wp_pods_[redacted]" with "557" records [11-Jan-2019 08:15:03] Backup database table "wp_pods_[redacted]" with "3" records [11-Jan-2019 08:15:03] Backup database table "wp_pods_[redacted]" with "34" records [11-Jan-2019 08:15:03] Backup database table "wp_pods_[redacted]" with "0" records [11-Jan-2019 08:15:03] Backup database table "wp_pods_[redacted]" with "114" records [11-Jan-2019 08:15:03] Backup database table "wp_pods_[redacted]" with "7" records [11-Jan-2019 08:15:03] Backup database table "wp_podsrel" with "9723" records [11-Jan-2019 08:15:03] Backup database table "wp_postmeta" with "94825" records [11-Jan-2019 08:15:04] Backup database table "wp_posts" with "16453" records [11-Jan-2019 13:15:04 America/New_York] PHP Fatal error: Allowed memory size of 73400320 bytes exhausted (tried to allocate 258048 bytes) in /srv/www/[redacted]/releases/20190110182729/web/app/plugins/backwpup/inc/class-mysqldump.php on line 514 [11-Jan-2019 08:15:04] ERROR: Allowed memory size of 73400320 bytes exhausted (tried to allocate 258048 bytes) [11-Jan-2019 08:30:04] WARNING: Job restarts due to inactivity for more than 5 minutes. [11-Jan-2019 08:30:04] 2. Try to backup database … [11-Jan-2019 08:30:04] Connected to database [redacted]_production on localhost [11-Jan-2019 13:30:05 America/New_York] PHP Fatal error: Allowed memory size of 73400320 bytes exhausted (tried to allocate 258048 bytes) in /srv/www/[redacted]/releases/20190110182729/web/app/plugins/backwpup/inc/class-mysqldump.php on line 514 [11-Jan-2019 08:30:05] ERROR: Allowed memory size of 73400320 bytes exhausted (tried to allocate 258048 bytes) [11-Jan-2019 13:30:05 America/New_York] PHP Notice: Undefined index: file in /srv/www/[redacted]/releases/20190110182729/web/app/plugins/backwpup/inc/class-job.php on line 719 [11-Jan-2019 13:30:05 America/New_York] PHP Notice: Undefined index: line in /srv/www/[redacted]/releases/20190110182729/web/app/plugins/backwpup/inc/class-job.php on line 720 [11-Jan-2019 13:30:05 America/New_York] PHP Warning: posix_isatty(): supplied resource is not a valid stream resource in phar:///usr/bin/wp/vendor/wp-cli/php-cli-tools/lib/cli/Shell.php on line 94 [11-Jan-2019 13:30:05 America/New_York] PHP Warning: posix_isatty(): expects argument 1 to be a valid stream resource in phar:///usr/bin/wp/vendor/wp-cli/php-cli-tools/lib/cli/Shell.php on line 94 [11-Jan-2019 08:30:05] WARNING: Packets out of order. Expected 8 received 56. Packet size=3420933 [11-Jan-2019 08:45:04] WARNING: Job restarts due to inactivity for more than 5 minutes. [11-Jan-2019 08:45:04] ERROR: Step aborted: too many attempts! [11-Jan-2019 08:45:04] 1. Trying to generate a manifest file … [11-Jan-2019 08:45:04] Added manifest.json file with 6.06 KB to backup file list. [11-Jan-2019 08:45:04] 1. Trying to create backup archive … [11-Jan-2019 08:45:04] Compressing files as TarGz. Please be patient, this may take a moment. [11-Jan-2019 08:45:04] Adding Extra files to Archive [11-Jan-2019 08:45:04] Backup archive created. [11-Jan-2019 08:45:04] Archive size is 2.25 KB. [11-Jan-2019 08:45:04] 2 Files with 6.28 KB in Archive. [11-Jan-2019 08:45:04] 1. Try to send backup file to Dropbox … [11-Jan-2019 08:45:04] Call to users/get_current_account [11-Jan-2019 08:45:05] [redacted] [11-Jan-2019 08:45:05] Call to users/get_space_usage [11-Jan-2019 08:45:05] 8.29 TB available on your Dropbox [11-Jan-2019 08:45:05] Uploading to Dropbox … [11-Jan-2019 08:45:05] Call to files/upload, with 2 KB of data, with parameters: {"path":"\/[redacted]\/Database_2019-01-11_08-15-03-AM_VXWGQ6KE06.tar.gz","mode":"overwrite"} [11-Jan-2019 08:45:07] Backup transferred to /[redacted]/Database_2019-01-11_08-15-03-AM_VXWGQ6KE06.tar.gz [11-Jan-2019 08:45:07] Call to files/list_folder, with parameters: {"path":"\/[redacted]\/"} [11-Jan-2019 08:45:08] 1. Trying to send backup file to S3 Service … [11-Jan-2019 08:45:08] Connected to S3 Bucket "[redacted]-backups" in [11-Jan-2019 08:45:08] Checking for not aborted multipart Uploads … [11-Jan-2019 08:45:08] Starting upload to S3 Service … [11-Jan-2019 08:45:08] Backup transferred to https://s3.amazonaws.com/[redacted]-backups/[redacted]/Database_2019-01-11_08-15-03-AM_VXWGQ6KE06.tar.gz. [11-Jan-2019 08:45:08] One old log deleted [11-Jan-2019 08:45:08] ERROR: Job has ended with errors in 1805 seconds. You must resolve the errors for correct execution.
Viewing 6 replies - 1 through 6 (of 6 total)
- The topic ‘Scheduled Backups Fail on wp_posts’ is closed to new replies.
