UpdraftPlus Home › Forums › Paid support forum – UpdraftPlus backup plugin › The backup is being aborted for a repeated failure to progress.
- This topic has 3 replies, 2 voices, and was last updated 3 years, 9 months ago by Bryle Crodua.
-
AuthorPosts
-
July 23, 2020 at 4:32 pm #625680Paul WhinneryParticipant
I have two physical servers. I’ve got Updraft working great on one of them (a Synology NAS). However, I keep getting failed backups on my other physical server — which is running SUSE Linux and has multiple virtual Apache servers running wordpress. Here’s the final log entries. Can you point me to what I need to do to fix this?
3611.785 (11) Table wp_revslider_navigations: corresponding file already exists; moving on
3611.785 (11) Table wp_revslider_navigations_bkp: corresponding file already exists; moving on
3611.785 (11) Table wp_revslider_sliders: corresponding file already exists; moving on
3611.785 (11) Table wp_revslider_sliders_bkp: corresponding file already exists; moving on
3611.785 (11) Table wp_revslider_slides: corresponding file already exists; moving on
3611.785 (11) Table wp_revslider_slides_bkp: corresponding file already exists; moving on
3611.785 (11) Table wp_revslider_static_slides: corresponding file already exists; moving on
3611.785 (11) Table wp_revslider_static_slides_bkp: corresponding file already exists; moving on
3611.785 (11) Table wp_sgpb_subscribers: corresponding file already exists; moving on
3611.785 (11) Table wp_sgpb_subscription_error_log: corresponding file already exists; moving on
3611.785 (11) Table wp_wpmailsmtp_tasks_meta: corresponding file already exists; moving on
3611.785 (11) Table wp_yoast_indexable: corresponding file already exists; moving on
3611.785 (11) Table wp_yoast_indexable_hierarchy: corresponding file already exists; moving on
3611.785 (11) Table wp_yoast_migrations: corresponding file already exists; moving on
3611.785 (11) Table wp_yoast_primary_term: corresponding file already exists; moving on
3611.785 (11) Table wp_yoast_seo_links: corresponding file already exists; moving on
3611.785 (11) Table wp_yoast_seo_meta: corresponding file already exists; moving on
3611.785 (11) The final database file (/srv/www/htdocs/cvd19claim/wp-content/updraft/backup_2020-07-23-1001_Elias_LLC_d4018c72fad8-db.gz) exists, but was apparently not modified within the last 30 seconds (time_mod=1595519741, time_now=1595520095, diff=354). Thus we assume that another UpdraftPlus terminated; thus we will continue.
3611.785 (11) PHP function is disabled; abort expected: gzopen()
3611.786 (11) backup_2020-07-23-1001_Elias_LLC_d4018c72fad8-db-table-wp_options.table.gz (1/37): adding to final database dump
3611.786 (11) PHP Fatal error (Error) has occurred. Error Message: Call to undefined function gzopen() (Code: 0, line 1744 in /srv/www/htdocs/cvd19claim/wp-content/plugins/updraftplus/backup.php)
3611.786 (11) An error condition has occurred for the first time during this job
3983.376 (12) Opened log file at time: Thu, 23 Jul 2020 16:07:47 +0000 on https://www.cvd19claim.com
3983.376 (12) UpdraftPlus WordPress backup plugin (https://updraftplus.com): 2.16.27.24 WP: 5.4.2 PHP: 7.2.5 (apache2handler, Linux prime 4.12.14-lp151.28.52-default #1 SMP Wed Jun 10 15:32:08 UTC 2020 (464fb5f) x86_64) MySQL: 10.2.32-MariaDB WPLANG: en_US Server: Apache safe_mode: 0 max_execution_time: 900 memory_limit: 256M (used: 43.9M | 6.3M) multisite: N openssl: OpenSSL 1.1.0i-fips 14 Aug 2018 mcrypt: N LANG: ZipArchive::addFile: Y
3983.377 (12) Free space on disk containing Updraft’s temporary directory: 1876497.1 MB
3983.377 (12) Backup run: resumption=12, nonce=d4018c72fad8, file_nonce=d4018c72fad8 begun at=1595516484 (3983s ago), job type=backup
3983.378 (12) [Updraftplus] The backup is being aborted for a repeated failure to progress.
3983.378 (12) An error condition has occurred for the first time during this job
3983.380 (12) Sending email (‘Files (database backup has not completed) (Full backup)’) report (attachments: 1, size: 52.2 KB) to: paul@…July 23, 2020 at 4:32 pm #625681Paul WhinneryParticipantThis reply has been marked as moderator-only.July 23, 2020 at 6:17 pm #625742Paul WhinneryParticipantI restarted the apache webserver and the next backup that I tried worked perfectly. No explanation — but the system healed itself.
July 24, 2020 at 12:11 pm #626190Bryle CroduaModeratorHi Paul,
Glad it is working now.
Please let us know here if you continue to get the same issue.
Best Wishes,
Bryle -
AuthorPosts
- The topic ‘The backup is being aborted for a repeated failure to progress.’ is closed to new replies.