Backup not completing (semaphore lock issue?)

Can you install the free plugin WP Crontrol and go to the Cron Events, are any of the events showing as overdue?

I’m having a similar semaphore lock issue. No new back-ups are being created.

This appears several times in my log file

1410.024 (4) Error (table=wp_actionscheduler_actions, type=BASE TABLE) (table_details_error): (Table ‘./secur124_veridify/wp_actionscheduler_actions’ is marked as crashed and should be repaired)

And this is the end of the log file:

1410.486 (4) UpdraftPlus WordPress backup plugin (https://updraftplus.com): 1.24.11 WP: 6.7.1 PHP: 7.4.33 (cgi-fcgi, Linux vps24399.inmotionhosting.com 3.10.0-1160.119.1.vz7.224.4 #1 SMP Mon Sep 30 15:36:27 MSK 2024 x86_64) MySQL: 5.6.51 (max packet size=268435456) WPLANG: en_US Server: Apache safe_mode: 0 max_execution_time: 900 memory_limit: 256M (used: 130.5M | 132M) multisite: N openssl: OpenSSL 1.1.1w 11 Sep 2023 mcrypt: N LANG: ZipArchive::addFile: N
1410.518 (4) Free space on disk containing Updraft’s temporary directory: 2964 MB
1410.520 (4) Requesting backup semaphore lock (ff94c0282fe3)
1410.522 (4) [Debug] Lock option (updraft_lock_ff94c0282fe3, wp_options) already existed in the database
1410.522 (4) [Info] Lock (updraft_lock_ff94c0282fe3, wp_options) could not be acquired (it is locked)
1410.523 (4) Failed to gain semaphore lock (ff94c0282fe3) – another resumption for this job is apparently already active
1410.524 (4) Failed to get backup job lock; possible overlapping resumptions – will abort this instance

Sorry for the delayed reply to the Plugin Support suggestion, but this didn’t get flagged to me by email. However, when I installed WP Crontrol there’s nothing that indicates an overdue event of any sort.

To lane0meyer … seems that you have a similar problem, but a subtly different cause. I assume that you didn’t resolve it. What I’m going to try is to backup some different way and then, when I’m happy I’ve got a properly working backup, I’ll uninstall UpDraftPlus and reinstall it. Reluctant to do that without an independent backup in case my on-line stored back-ups disappear, so this isn’t something that’ll get done today!

Hi there,

That’s no problem with the delay.

The reason my colleague suggested looking at the Cron Events is they should be registered.
At a minimum when database and files are scheduled for backup you should see these items:

updraft_backup_database, updraft_backup, updraftplus_clean_temporary_files

When searching the Cron events using the keyword ‘updraft’ the hooks should appear listed.
If this isn’t the case you could make a small change to backup settings and then change back.

It’s important to click ‘Save Changes’ to make sure the settings entries are correctly preserved.
When you return to the Cron Events the items should now be visible and scheduled to process.

If this isn’t the case please message us back and we will look for any further causes for the issue.

Best regards,

Nick

Thanks, Nick

Pretty sure that the scheduling wasn’t a problem as the plug-in wouldn’t work even when manually started. Eventually asked my wonderfully helpful host (34sp.com) for assistance. They pulled the site over to staging and were also unable to run Updraft. They then totally completely removed Updraft, deleted all the files from the staging server, reinstalled Updraft, and it is now working. Just needs to be transferred back to the main site.

While the problem has been resolved, it still doesn’t explain why things went wrong in the first place. Also it’s clear that uninstalling and reinstalling Updraft from the WordPress Plug-ins menu doesn’t completely remove all traces of the initial installation. I feel that the plug-in uninstal should at least give the option to properly clean out the application.

Hi there,

Thank you, I’m pleased to hear the problem was resolved. Your hosting sounds very helpful.
One of the challenges we face here is the constraints as to what we can do from the forum.

Your hosting did exactly what we would do, replicated the issue in a safe test environment.
We’re not allowed to do that here, we would certainly be interested in any hosting findings.

With regard to clearing all traces of the installation, I’m going to speak with our developers.
I have a script which does this but can’t distribute it until it’s been checked over thoroughly.

I fully agree with the option you suggest, maybe with an additional ‘Are you sure?’ message.
This would allow a differentiation between a full uninstall and temporary for other purposes.

Best regards,

Nick