Now backups unsuccessful after years successful

  • Resolved eftcolumbus

    (@eftcolumbus)


    3 years, 9 months ago

    Hi, over the past month my email alert says it was apparently unsuccessful. I’ve been doing a weekly backup to S3 for years and it has been failing every week for about month. My hosting and S3 accounts have not changed. When I click Test S3 Settings it says:

    S3 settings test result: Success: Region: us-east-2: We accessed the bucket, and were able to create files within it. The communication with Amazon S3 was encrypted.

    Currently it is now saving most of my backup to my /backup folder on my server. When I check S3 the last one is from January 17. I am having no other issues with my S3 account in other usages.

    On the backup I just tried today, it always says “moving on” at the end of each line until I get to this (NOTE: I replaced the domain name with “mydomain”)

    3744.307 (12) The final database file (/home/nginx/domains/mydomain.com/public/wp-content/backup/backup_2021-02-15-1258_mydomain_4aeb53402275-db.gz) exists, but was apparently not modified within the last 30 seconds (time_mod=1613415341, time_now=1613415667, diff=326). Thus we assume that another UpdraftPlus terminated; thus we will continue.
    3744.353 (12) backup_2021-02-15-1258_mydomain_4aeb53402275-db-table-hp_options.table.gz (1/279): adding to final database dump
    3744.665 (12) backup_2021-02-15-1258_mydomain_4aeb53402275-db-table-hp_users.table.tmpr4920.gz (2/279): adding to final database dump
    3744.716 (12) backup_2021-02-15-1258_mydomain_4aeb53402275-db-table-hp_users.table.gz (3/279): adding to final database dump
    3744.720 (12) backup_2021-02-15-1258_mydomain_4aeb53402275-db-table-hp_usermeta.table.gz (4/279): adding to final database dump
    3745.119 (12) backup_2021-02-15-1258_mydomain_4aeb53402275-db-table-hp_actionscheduler_actions.table.tmpr105359.gz (5/279): adding to final database dump
    3745.145 (12) backup_2021-02-15-1258_mydomain_4aeb53402275-db-table-hp_actionscheduler_actions.table.gz (6/279): adding to final database dump
    3745.149 (12) backup_2021-02-15-1258_mydomain_4aeb53402275-db-table-hp_actionscheduler_claims.table.tmpr26909.gz (7/279): adding to final database dump
    3745.151 (12) backup_2021-02-15-1258_mydomaine_4aeb53402275-db-table-hp_actionscheduler_claims.table.gz (8/279): adding to final database dump
    3745.153 (12) backup_2021-02-15-1258_mydomain_4aeb53402275-db-table-hp_actionscheduler_groups.table.tmpr6.gz (9/279): adding to final database dump
    3745.155 (12) backup_2021-02-15-1258_mydomain_4aeb53402275-db-table-hp_actionscheduler_groups.table.gz (10/279): adding to final database dump
    3745.158 (12) backup_2021-02-15-1258_mydomain_4aeb53402275-db-table-hp_actionscheduler_logs.table.tmpr85448.gz (11/279): adding to final database dump
    3745.192 (12) backup_2021-02-15-1258_mydomain_4aeb53402275-db-table-hp_actionscheduler_logs.table.gz (12/279): adding to final database dump
    3745.195 (12) backup_2021-02-15-1258_mydomain_4aeb53402275-db-table-hp_commentmeta.table.tmpr122727.gz (13/279): adding to final database dump
    3745.203 (12) backup_2021-02-15-1258_mydomain_4aeb53402275-db-table-hp_commentmeta.table.gz (14/279): adding to final database dump
    3745.206 (12) backup_2021-02-15-1258_mydomain_4aeb53402275-db-table-hp_comments.table.gz (15/279): adding to final database dump
    3745.444 (12) backup_2021-02-15-1258_mydomain_4aeb53402275-db-table-hp_links.table.tmpr0.gz (16/279): adding to final database dump
    3745.448 (12) backup_2021-02-15-1258_mydomain_4aeb53402275-db-table-hp_links.table.gz (17/279): adding to final database dump
    3745.451 (12) backup_2021-02-15-1258_mydomain_4aeb53402275-db-table-hp_ms_snippets.table.tmpr0.gz (18/279): adding to final database dump
    3745.454 (12) backup_2021-02-15-1258_mydomain_4aeb53402275-db-table-hp_ms_snippets.table.gz (19/279): adding to final database dump
    3745.456 (12) backup_2021-02-15-1258_mydomain_4aeb53402275-db-table-hp_postmeta.table.gz (20/279): adding to final database dump
    4103.885 (13) Opened log file at time: Mon, 15 Feb 2021 19:07:06 +0000 on https://mydomain.com
    4103.888 (13) UpdraftPlus WordPress backup plugin (https://updraftplus.com): 1.16.47 WP: 5.6.1 PHP: 7.3.11 (fpm-fcgi, Linux ngx.mydomain.com 2.6.32-042stab127.2 #1 SMP Thu Jan 4 16:41:44 MSK 2018 x86_64) MySQL: 10.1.48-MariaDB WPLANG: en_US Server: nginx/1.17.5 safe_mode: 0 max_execution_time: 900 memory_limit: 800M (used: 32.5M | 18.5M) multisite: N openssl: OpenSSL 1.0.2k 26 Jan 2017 mcrypt: Y LANG: ZipArchive::addFile: Y
    4103.890 (13) Free space on disk containing Updraft’s temporary directory: 6745 MB
    4103.893 (13) Requesting backup semaphore lock (4aeb53402275)
    4103.895 (13) [Lock (updraft_lock_4aeb53402275, hp_options) acquired] info
    4103.898 (13) Backup run: resumption=13, nonce=4aeb53402275, file_nonce=4aeb53402275 begun at=1613411922 (4104s ago), job type=backup
    4103.901 (13) [Updraftplus] The backup is being aborted for a repeated failure to progress.
    4103.903 (13) An error condition has occurred for the first time during this job
    4103.905 (13) [Lock option (updraft_lock_4aeb53402275, hp_options) released] info
    4103.908 (13) An email has been scheduled for this job, because we are in debug mode
    4103.910 (13) Fetching RSS news feed
    4104.011 (13) Fetched RSS news feed; result is a: SimplePie
    4104.061 (13) Sending email (‘Files (database backup has not completed) (Full backup)’) report (attachments: 1, size: 556.2 KB) to: busin…
    4105.174 (13) The backup attempt has finished, apparently unsuccessfully

Viewing 15 replies - 1 through 15 (of 23 total)
  • Plugin Contributor bcrodua

    (@bcrodua)

    Hi,

    It shows that the backup process is timed out or killed off.

    Please ask your hosts/server admin to investigate their PHP error logs. These logs should contain more information on the exact issue that is causing the backup process to halt.

    Kind Regards,
    Bryle

    Thread Starter eftcolumbus

    (@eftcolumbus)

    Thank you. My web admin checked and said according to our PHP log there are no errors being thrown at all. Is there anything else to check?

    Thread Starter eftcolumbus

    (@eftcolumbus)

    Hi did you see what I replied that there are no PHP errors being thrown. What else can we do?

    @eftcolumbus
    Could you try to reduce the backup archive split size. This will split the backup into smaller, more manageable files. To do this, open the ‘expert settings’ section of the UpdraftPlus Settings tab, and find the ‘split backups every’ option. Set this to 25Mb, save your settings and run a new process.

    Thread Starter eftcolumbus

    (@eftcolumbus)

    I actually did this yesterday. I was at 400 i went to 200, 100, then 25 (based on responses to other people reporting the same thing). And they were all still unsuccessful.

    Thread Starter eftcolumbus

    (@eftcolumbus)

    I forgot I also saw in this forum say that reverting back from 7.4 PHP fixed the problem, I checked and I’m at 7.3.11, not 7.4

    @eftcolumbus
    Please could you install the free WP Crontrol plugin, and then open WP-Admin->Tools->Cron Events?

    Does it look like there are any errors?

    If there are, could you try adding the following line of code to your wp-config.php file (above the ‘stop editing’ line):
    define( ‘ALTERNATE_WP_CRON’, true );

    This will enable the alternative WordPress Cron system. This is designed to allow scheduled tasks to be processed when the main WP Cron is not able to run.

    Thread Starter eftcolumbus

    (@eftcolumbus)

    Thanks, so I asked my webadmin to take a look at wp-cron and he isn’t seeing any errors.

    He said

    I am not seeing any issues with the wp cron event list. wp cron test returns:

    Success: WP-Cron spawning is working as expected.

    I literally have 52 plugins so I’m always hesitant to add another unless I have no other options. With the cron success test above, is it still absolutely necessary to add another plugin?

    @eftcolumbus

    If your wp cron events list isn’t showing any errors then that probably rules out any issues with your scheduler.

    Are you able to paste your full log?

    Can you use a tool such as: https://pastebin.pl

    Thread Starter eftcolumbus

    (@eftcolumbus)

    OK here is a 1-time link, not a fan of sending logs on open forums like this but hopefully since you are online right now you will click through first.

    https://1ty.me/PFoRRaAK

    @eftcolumbus
    Your log shows this:

    “1903.227 (6) Failed to get backup job lock; possible overlapping resumptions – will abort this instance”

    Are you asking UpdraftPlus to do backups in quick successions or are you backing up another site around the same time (if you have more than once site please leave at least one hour between backups)

    Thread Starter eftcolumbus

    (@eftcolumbus)

    i use it once a week on Sunday mornings and I only use it for one domain, so no and no.

    Can you ask your hosts for the PHP error logs?

    Have you added a password to your htaccess?

    Thread Starter eftcolumbus

    (@eftcolumbus)

    They say there are no PHP errors related to Updraft in the error logs for the day of, day before, or day after the unsuccessful backup on Feb 14 for which I sent you the log. So nothing on Feb 13, 14, or 15. Do you want to see other PHP errors around those days?

    Also he said we are using NGINX not Apache so no password on htacess

    Apologies for the delay,

    I don’t think more PHP logs will tell us much.

    Is it possible that you still had a backup running when I asked you to do a new one (You said that you backup on a Sunday Morning and I asked you to run one on the Sunday evening) Sometimes, if there is an issue, backups can run for a couple of days.

    Have you done a backup since, does it show the same issue?

Viewing 15 replies - 1 through 15 (of 23 total)
  • The topic ‘Now backups unsuccessful after years successful’ is closed to new replies.