Backups failing – Continually Scheduling a resumption

Hi there,

Could you please tell me if the backup is being stored locally or sent to remote storage?
If you are using remote storage please let me know which service you are using for this.

Best regards,

Nick

Hi Nick, thank you for your speedy reply. I’m just trying to back up to local storage when I’m getting these errors, and we have plenty of space.

We do have remote backups scheduled to a Google drive, weekly full backup and daily database only backups. I don’t have access to that storage, but it looks like those have been failing too. The last one was Oct 21.

I notice that you are using a lite speed server.

Can you try adding the following to your .htaccess;

RewriteRule .* - [E=noabort:1]?

I have added that RewriteRule to the top level .htaccess file, still the same issue persists.

Previously with the same lite speed server Updraft Plus worked without issue. That changes sometime in October. The last backup I have is from October 21st. So somewhere around that time depending on when I updated plugins I’m thinking there might have been a change to that update which is causing the issue.

I even tried just now only backing up the database, which is pretty small and that failed in the same way.

I’m just looking in the wp-content > updraft folder and I see that there is another .htaccess file there. Was that the one that I was supposed to add the RewriteRule to? The reply I got didn’t specify so I assumed it was the top level file.

I’m seeing files in the wp-content > updraft folder that look like backups, but none of them have the date of the two files that are showing up in the Updraft dashboard. There are only 2 backups showing in the WP admin Updraft dashboard, Oct 15 & 21st. I don’t see files with that date when looking in the folder on the server. It looks like these files are all from 2021 from the file names (e.g. backup_2021-11-03-1622_ with site name and guid added after the _), but in the date column it says 5/8/24 for all of them. Can I safely delete those old files?

Using the same host, also using a Lite Speed Server another site running Updraft v1.24.2 works fine as it always has (on both sites), but the site having the problem is using Updraft Version 1.24.7. So something broke in one of those versions after v1.24.2.

• This reply was modified 1 week, 3 days ago by DonnaMiller. Reason: Added additional information
• This reply was modified 1 week, 3 days ago by DonnaMiller. Reason: Added additional info about versions

Hi Donna,

Apologies, I was off for a few days so I’m just catching up now.

Litespeed servers have some known issues with WordPress processes and can be patchy.
The .htaccess fix does work in some instances, I would also like to suggest an alternative.

The issue usually relates to connection timeouts so this fix helps manage performance.
Please go to Settings >> Expert settings >> Show expert settings >> Split archives every:

Change this figure to a low number like 25. It will help the backups process more quickly.
My apologies if it is already a low number, the information isn’t available in the log file.

For the moment I wouldn’t delete any backups until we’ve fixed the current issue for you.
Once backups are running correctly again it will be safer to have a clean up of old files.

Please let me know if this adjustment helps the backups to run.

Best regards,

Nick

Hi Nick, no worries. I changed the “Split Archives Every” option to 25 (it was 400) and tried again. Same thing is happening still.

Hi Donna,

Thanks, and thank you for confirming. I’m sorry this didn’t resolve the problem.

What you wrote earlier about the v1.24.2 working fine on another server is interesting.
As you mention it’s the same host we could anticipate the server settings are similar.

Would you be willing to install the v1.24.2 on the server which currently has a problem?
If it works as it does on the other site it would help us to identify where the issue is.

You can download v1.24.2 at the bottom of this page:
https://www.ads-software.com/plugins/updraftplus/advanced/

If this is inconvenient for you please let me know and I’ll look for other solutions.

Best regards,

Nick

I have similar experience, unfortunately didn’t keep the logs but remember “next resumption” and then fails. Based on the existing backups it started to fail some weeks ago. Rolled back to 1.24.2 because it was mentioned here and now it works again.

@jonasoo that’s great! And thank you for posting here. It will help others who have the same problem and it was a great reminder to me that I need to do this. I had gotten pulled off into other work and forgot about it. Thank you!

I’ve just uploaded the 1.24.2 version, purged the cache and tried again. Got the same issue and error message. I tried a couple times. Same every time.

Failed to gain semaphore lock (fd) - another backup of this type is apparently already active - aborting (if this is wrong - i.e. if the other backup crashed without removing the lock, then another can be started after 3 minutes) (Nov 21 13:09:06)

I see that there is a new version out. So I’m going to try to update to that and see if the issue is fixed.

It looks like the newest version is still doing the same thing.

Scheduling a resumption (1) after 300 seconds (1732224069) in case this run gets aborted (Nov 21 13:16:09)

So please advise on where to go from here. I was hopeful that the 1.24.2 version would work at least so I could backup and do the updates that are needed. There is now a new WordPress update, and I have no way to backup even just the database.